PANews reported on January 18 that Vitalik Buterin posted on the X platform that an vital and long-underestimated facet of “trustlessness,” “leaving exams,” and “self-sovereignty” is protocol simplicity.
Even when a protocol has a whole lot of 1000’s of nodes, 49% Byzantine fault tolerance, and the nodes totally confirm all the pieces by quantum-resistant peerdas and starks, if the protocol is a large mess of a whole lot of 1000’s of strains of code and 5 PhD-level cryptographic strategies, then the protocol will finally fail in all three exams:
It’s not trustless as a result of customers should belief a small group of high-ranking clergy to inform them of the protocol’s properties.
It can not move the “go away check” as a result of if the present consumer group leaves, this can be very troublesome for the brand new group to obtain the identical degree of high quality.
It lacks self-sovereignty as a result of even essentially the most technically expert individual can not examine or perceive it, so it doesn’t totally belong to the person.
On the similar time, its safety can be low as a result of every a part of the protocol, particularly when it could possibly work together with different elements in advanced methods, is susceptible to protocol collapse.
One concern I’ve in regards to the development of the Ethereum protocol is that we could also be too keen to add new options to meet extremely particular needs, even when these options bloat the protocol or add totally new forms of interactive parts or advanced cryptography as key dependencies. This can be useful for function good points within the quick time period, however it’s extremely damaging to sustaining long-term self-sovereignty and making a decentralized superstructure that transcends the rise and fall of empires and ideologies for hundreds of years to come.
The core concern is that if protocol modifications are judged solely by “how a lot they modify the present protocol,” then the need to preserve backward compatibility means way more additions than reductions, inevitably main to bloat over time. To handle this, the Ethereum development course of needs a transparent “simplification” or “rubbish assortment” perform. “Simplification” has three metrics:
1. Decrease the whole variety of strains of code within the protocol.
2. Avoid pointless dependencies on basically advanced technical parts.
3. Add extra invariants: Core properties that the protocol can depend on, comparable to EIP-6780 (eradicating selfdestruct), which provides the property {that a} most of N storage slots could be modified per block, drastically simplifying consumer development.
Rubbish assortment could be piecemeal or large-scale. Piecemeal approaches try to simplify current performance, making it extra concise and logical. An instance of large-scale rubbish assortment is changing PoW with PoS.
One other method is “Rosetta-style backward compatibility,” the place advanced however hardly ever used options stay out there, however are “downgraded” to sensible contract code fairly than a part of the obligatory protocol, so new consumer builders haven’t got to cope with them. For instance, after upgrading to a completely native account abstraction, all older transaction varieties could be deprecated; current pre-compiled code could be changed with EVM or RISC-V code; and finally, the digital machine could be modified from EVM to RISC-V.
Lastly, it’s hoped that consumer builders will now not want to cope with all of the outdated variations of the Ethereum protocol. In the long term, the tempo of change to Ethereum could be slowed down, and efforts needs to be made to stop ineffective elements from turning into a everlasting drag on the Ethereum protocol.
