Taiko is an Ethereum Layer 2 network built as a type-1 ZK-EVM and a based rollup. It aims to preserve Ethereum execution compatibility while using Ethereum L1 validators to order rollup proposals. That design avoids a separate permanent sequencer, but Taiko’s current fast proposer and preconfirmation path is whitelisted, with forced inclusion and delayed permissionless paths serving as fallbacks. The distinction matters: “based” describes the sequencing relationship to Ethereum, not a guarantee that every part of the live system is already fully permissionless.
What Taiko is
Taiko, whose mainnet network is called Alethia, executes Ethereum-style transactions on an L2 and publishes the data needed to derive its state on Ethereum. Its type-1 ZK-EVM design targets Ethereum equivalence, so developers can generally use familiar EVM contracts and tools. Compatibility does not mean every L1 behavior is identical: fees, bridges, finality stages, contract addresses, and protocol upgrades still depend on Taiko’s own implementation.
What “based rollup” means
Many rollups use a separate sequencer to gather and order user transactions. A based rollup instead relies on the underlying L1’s validators to order rollup proposal transactions. In Taiko’s case, Ethereum determines the order in which proposals reach its L1 Inbox. This connects proposal ordering to Ethereum consensus and avoids relying on one standalone sequencer operator.
There is an important qualification in the current rollout. Taiko’s documentation describes a whitelisted fast path for proposers and preconfirmation, while the Inbox’s forced-inclusion mechanism preserves a slower permissionless fallback. A user can queue a forced inclusion on L1; when it becomes due, a proposer must process it before its own transactions. That is a censorship-resistance backstop, not the fastest ordinary transaction path.
How proposals are proved and finalized
A proposer submits one or more L2 blocks to Taiko’s Inbox on Ethereum. Nodes can derive and execute the proposed blocks, but proposal alone does not mean the range has reached Taiko protocol finality. Provers submit validity proofs for a contiguous range of proposals. When the configured verifier accepts the proof, the Inbox records a checkpoint and advances the finalized proposal range.
Taiko’s current documentation describes a composed verifier that requires multiple proof components, including at least one zero-knowledge proof. The verifier set also includes SGX-based trusted-execution proofs. This combination provides proof diversity, but it is not accurate to say the system depends only on cryptographic ZK proofs: SGX relies on hardware and attestation assumptions, and the security properties depend on the actual verifier configuration and contracts deployed.
Preconfirmations are not the same as finality
Taiko uses preconfirmations to give users an earlier indication that a transaction is expected to be included. The L1 proposal and proof process still determines how the protocol advances from a proposed state to a proved and finalized state. A quick preconfirmation should therefore not be described as identical to Ethereum finality or as eliminating all bridge and settlement risk. The live proposer and prover permissions, forced-inclusion delays, and current fork rules affect how the process works.
TAIKO token and governance
TAIKO is Taiko’s governance token; users pay ordinary Taiko L2 transaction gas in ETH. Taiko’s economic documentation also describes TAIKO proposer bonds as a protocol function, but states that the live Unzen configuration uses a zero liveness bond. Token utility should be described from the deployed configuration rather than from an earlier design or roadmap.
Governance is not simply “all decisions are made by token holders.” Taiko DAO documentation gives token holders roles in standard proposals, including a veto process, while a Security Council has security and operational authority and can approve emergency proposals. The council structure and token-holder process are part of the current governance trade-off: specialized response can be faster, while the council retains powers users should understand.
What to consider before using Taiko
Using Taiko involves the usual L2 and smart-contract risks: bugs in rollup, bridge, or application contracts; Ethereum congestion and data costs; and possible delays between a fast indication, L1 proposal, proof, and finality. Based sequencing does not remove every trust or operational assumption. The current whitelist on fast proposing and proving, SGX attestation assumptions, protocol upgrades, and forced-inclusion timing all belong in a realistic assessment.
Before bridging, check the official network and contract information, confirm that the token and application are supported, understand the bridge’s withdrawal path, and distinguish a preconfirmation from a finalized withdrawal. Do not rely on old claims that Taiko has no permissioned components or that every transaction has the same finality as a settled Ethereum L1 transaction.
Social Media Sentiment
A small r/taiko_xyz discussion of the Shasta proposal showed mixed reactions: one commenter dismissed the project, while another praised the technology and based-rollup approach. The thread had only a few votes and a brief exchange, so it is weak evidence about broader community opinion. It illustrates a tension visible in Taiko’s own design discussion—interest in Ethereum-aligned sequencing alongside questions about whether the technology and rollout are gaining traction—not a reliable measure of adoption or sentiment across users.
Last updated: 2026-10
Related Terms
See Also
- Are Layer 2 Networks Actually Decentralized?
- Does Ethereum TPS Include Layer 2 Transactions?
- What Is MEV — And Why Every Ethereum Transaction Is a Game
Looking to exchange crypto? Swap crypto with ChangeNOW.
Sources
- Taiko Protocol Overview — explains the type-1 based-rollup design, proposal lifecycle, current fork, and proof verification.
- Taiko: Based Rollups — describes Ethereum L1 proposal ordering and the current whitelisted fast path and forced-inclusion fallback.
- Taiko: Proving System — documents the live composed verifier, SGX and ZK proof roles, and proposal finalization.
- Taiko: Economics — covers ETH transaction fees, TAIKO governance and proposer-bond functions, and the current zero-bond setting.
- Taiko DAO: How the DAO Works — describes the roles of token holders and the Security Council in standard and emergency proposals.
- r/taiko_xyz: “Shasta proposal: early look” — a low-engagement community discussion used only for the bounded sentiment summary, not as technical evidence.