Original title: "a thread about the future of optimismFND"
Original author: smartcontracts.eth, Optimism developer
Original compilation: Kxp, BlockBeats
Today I think Talk about the future development of Optimism, the upcoming upgrade of Bedrock, Rollup decentralization, and ZK. If you are interested, please continue reading.
I discussed the future of Optimism in a recent talk, today I mainly want to recap Let's take a look at the core points I made in that talk so that we can fully understand how Optimism works. In addition, I also want to talk to you about the development trend of Bedrock, decentralization and ZK.
Optimism's upcoming Bedrock is the most advanced Rollup architecture ever, approaching in every way Theoretical optimal state - optimal transaction fee, optimal point of difference, optimal network, optimal block production. What makes Bedrock so advanced is its modularity and simplicity, and its design philosophy is to turn Ethereum's existing code into Rollup code. After implementing this transformation, the client-side difference was only 500 lines of code.
Bedrock is equipped with a new L2 derivative pipeline to maximize the transaction data released to Ethereum It is the only Rollup architecture that can save Gas costs. It is also the only Rollup that uses Ethereum's Engine API for consensus/execution client separation. With these capabilities, Bedrock will help Optimism become the first truly decentralized, EVM-based Rollup.
To design a Rollup that is both safe and decentralized, we must It sets up a proof mechanism (failure proof or "fraud proof") that does not include an upgrade key, so that it can update proofs without long delays.
The core problem in the design of Rollup is that during rapid , the security of the entire chain still depends on the upgrade key. Rollup security cannot be truly achieved until this problem is solved - and there is only one way to solve this problem, and that is to increase customer diversity and proof diversity.
Like Ethereum, Rollup also needs a diversity of clients so that system failures can Fork to solve. When there is a single customer, a failure can become a critical security incident. Bedrock also has a 500-line-of-code diff and consensus/enforcement separation in order to increase client diversity - neither of which is a glitch, but rather a deliberate decision. Today, Optimistic Geth is live, and I believe there will be Optimistic Erigon in the future. In addition, proof diversity will also become possible in the future, realizing multiple functions of failure proof. Ultimately, we can detect critical failures based on multiple proofs running on multiple clients.
The diversity of customers and certificates will be the future direction of development, to achieve no upgrade key smooth transition of time.
At the same time, Bedrock is the basis for many other features. Because of its flexibility and modularity, Bedrock can easily embed new data availability layers using L2-derived pipelines and failure-proof architectures (this is why OP Labs helped ship EIP-4844). As long as Ethereum ships EIP-4844, Optimism can seamlessly migrate to block blob mode, saving users a lot of money.
Bedrock's flexibility is also reflected in: it is an independent Rollup client, not An Optimistic Rollup client. Unlike other designs, Bedrock does not target a specific type of Rollup proof, or even understand the specifics of the proof. Right now, we are building an Optimistic proof - Cannon.
However, this is not to say that Bedrock cannot be replaced by a ZK proof system. We think Optimistic Rollup currently has advantages over its ZK counterparts, but Bedrock is designed to allow a seamless transition between Optimistic and ZK.
Original link
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia