Search

Search for projects by name

SummaryValue SecuredActivityOnchain costsData postedLivenessMilestones & IncidentsRisk summaryRisk analysisRollup stageData availabilityState validationOperatorWithdrawalsPermissionsSmart contracts

Taiko Alethia logo
Taiko Alethia

Badges

About

Taiko Alethia is an Ethereum-equivalent rollup on the Ethereum network. Taiko aims at combining based sequencing and a multi-proof system through SP1, RISC0 and TEEs.

  • Total Value SecuredTVS
    $41.85 M7.22%
  • Past day UOPSDaily UOPS
    1.8425.4%
  • Gas token
    ETH
  • Type
    Other
  • Purpose
    Universal
  • Chain ID
    167000

    • Tokens breakdown

    Value secured breakdown

    View TVS breakdown
    Sequencer failureState validationData availabilityExit windowProposer failure
    Explore more in Discovery UI

    Badges

    About

    Taiko Alethia is an Ethereum-equivalent rollup on the Ethereum network. Taiko aims at combining based sequencing and a multi-proof system through SP1, RISC0 and TEEs.

    Why is the project listed in others?

    The proof system isn't fully functional

    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.

    Learn more about the recategorisation here.

    Value SecuredView TVS breakdown

    2024 Sep 25 — 2025 Sep 24

    Total
    $41.85 M7.22%
    Canonically BridgedCanonically Bridged ValueCanonical
    $41.31 M7.30%
    Natively MintedNatively Minted TokensNative
    $0.000.00%
    Externally BridgedExternally Bridged ValueExternal
    $547.81 K0.98%
    ETH & derivatives
    $10.84 M8.65%
    Stablecoins
    $1.75 M1.61%
    BTC & derivatives
    $194.67 K3.30%
    Other
    $29.06 M7.19%
    View TVS breakdown
    Activity

    2024 Sep 24 — 2025 Sep 23

    Past Day UOPS
    1.84
    Past Day Ops count
    159.15 K
    Max. UOPS
    57.89
    2024 Nov 04
    Past day UOPS/TPS Ratio
    <1.01
    Onchain costs

    The section shows the operating costs that L2s pay to Ethereum.

    2024 Sep 24 — 2025 Sep 23

    1 year total cost
    $7.73 M
    Avg cost per L2 UOP
    $0.010556
    Avg cost per day
    $21.18 K
    Data posted

    This section shows the amount of data the project has posted to the EthereumEthereum.

    2024 Sep 26 — 2025 Sep 23

    1 year data posted
    99.87 GiB
    Avg size per day
    281.72 MiB
    Avg size per L2 UOP
    147.21 B
    Liveness

    This section shows how "live" the project's operators are by displaying how frequently they submit transactions of the selected type. It also highlights anomalies - significant deviations from their typical schedule.

    No ongoing anomalies detected

    2025 Aug 25 — Sep 24

    30D avg. tx data subs. interval
    6 minutes
    30D avg. state updates interval
    9 minutes
    Past 30 days anomalies
    Milestones & Incidents

    Preconfs introduction

    2025 Aug 11th

    Taiko implements preconfs - whitelisted actors provide fast soft confirmations for L2 txs.

    Learn more

    Plonky3 vulnerability patch

    2025 Jun 4th

    SP1 verifier is patched to fix critical vulnerability in Plonky3 proof system (SP1 dependency).

    Learn more
    Risk summary
    This project includes unverified contracts.
    (CRITICAL)

    Funds can be stolen if

    1. a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL),
    2. the source code of unverified contracts contains malicious code (CRITICAL),
    3. a malicious block is proven by compromised SGX instances.

    Users can be censored if

    1. the operator refuses to include their transactions.

    MEV can be extracted if

    1. the operator exploits their centralized position and frontruns user transactions.
    Risk analysis
    This project includes unverified contracts.
    (CRITICAL)
    Sequencer failureState validationData availabilityExit windowProposer failure
    Sequencer failure
    Enqueue via L1

    Users can submit transactions to an L1 queue, but can’t force them. The sequencers cannot selectively skip transactions but can stop processing the queue entirely. In other words, if the sequencers censor or are down, they are so for everyone.

    State validation
    Multi-proofs

    A multi-proof system is used. There are four verifiers available: SGX (Geth), SGX (Reth), SP1 and RISC0. Two of them must be used to prove a block, and SGX (Geth) is mandatory. A block can be proved without providing a ZK proof as SGX (Geth) + SGX (Reth) is a valid combination.

    Data availability
    Onchain

    All of the data needed for proof construction is published on Ethereum L1.

    Exit window
    None

    There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.

    Proposer failure
    Self propose

    Anyone can be a Proposer and propose new roots to the L1 bridge. Proofs can only be submitted for blocks sequenced by whitelisted operators. Provers are required to submit two valid proofs for blocks, one of which must be SGX (Geth), and the other can be either SGX (Reth), SP1, or RISC0. If the initial proposer fails to prove the block within the proving window, they forfeit half of their liveness bond.

    Rollup stage
    Taiko AlethiaTaiko Alethia is not even a
    Stage 0
    project.

    Learn more about Rollup stages
    Please keep in mind that these stages do not reflect rollup security, this is an opinionated assessment of rollup maturity based on subjective criteria, created with a goal of incentivizing projects to push toward better decentralization. Each team may have taken different paths to achieve this goal.
    Data availability

    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.

    Learn more about the DA layer here: Ethereum logoEthereum
    State validation
    Validity proofs

    Taiko uses a multi-proof system to validate state transitions. The system requires two proofs among four available verifiers: SGX (Geth), SGX (Reth), SP1, and RISC0. The use of SGX (Geth) is mandatory, while the other three can be used interchangeably. This means that a block can be proven without providing a ZK proof if SGX (Geth) and SGX (Reth) are used together. Batch proposers are required to stake a liveness bond of 25.0 TAIKO, half of which is forfeited if they fail to prove the block within the proving window of 2h. The multi-proof system allows to detect bugs in the verifiers if they produce different results for the same block. If such a bug is detected, the system gets automatically paused.

    • Funds can be stolen if a malicious block is proven by compromised SGX instances.

    1. TaikoL1.sol - Etherscan source code, liveness bond
    Operator

    The system uses whitelist-based rotating operators

    The system uses a whitelist-based sequencing mechanism to allow for fast preconfirmations on the L2. On the L1, whitelisted preconfirmers (or the fallback operator) can sequence Taiko L2 blocks by proposing them on the TaikoL1 contract. The whitelist is managed by the PreconfWhitelist contract, which currently has 4 active operators registered. 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 2h proving window. Currently, proving a block requires the block proposer to run a SGX instance with Geth, plus either SGX (Reth), SP1, or RISC0 to prove the block. Unless the block proposer proves the block within the proving window, it will forfeit half of its liveness bond to the TaikoL1 smart contract.

    • MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.

    1. TaikoL1.sol - Etherscan source code, proposeBatch function
    2. PreconfWhitelist.sol - Etherscan source code

    Users can force any transaction via L1

    Users can submit a blob containing a standalone transaction by calling the storeForcedInclusion() function on the ForcedInclusionStore contract. This forced transaction mechanism allows users to submit a transaction without running a prover. This mechanism ensures that at least one forced transaction from the queue is processed every 255 batches. However, if many transactions (k) are added to the queue, an individual transaction could experience a worst-case delay of up to k * 255 batches while waiting for its turn. Also, right now there is no mechanism that forces L2 Sequencer to include transactions from the queue in an L2 block, since L1 batches submission is permissioned behind a whitelist.

    • Users can be censored if the operator refuses to include their transactions.

    1. ForcedInclusionStore.sol - Etherscan source code, storeForcedInclusion function
    Withdrawals

    Regular exit

    The user initiates the withdrawal by submitting a regular transaction on this chain. When the block containing that transaction is finalized the funds become available for withdrawal on L1. Finally the user submits an L1 transaction to claim the funds. This transaction requires a merkle proof.

    Permissions
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    Disco UI BannerExplore in Disco

    Ethereum

    Roles:

    Sequencer (4) 0x000c…3DE70x5F62…99900xCbeB…9e9d0xe2dA…AB74

    Allowed to commit transactions from the current layer to the host chain.

    Actors:

    DAO 0x9CDf…f261

    The main contract and entrypoint of the Aragon-based DAO governance framework. Fine-grained DAO permissions, proposals, voting and thresholds are configured here.

    • Can upgrade with no delay
      • ForcedInclusionStore
      • TaikoL1
      • AutomataDcapV3Attestation
      • Taiko Token
      • DefaultResolver
      • Risc0VerifierGateway
      • TaikoDAOController
      • SgxVerifier
      • AutomataDcapV3Attestation
      • DefaultResolver
      • QuotaManager
      • MainnetERC20Vault
      • MainnetSignalService
      • SgxVerifier
      • TaikoWrapper
      • VerifierGateway
      • SP1VerifierGateway
      • PreconfRouter
      • MainnetBridge
      • L1SharedAddressManager
      • TaikoDAOController
      • PreconfWhitelist
    • Can interact with AutomataDcapV3Attestation
      • can update the program being verified
    • Can interact with DefaultResolver
      • can update the contract address for a given name
    • Can interact with Risc0VerifierGateway
      • can update the program being verified
    • Can interact with SgxVerifier
      • can add new instances without a DCAP attestation
    • Can interact with AutomataDcapV3Attestation
      • can update the program being verified
    • Can interact with DefaultResolver
      • can update the contract address for a given name
    • Can interact with SgxVerifier
      • can add new instances without a DCAP attestation
    • Can interact with SP1VerifierGateway
      • can update the program being verified
    • Can interact with L1SharedAddressManager
      • can update the contract address for a given name
    Taiko Foundation Treasury Multisig 0x363e…B3Da

    A Multisig with 2/3 threshold.

    Participants (3):

    TaikoDAOControllerEOA 10x3b1D…d5F1
    Taiko Multisig 0x9CBe…9C7F

    A Multisig with 5/7 threshold.

    Participants (7):

    0xAC58…71630xDC4e…8a0a0x0aED…50B30x1eE4…145AEOA 10x7Cdd…7F910x3b1D…d5F1
    EOA 1 0x0F02…0438

    Member of Taiko Foundation Treasury Multisig, Taiko Multisig.

    • Can upgrade with no delay
      • ProverSet

    Taiko Alethia

    Actors:

    DelegateController 0xfA06…8C7C
    • Can upgrade with no delay
      • Bridge
      • SignalService
      • L2AddressManager
      • TaikoAnchor
      • DefaultResolver
      • DelegateController
    • Can interact with L2AddressManager
      • can update the contract address for a given name
    • Can interact with DefaultResolver
      • can update the contract address for a given name
    Smart contracts
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    Disco UI BannerExplore in Disco
    A diagram of the smart contract architecture
    A diagram of the smart contract architecture

    Ethereum

    MainnetERC20Vault 0x9962…15AbImplementation (Upgradable)Admin

    Shared vault for Taiko chains for bridged ERC20 tokens.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
    • This contract can store any token.
    Can be upgraded by:
    DAO with no delay
    TaikoDAOController 0x75Ba…CD0aImplementation (Upgradable)Admin

    Middleware contract that maintains ownership of DAO-controlled assets and contracts. Its token weight does not count towards the DAO quorum. Member of Taiko Foundation Treasury Multisig.

    • Roles:
      • admin: DAO
      • owner: DAO
    Can be upgraded by:
    DAO with no delay
    TaikoDAOController 0xfC3C…b2D3Implementation (Upgradable)Admin

    Middleware contract that maintains ownership of DAO-controlled assets and contracts. Its token weight does not count towards the DAO quorum.

    • Roles:
      • admin: DAO
      • owner: DAO
    Can be upgraded by:
    DAO with no delay
    ForcedInclusionStore 0x05d8…4e03Implementation (Upgradable)Admin

    Contract that allows users to enqueue forced transactions via L1. The system guarantees that at least one pending forced transaction from the queue will be processed every 255 batches. Individual transactions may face longer delays if the queue is extensive.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    TaikoL1 0x06a9…b19aImplementation #1 (Upgradable)Implementation #2 (Upgradable)Implementation #3 (Upgradable)Admin

    Main contract implementing the logic for proposing and proving Taiko blocks on L1.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    SignerList 0x0F95…79c2Implementation (Upgradable)Admin

    A signer list for registering agents, similar to a Multisig.

    AutomataDcapV3Attestation 0x0ffa…9261Implementation (Upgradable)Admin

    Contract managing SGX attestation certificates.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
      • owner: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    Taiko Token 0x10de…d800Implementation (Upgradable)Admin

    ERC20 contract implementing the TAIKO token. It defines a list of addresses designated as non-voting.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    EmergencyMultisig 0x2Aff…7ECdImplementation (Upgradable)Admin

    Modular Governance contract allowing for proposing, voting on and executing encrypted proposals (e.g. for Security Council emergency proposals).

    EncryptionRegistry 0x2eFD…42d1

    A registry for signers (of the Security Council) to appoint agents to operate on their behalf. These agents can also register their encryption keys for encrypted emergency proposal support.

    RiscZeroGroth16Verifier 0x34Ed…641c

    Verifier contract for RISC Zero Groth16 proofs (version 2.2.0).

    DefaultResolver 0x5A98…b33aImplementation (Upgradable)Admin

    Maps contract names to contract addresses. Changes in this mapping effectively act as contract upgrades.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
      • owner: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    ProverSet 0x68d3…0dC9Implementation (Upgradable)Admin

    An operator proxy used by the Taiko team for operating (proposing, proving) the based rollup from permissioned addresses.

    • Roles:
      • admin: EOA 1
    Can be upgraded by:
    EOA 1 with no delay
    Risc0VerifierGateway 0x73Ee…74AEImplementation (Upgradable)Admin

    Entry contract to verify batches using RISC Zero.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
      • owner: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    SgxVerifier 0x7e64…0782Implementation (Upgradable)Admin

    Verifier contract for SGX proven blocks.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
      • owner: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    AutomataDcapV3Attestation 0x8d7C…a8A3Implementation (Upgradable)Admin

    Contract managing SGX attestation certificates.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
      • owner: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    DefaultResolver 0x8Efa…b43eImplementation (Upgradable)Admin

    Maps contract names to contract addresses. Changes in this mapping effectively act as contract upgrades.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
      • owner: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    QuotaManager 0x91f6…f29EImplementation (Upgradable)Admin

    Defines withdrawal limits per token.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    OptimisticTokenVotingPlugin 0x989E…50BEImplementation (Upgradable)Admin

    An optimistic governance module. Proposals pass and can be executed unless 10% of votable TAIKO veto them within 7d.

    SgxVerifier 0x9e32…0136Implementation (Upgradable)Admin

    Verifier contract for SGX proven blocks.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
      • owner: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    TaikoWrapper 0x9F9D…ef72Implementation (Upgradable)Admin

    Entry point for proposing blocks. It enforces the inclusion of forced transactions after their deadline.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    VerifierGateway 0xB169…8da1Implementation (Upgradable)Admin

    Gateway contract for the multi-proof system. It redirects proof to the appropriate verifier based on the proof type.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    SP1VerifierGateway 0xbee1…02B9Implementation (Upgradable)Admin

    Entry contract to verify batches using SP1.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
      • owner: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    PreconfRouter 0xD5AA…688aImplementation (Upgradable)Admin

    Entry point for batch proposals under the pre-confirmation architecture. It allows batches to be proposed only by whitelisted addresses.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    MainnetBridge 0xd602…d8ECImplementation (Upgradable)Admin

    Shared bridge for Taiko chains for bridged ETH.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
    • This contract stores the following tokens: ETH.
    Can be upgraded by:
    DAO with no delay
    Multisig 0xD7dA…0321Implementation (Upgradable)Admin

    Modular Governance contract allowing for proposing, voting on and executing proposals (e.g. for Security Council standard proposals).

    L1SharedAddressManager 0xEf9E…fBaaImplementation (Upgradable)Admin

    Maps contract names to contract addresses. Changes in this mapping effectively act as contract upgrades.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
      • owner: TaikoDAOController; ultimately DAO
    Can be upgraded by:
    DAO with no delay
    PreconfWhitelist 0xFD01…b2acImplementation (Upgradable)Admin

    Contains the whitelist of addresses allowed to propose batches on L1. These operators can also issue pre-confirmation from their public addresses. Currently, there are 4 operators registered.

    • Roles:
      • admin: TaikoDAOController; ultimately DAO
      • getOperatorCandidatesForCurrentEpoch: EOA 2, EOA 3, EOA 4, EOA 5
    Can be upgraded by:
    DAO with no delay
    SP1Verifier 0xFF5A…216B

    Verifier contract for SP1 proofs (v5.0.0).

    Taiko Alethia

    Bridge 0x1670…0001Implementation (Upgradable)Admin
    • Roles:
      • admin: DelegateController
    Can be upgraded by:
    DelegateController with no delay
    SignalService 0x1670…0005Implementation (Upgradable)Admin
    • Roles:
      • admin: DelegateController
    Can be upgraded by:
    DelegateController with no delay
    L2AddressManager 0x1670…0006Implementation (Upgradable)Admin

    Maps contract names to contract addresses. Changes in this mapping effectively act as contract upgrades.

    • Roles:
      • admin: DelegateController
      • owner: DelegateController
    Can be upgraded by:
    DelegateController with no delay
    TaikoAnchor 0x1670…0001Implementation (Upgradable)Admin

    Handles cross-layer message verification and manages EIP-1559 gas pricing for L2 operations. Anchors L1 block details to L2 for cross-layer communication.

    • Roles:
      • admin: DelegateController
    Can be upgraded by:
    DelegateController with no delay
    DefaultResolver 0xc322…0DC8Implementation (Upgradable)Admin

    Maps contract names to contract addresses. Changes in this mapping effectively act as contract upgrades.

    • Roles:
      • admin: DelegateController
      • owner: DelegateController
    Can be upgraded by:
    DelegateController with no delay

    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).

    • Funds can be stolen if the source code of unverified contracts contains malicious code (CRITICAL).