Taiko Alethia
Badges
About
Taiko Alethia is an Ethereum-equivalent Optimistic Rollup on the Ethereum network. In the future it aims to add zkVerifier making it a hybrid, optimistic-zk construction. Taiko combines based sequencing and a contestation mechanism with multi-proofs.
Badges
About
Taiko Alethia is an Ethereum-equivalent Optimistic Rollup on the Ethereum network. In the future it aims to add zkVerifier making it a hybrid, optimistic-zk construction. Taiko combines based sequencing and a contestation mechanism with multi-proofs.
Taiko AlethiaProjects under review might present incomplete info & data.
Recategorisation
The project will be classified as "Other" due to its specific risks that set it apart from the standard classifications.
The project will move to Others because:
Consequence: projects without a proper proof system fully rely on single entities to safely update the state. A malicious proposer can finalize an invalid state, which can cause loss of funds.
2024 May 16 — 2025 May 16
2024 May 25 — 2025 May 15
The section shows the operating costs that L2s pay to Ethereum.
2024 May 25 — 2025 May 15
Taiko Based Sequencing Upgrade
2024 Jun 6th
Proposing blocks on Taiko is now permissionless.
A multi-tier proof system is used. The tiers are SGX, ZK (RISC0, SP1), Minority Guardian, and Guardian (highest tier). A higher tier proof can challenge a lower one within the challenge period. The system allows for an invalid state to be finalized by compromised Guardians (the highest tier) and does not enforce ZK proofs.
All of the data needed for proof construction is published on Ethereum L1.
There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.
Taiko Alethia is a All data required for proofs is published on chain
All the data that is used to construct the system state is published on chain in the form of blobs. This ensures that it will be available for enough time.
EthereumTaiko uses a multi-tier proof system to validate state transitions. There are five tiers: The SGX tier, two ZK tiers with RISC0 and SP1 verifiers, the 1/8 Guardian tier and the 6/8 Guardian tier (from lowest to highest). Since the Guardian tiers are the highest, validity proofs can generally be overwritten by a single Guardian. Consequently, there is no way to force the RISC0 or SP1 tiers.
When proposing a batch (containing one or multiple L2 blocks), the proposer is assigned the designated prover role for that batch and is required to deposit a liveness bond (125.0 TAIKO) as a commitment to prove the batch, which will be returned once the batch is proven. The default (lowest) SGX tier has a proving window of 5h, during which only the designated prover can submit the proof for the batch. Once elapsed, proving is open to everyone able to submit SGX proofs and a validity bond. The two ZK tiers have a proving window of 7h.
After the proof is submitted and during its 4h cooldown window, anyone can dispute the batch by submitting a contest bond. Anyone can then prove this new dispute by submitting a validity bond as a commitment to win the respective higher-tier proof. A validity bond is TAIKO 100.0 for SGX vs 150.0 for ZK tiers, while a contest bond is TAIKO 656.25 for SGX vs. 984.375 for the two ZK tiers. For the Minority guardian tier, validity and contest bonds are set to 200.0 TAIKO and 1312.5 TAIKO, respectively. The highest Guardian tier does not require bonds.
It is not required to provide a proof for the batch to submit a contestation. When someone contests, a higher level tier has to step in to prove the contested batch. Decision of the highest tier (currently the 6/8 Guardian) is considered final. If no one challenges the original SGX proof, it finalizes after 4h (the cooldown window).
Funds can be stolen if a malicious block is proven by a compromised SGX instance or approved by Guardians.
The system uses a based sequencing mechanism
The system uses a based (or L1-sequenced) sequencing mechanism. Anyone can sequence Taiko L2 blocks by proposing them directly on the TaikoL1 contract. The proposer of a block is assigned the designated prover role, and will be the only entity allowed to provide a proof for the block during the initial proving window. Currently, proving a block requires the block proposer to run an SGX instance. Proposing a block also requires depositing a liveness bond as a commitment to proving the block. Unless the block proposer proves the block within the proving window, it will forfeit its liveness bond to the TaikoL1 smart contract.
Ethereum
Actors:
- A Multisig with 3/5 threshold.
- Can upgrade with no delay
- TaikoL1Contract
- TaikoToken
- Risc0Verifier
- GuardianMinorityProver
- L1RollupAddressManager
- SP1Verifier
- DAOFallbackProposer
- AutomataDcapV3Attestation
- SharedERC20Vault
- SignalService
- SgxVerifier
- TaikoBridge
- GuardianProver
- L1SharedAddressManager
- The entry point to the DAO Aragon-based governance framework.
- Can upgrade with no delay
- TaikoDAOController
- A Multisig with 3/5 threshold.
Ethereum
Contract managing and routing the multi-tier proof system.
This contract manages the rollup addresses list, allowing to set the address for a specific chainId-name pair.
Shared vault for Taiko chains for bridged ERC20 tokens. This contract can store any token.
Contract that maintains ownership of all contracts and assets, owned by the DAO. Its token weight does not count towards the DAO quorum.
Verifier contract for ZK-proven batches.
Verifier contract for ZK-proven batches.
SP1Verifier is a contract used to verify proofs given public values and verification key.
Contract managing SGX attestation certificates.
Shared bridge for Taiko chains for bridged ETH. This contract stores the following tokens: ETH.
This contract manages the shared addresses for Taiko rollups.
This contract provides functionalities for proposing, proving, and verifying blocks.
Taiko’s native token. Used for block proposal rewards, proving bonds and rewards, and contesting bonds.
A contract that holds TAIKO token and acts as a Taiko Labs owned proposer and prover proxy. This contract relays proveBlock calls to the TaikoL1 contract so that msg.sender doesn’t need to hold any TAIKO. There are several instances of this contract operated by different entities.
The current deployment carries some associated risks:
Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).