This week’s CoinGeek Weekly Livestream saw CoinGeek’s Chief Bitcoin Historian Kurt Wuckert Jr. catch up with Connor Murray, founder and CEO at blockchain verified review platform Britevue.
Wuckert begins by crediting Murray as one of his main influences in getting into Bitcoin SV in the first place, as an early inspiration behind Wuckert’s journey to championing the true implementation of Bitcoin, as described in Satoshi’s whitepaper.
Murray said Britevue was gearing up for next week’s CoinGeek Conference in New York, the largest event so far in Bitcoin SV history. At the conference, which is expected to draw delegates from around the world, both in person and online via the event livestream, Murray said Britevue was preparing to formally announce its verified review service.
After speaking about the review service at previous Bitcoin SV events in Miami and New York, Murray said there would be a formal announcement in New York addressing the firm’s generalized API server, which will issue proof of purchases which can later be tied to online reviews.
Britevue solves the problem of online review integrity by linking reviews to verified online purchases. Murray explains that at the point of purchase, a token is gifted to the consumer, which must be spent in order to leave feedback. This means that reviews cannot be left maliciously as easily as they can now, nor can they be left fraudulently by merchants faking their own positive testimonies. Murray said the goal of Britevue is to make the proof public for other people, engendering a greater degree of trust in the reviews we see. This is achieved with the help of the Bitcoin SV blockchain, which provides the platform on which reviews and customers status are verified.
During the livestream, Wuckert and Murray touched on a number of talking points around Bitcoin SV, both the protocol and how it does and should work in the future, and the issues presenting to developers and entrepreneurs building on the blockchain now.
The discussion turned to the storage of data on the blockchain, and the need to determine what information was actually being stored there. Murray said that large volumes of transactional data related to OP_return functions on the blockchain were currently being written to the chain. While that is less of a problem with Bitcoin SV than other blockchains due to the infinite block size, there is still the issue of whether all information being written to the blockchain needs to be recorded immutably in this way. Rather, they suggested it might be better to prioritise data that is going to be looked back on in 1000 years time, rather than operational data from the day to day, suggesting this could be where Bitcoin SV ultimately heads.
However, with transactions costing as little as fractions of a penny, and the block sizes sufficiently voluminous to take on any volumes of data, there is nothing to throttle these types of data being written to the chain. While this is far from problematic, the duo discussed how this could be streamlined in the future, creating a more user-friendly experience for those browsing the blockchain, or searching for specific data recorded to it.
Murray spoke about developing for BSV now, and whether development should focus on the tech as it is now, or as it is going to be. While he said there were a lot of opportunities at this stage in BSV enterprise blockchain’s growth, Murray noted there were complex problems being created by this forward view. So while for instance, developing with OP_return codes was probably safe, knowing these would likely still be around years from now, there were issues over building with things like non-standard scripts, which will ultimately be replaced by standard scripts.
While these are all signs of a healthy, developing ecosystem, Murray noted that this poses challenges for developers in the here and now.
New to Bitcoin? Check out CoinGeek’s Bitcoin for Beginners section, the ultimate resource guide to learn more about Bitcoin—as originally envisioned by Satoshi Nakamoto—and blockchain.