Partnered With:

Controversial Basic Rollup (BCR): a configurable, multi-verification Rollup design.

Read this article in 7 Minutes

Original author: Daniel Wang

Original title: "Based Contestable Rollup (BCR): A configurable, multi-proof rollup design"

Translated by: BlockBeats

Editor's note: This article was written by Daniel Wang, co-founder and CEO of Taiko, and delves into the architecture of the controversial Rollup (BCR), an innovative solution designed for Ethereum Rollup. The article not only analyzes the advantages and disadvantages of BCR, but also explains how it can become the ideal design framework for Ethereum Rollup. Ethereum co-founder Vitalik Buterin also discussed the concept of BCR in depth during this month's themed Twitter Space event, further confirming the relevance and timeliness of these ideas.

Table of Contents:・The uniqueness of TaikoThe credibility of the proof・Controversial Rollup・Multi-factor authentication system

・Validator availability・Dynamic configuration adjustment

・Balancing Cost and Security・Guardian Validators

・Next testnet

Taiko's uniqueness

First, let's understand the difference between Taiko and its competitors:

・No permission and decentralization required: Taiko is a basic Rollup that is the first of its kind among competitors. It does not have a centralized sequencer, but relies on Ethereum validators to sort transactions and blocks.

・Frictionless developer experience: Taiko provides a "scalable Ethereum" by using a Type 1 ZK-EVM that is equivalent to Ethereum for execution-level compatibility with Ethereum, fundamentally improving the developer experience.

・Highly configurable and future-proof: As a controversial Rollup, Taiko allows application chains to define their own proof systems and adopt updated, more efficient validity proofs as technology advances, without modifying Taiko's core protocol.

Now, let's explore why adopting a dispute mechanism is the most reasonable option for Taiko.

Proof of Trustworthiness

"34,469 lines of code can never be without errors." - Vitalik Buterin on ZK-EVM code.

Taiko's key consideration in adopting the controversial Rollup and multi-proof structure is a reasonable suspicion that "zero-knowledge proofs (ZKP) will not go wrong". Given that software complexity often increases the likelihood of vulnerabilities - as demonstrated by the Heartbleed vulnerability of OpenSSL (2014) and the major oversight of the Linux kernel in 2003, which went undiscovered for a long time - Taiko takes a cautious approach.

As a rapidly developing technology, ZKP is prone to errors. Centralized Rollup can tolerate some risks, but Taiko cannot. Taiko is committed to complete decentralization and permissionlessness, and hopes to give up control of the Taiko network in the future. Therefore, the assumption of Taiko in the design stage is that without years of proven practice, any proof may have security risks. This is why Taiko needs a dispute mechanism.

Basic Controversial Rollup (BCR)

Basic Rollup is a controversial Rollup with basic sorting. To illustrate how controversy works within the Taiko framework, consider the following example:

・Alice proposed a new block.

Bob submitted a proof for the state transition from H1 to H2, where H1 is the parent hash.

H2 is the hash of the new block. Bob placed a valid collateral of 10,000 TKO. His proof subsequently entered the cooling-off period.

・The state transition and accompanying proof proposed by Bob are publicly visible.

・Cindy noticed that Bob's conversion was incorrect and believed that it should be H1→H3 instead of H1→H2. During the cooling-off period, Cindy challenged Bob's proof by submitting her 10,000 TKO dispute bond, but she did not provide alternative proof or clearly indicate the correct conversion.

This controversial transformation is now awaiting a new, higher level of proof. Bob and any other verifiers have the opportunity to provide this proof.

Scenario 1: