Bitcoin (BTC) core developers have long been at odds over improvement proposals (BIPs) to address pain-points of the protocol, as was evident in a heated panel during Bitcoin Amsterdam.
Long-time Bitcoin developers Paul Sztorc and Peter Todd brought this to the fore in Amsterdam, with the latter coming across as highly critical of Sztorc’s work in the ongoing development of Drivechains.
Sztorc’s LayerTwo Labs has been working on BIP-300 for nearly six years, which advocates for the creation of layer two sidechains that have the potential to address a number of problems without requiring base layer changes to the Bitcoin protocol.
The ensuing debate, which was at times heated with Todd talking over Sztorc, highlighted the difficulty in reaching a consensus over BIPs that could potentially improve the overall functionality of the Bitcoin protocol.
Related: Bitcoin Amsterdam: Focus on BTC fundamentals, says Edward Snowden
Jameson Lopp, co-founder and CTO of Bitcoin custody firm Casa, weighed in on the issue during an in-depth interview with Cointelegraph at the conference, saying that the velocity of improvements and protocol changes has slowed down more than he would have liked.
That has changed somewhat in recent weeks with the emergence of new projects like BitVM and SpiderChain as Lopp explains, which leads him to believe that a couple of proposed soft forks may well be beneficial to the future of the protocol:
“In general, I think that Bitcoin should implement functionality that will improve its ability to be what you could call a cryptographic accumulator. Bitcoin should enable functionality that will boost the ability of second layers.”
Lopp adds that any potential “hardcore ossification” that some maximalists have argued for in the past would have stifled innovation that led to the creation of solutions like the Lightning Network that has helped the Bitcoin network scale to better process transactions.
“Lightning wouldn’t really be possible without OP_CLTV. It would have maybe been possible, but really clunky without SegWit. And without OP_CSV, it would not be possible to have indefinitely long-lived Lightning channels.”
Lopp was making reference to CHECKSEQUENCEVERIFY (OP_CSV) and CHECKLOCKTIMEVERIFY (OP_CLTV), two BIPs that were carried out to facilitate payment channels as soft forks. OP_CLTV was authored by Todd, describing a Bitcoin operation code that allows a transaction…
Click Here to Read the Full Original Article at Cointelegraph.com News…