bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 3쪽 중 1쪽
TAIKO: AN ETHEREUM-EQUIVALENT BASED ROLLUP
2.0.0 (September 12, 2025)
TAIKO LABS (INFO@TAIKO.XYZ)
Abstract. Taiko Alethia is an Ethereum-equivalent based rollup that achieves scaling through Ethereum’s native
validator set rather than a separate sequencer. As a based rollup, Taiko Alethia leverages Ethereum L1 validators for
transaction sequencing, ensuring maximum decentralization and inheriting Ethereum’s liveness and censorship resistance
properties. This architecture eliminates the need for centralized or semi-centralized sequencers while maintaining full
EVM-equivalence. Supporting all existing Ethereum applications, tooling, and infrastructure remains the primary
goal. Taiko Alethia operates with asynchronous batch-based processing, where multiple blocks are proposed together
and proved with aggregated validity proofs. Block proposals and proofs are asynchronous, allowing flexibility in proof
submission timing. Taiko Alethia implements a multiproving system where blocks are verified through a combination
of validity proofs including ZK-SNARKs and SGX attestations, providing both security and efficiency. A two-phase
preconfirmation system provides fast transaction confirmation, transitioning from whitelisted operators to permissionless
L1 validator participation with cryptoeconomic security. The protocol consists of three main components: Ethereum L1
validators who sequence transactions, provers who generate validity proofs for batch transitions, and a set of smart
contracts deployed on Ethereum L1 that manage the rollup’s state and verify proofs. By building directly on Ethereum’s
consensus layer, Taiko Alethia achieves true decentralization from day one while maintaining the security guarantees
and network effects of Ethereum. This based rollup design represents a paradigm shift in L2 architecture, prioritizing
decentralization and Ethereum-alignment over maximum theoretical throughput.
1.Introduction
Ethereum is well on its way into executing its rollup-
centric roadmap to achieve scalability[ 1]. This progress
has been shared by the independent rollup projects, as well
as Ethereum itself which has coordinated to accommodate
rollup-friendly upgrades.
At its base layer, facing the blockchain trilemma,
Ethereum has always been unwilling to sacrifice decentral-
ization or security in favour of scalability. These principles
have made it the most compelling network to secure value.
Its popularity, however, has often congested the network,
leading to expensive transaction fees and crowding out cer-
tain users and use cases. To serve as the world’s settlement
layer for an internet of value, the activity that Ethereum
settles will increasingly be executed on rollups: layer-2
scaling environments tightly coupled to and secured by
Ethereum.
Rollups have shifted the tradeoff space: scaling to serve
all users who seek to transact on Ethereum and enabling
lesser-value, non-financial applications without subordinat-
ing Ethereum’s strong claim of credible neutrality. There
now exists a new tradeoff space among different rollup
constructions, and there exists a hope to again shift the
solution curve, rather than move along it. Taiko Alethia at-
tempts to do exactly that, by implementing a based rollup
that stays as true to the EVM and Ethereum specifications
as possible, while leveraging advanced cryptographic proofs
including ZK-SNARKs and SGX attestations for efficient
batch verification.
Taiko Alethia aims for full Ethereum-equivalence, al-
lowing our rollup to support all existing Ethereum smart
contracts and dapps, developer tooling, and infrastructure.
Complete compatibility benefits developers who can deploy
their existing solidity contracts as is, and continue using
the tools they are familiar with. This compatibility also
extends to network participants and builders of Taiko’s L2
blockchain, who can, for example, run Taiko Alethia nodes
which are minimally modified Ethereum execution clients
like Geth, and reuse other battle-hardened infrastructure.
Finally, it extends to end-users, who can experience the
same usage patterns and continue using their preferred
Ethereum products. We have seen the strong demand for
cheaper EVM environments empirically, with dapp and
protocol developers as well as users often migrating to
sidechains or alternative L1s which run the EVM, even if
it meant much weaker security guarantees.
To be Ethereum-equivalent means to emulate Ethereum
along further dimensions, too. Prioritizing decentralization
and security within the layer-2 architecture ensures there
is no dissonance between the environments, and that the
Ethereum community’s core principles are upheld. With
calldata cost reductions such as EIP-2028[2] and blob-based
cost reduction in EIP-4844[3], as well as other mechanisms
coming in the future, Ethereum’s commitment to rollups
is strong and credible; rollups’ commitment to Ethereum
ought to be the same.
2.Previous Work
The Ethereum ecosystem began exploring layer-2 so-
lutions for scaling in 2017 with Plasma[ 5]. Layer-2s
move computation off-chain while keeping data either on
Ethereum or also off-chain.
Rollups, which post compressed transaction data to
Ethereum, emerged as the leading scalability path over the
past several years, offering stronger security guarantees
than earlier L2 solutions (Plasma and State Channels)
while supporting a broader range of applications. Initially
proposed by Vitalik Buterin[ 6] and Barry Whitehat[ 7] in
2018, rollups have evolved through multiple paradigms.
Early ZK-Rollups, starting with Loopring in 2019, were
application-specific due to ZKP limitations, precluding gen-
eral EVM use cases and composability. Optimistic rollups
like Optimism and Arbitrum achieved EVM-compatibility
in 2021 but rely on fraud proofs, introducing challenges
Date: September 12, 2025.
1
TAIKO: AN ETHEREUM-EQUIVALENT BASED ROLLUP 2
including dependency on watchers for security and lengthy
withdrawal periods that hinder cross-rollup composability.
Projects such as zkSync, Starkware, Polygon, and Scroll,
supported by the Ethereum Foundation’s Privacy and
Scaling Explorations unit[8], have developed ZK-powered
rollups that combine EVM compatibility with crypto-
graphic security. However, most existing rollups, both opti-
mistic and ZK-based, rely on centralized or semi-centralized
sequencers, creating single points of failure, censorship
risks, and MEV extraction concerns.
Based rollups, first conceptualized by Justin Drake[ 16],
represent a paradigm shift in rollup design. Rather than
operating independent sequencers, based rollups leverage
Ethereum L1 validators for transaction sequencing. This
approach inherits Ethereum’s liveness, censorship resis-
tance, and decentralization properties while eliminating
sequencer-related risks. The concept builds upon ear-
lier work on forced inclusion mechanisms[ 17] and shared
sequencing[18].
Recent research has explored various aspects of based
rollup design, including preconfirmations for faster trans-
action confirmations[ 19], multiproving systems for en-
hanced security[ 20], and mechanisms for cross-rollup
composability[21]. The trade-off space has shifted from
EVM-compatibility versus proving efficiency to decentral-
ization versus maximum theoretical throughput.
Taiko Alethia’s approach prioritizes Ethereum-
equivalence and decentralization through its based rollup
architecture with asynchronous batch-based processing.
The protocol maintains security through a multiproving
system combining ZK-SNARKs and SGX attestations.
This design philosophy aligns with Ethereum’s core val-
ues while providing practical scalability, as we describe
throughout this paper.
3.Design Principles
Taiko Alethia’s based rollup architecture is guided by
fundamental principles that prioritize decentralization, se-
curity, and Ethereum alignment:
(1) Based Sequencing.Transaction sequencing is
performed by Ethereum L1 validators rather than
a separate sequencer set. This eliminates central-
ized sequencers and inherits Ethereum’s liveness
guarantees, ensuring the rollup cannot halt inde-
pendently of L1.
(2) Permissionless Participation.Anyone can pro-
pose blocks and generate proofs without special
permissions. The protocol is designed such that
anyone is able to opt-in and propose or prove
blocks. Phase 1 of preconfirmations Taiko Alethia
is permissioned, but with phase 2 rollout and
whitelist removal, will return to permisionless se-
quencing and proposing.
(3) Ethereum-Equivalence.The rollup maintains
full compatibility with Ethereum by directly inter-
preting EVM bytecode, using identical hash func-
tions, state trees, transaction trees, and precom-
piled contracts. This ensures seamless deployment
of existing Ethereum applications and tooling.
(4) Security.State transitions are secured through
multiple independent proof systems, including ZK-
SNARKs and SGX attestations. This approach
ensures security even if one proving system is com-
promised.
(5) Censorship Resistance.By inheriting
Ethereum’s censorship resistance through based
sequencing and supporting forced transaction in-
clusion, users cannot be censored by any single
party. Transactions submitted to L1 are guaran-
teed eventual inclusion.
(6) Economic Alignment.MEV and transaction
fees flow to Ethereum validators and the Ethereum
ecosystem, strengthening L1’s economic security.
The rollup’s economic success directly reinforces
Ethereum’s sustainability.
(7) Minimal Trust Assumptions.Security relies
solely on Ethereum’s consensus and cryptographic
proofs, with no additional trust assumptions. The
protocol avoids, as much as possible, introduc-
ing new honest-majority assumptions or trusted
parties.
These principles guide Taiko toward building a truly
decentralized scaling solution that extends Ethereum with-
out compromising its core values. By leveraging based
sequencing, Taiko Alethia achieves decentralization while
maintaining practical performance through preconfirma-
tions and efficient proving systems.
The protocol may initially disable certain EIPs[ 9] for sta-
bility, with plans to enable them as the system matures
(see Section B).
4.Overview
Taiko Alethia builds a secure, decentralized, based
rollup on Ethereum with native preconfirmation support.
These requirements dictate the following properties:
(1) Data Availability on L1:All block data re-
quired to reconstruct the post-block state is pub-
lished on Ethereum, ensuring public availability.
This satisfies the rollup property and maintains
decentralization. For permissionless proof genera-
tion, all data needed to re-execute blocks step-by-
step must be publicly accessible, enabling anyone
to generate proofs using only public data.
(2) Based Sequencing with Preconfirmations:
Block creation leverages Ethereum validators for
sequencing while supporting fast preconfirmations.
Through Taiko Alethia’s based preconfirmation
mechanism, users receive up to sub-second trans-
action confirmations from preconfirmers who pro-
vide economic guarantees before L1 inclusion. This
combines the decentralization of based sequencing
with the UX benefits of fast confirmations.
Taiko Alethia implements a sophisticated block lifecycle:
Preconfirmation Phase: Users submit transac-
tions to preconfirmers who provide a receipt via
inclusion in an “unsafe” block, which is created
and gossiped via P2P. These preconfirmations offer
economic guarantees backed by collateral, giving
users confidence that their transactions are exe-
cuted within seconds rather than waiting for L1
block times. When the batch is proposed to the
L1, these blocks achieve finality (given that the
L1 does not experience a reorg).
TAIKO: AN ETHEREUM-EQUIVALENT BASED ROLLUP 3
Block Proposal: Preconfirmed transactions are
batched and proposed to the TaikoInbox contract
on Ethereum. Once registered, all block properties
become immutable, making execution determin-
istic. The block is immediately consideredexe-
cutableas anyone can calculate the post-block
state. The Pacaya fork ensures preconfirmers
honor their commitments through slashing condi-
tions.
Block Verification: Provers generate validity
proofs (ZK-SNARKs or SGX attestations) for
proposed blocks. Since blocks are deterministic
post-proposal, they can be proven in parallel.
The Pacaya fork’s multiproving system requires
different proof types for enhanced security. Once
proven, blocks achieveon-chain verification.
The Pacaya fork optimizes costs through intelligent
batching:
Batch-based Protocol: Blocks are proposed in
batches to amortize L1 costs. Each batch can
contain multiple L2 blocks that share metadata
and transaction sources (calldata or blobs). This
enables frequent small blocks in a single batch,
crucial for supporting responsive preconfirmations
while maintaining economic viability.
Preconfirmation Integration: The batching sys-
tem coordinates with preconfirmers to ensure
committed transactions are included within their
promised timeframes. This maintains the validity
of preconfirmation guarantees while optimizing L1
resource usage.
This architecture enables up to sub-second preconfir-
mations with strong economic guarantees while preserving
the security and decentralization properties of based se-
quencing (see Section 6).
5.The Taiko Alethia Blockchain
Taiko Alethia operates as an Ethereum-equivalent based
rollup with asynchronous batch-based processing. The
blockchain consists of batches containing multiple blocks
of user transactions, where each batch is proposed to the
TaikoInbox contract on Ethereum L1. Block proposals and
proofs operate asynchronously, allowing flexibility in proof
submission timing while maintaining security through eco-
nomic bonds.
The protocol implements a multiproving system sup-
porting multiple verifier types including SGX attestations,
SP1 proofs, and Risc0 proofs. Each batch undergoes veri-
fication through designated verifier contracts, with proof
systems presumed error-free validated.
The protocol architecture includes a two-phase pre-
confirmation system aimed at improving user experience
through fast transaction confirmation. Phase 1 utilizes
whitelisted operators managed through PreconfWhitelist
and PreconfRouter contracts, while Phase 2 transitions
to permissionless L1 validator participation with cryptoe-
conomic security. Authorized preconfirmers can propose
batches through the PreconfRouter contract, enhancing
user experience with up to sub-second confirmations while
maintaining the decentralization properties of based se-
quencing.
5.1.Core Contracts.Taiko Alethia implements its based
rollup protocol through a suite of smart contracts deployed
on both L1 and L2, with additional contracts supporting
the preconfirmation and forced inclusion systems.
5.1.1.Layer 1 Contracts.
TaikoInbox. The primary L1 contract for batch proposals
in Taiko Alethia. The contract implements asynchronous
batch-based processing where multiple blocks are proposed
together and proved with aggregated validity proofs. The
contract maintains:
state: A State struct containing batch ring buffer,
transition states, and bond balances.
inboxWrapper: Optional address that when set,
restricts batch proposals.
verifier: Address for contract that handles proof
verification.
signalService: Interface for cross-layer communica-
tion and state synchronization.
PreconfWhitelist. Manages the authorized preconfirmation
operators with epoch-based selection:
operators: Registry of preconfirmation operators
with activation/inactivation epochs.
epochSelection: Selects operators for specific
epochs using randomness from beacon block roots.
operatorManagement: Supports adding, remov-
ing, and consolidating operators with configurable
delays.
PreconfRouter. Provides a controlled entrypoint for se-
quencers to propose batches:
batchProposal: Routes batch proposals from au-
thorized preconfirmers to the TaikoInbox.
authorization: Ensures only whitelisted precon-
firmers or fallback addresses can propose.
blockValidation: Optionally validates expected
last block ID before accepting proposals.
ForcedInclusionStore. Allows users to pay a fee to ensure
their transactions are included in a block:
queue: FIFO queue of forced inclusion requests with
head and tail tracking.
inclusionDelay: Configurable delay before forced
inclusions become processable.
getOldestForcedInclusionDeadline(): Returns
when the oldest forced inclusion becomes due.
TaikoWrapper. A delayed inbox implementation to enforce
transaction inclusion:
proposeBatch(): Processes both forced inclusion
and regular batches.
validation: Ensures minimum transaction require-
ments for forced inclusions.
integration: Works with TaikoInbox and ForcedIn-
clusionStore contracts.
5.1.2.Layer 2 Contracts.
TaikoAnchor. The primary L2 contract that handles cross-
layer message verification and manages EIP-1559 gas pric-
ing:
(1) Anchoring: Anchors latest L1 block details to L2
and verifies cross-layer message integrity.
(2) State Root Synchronization: Synchronizes L1 state
roots via signal service for multi-hop bridging.
TAIKO: AN ETHEREUM-EQUIVALENT BASED ROLLUP 4
(3) Gas Pricing: Calculates base fee using EIP-1559
parameters with gas excess tracking.
(4) Public Input Hash: Maintains a rolling public in-
put hash using a 255-block ring buffer.
The TaikoAnchor contract uses a “golden touch” ad-
dress for authorized anchoring transactions.
5.1.3.Transaction Lists.The txList contains the RLP-
encoded list of all transactions in blocks within a batch.
Transaction data can be provided either through calldata
or EIP-4844 blobs for more efficient data availability. The
protocol calculates a txsHash from the transaction data,
which is used for verification purposes.
5.2.Proposing Blocks.Block proposing in Taiko
Alethia occurs through the TaikoInbox contract’s
proposeBatch() function. The contract supports both
permissionless proposing and restricted proposing through
an optional inboxWrapper. Batches can contain multiple
blocks and support both calldata and blob-based trans-
action data. Block proposals and proofs operate asyn-
chronously, allowing flexibility in proof submission timing.
The TaikoInbox contract performs validation including
checking anchor blocks, timestamp progression, and ensur-
ing proposers have sufficient bonds.
5.2.1.Batch Metadata.Batches are proposed to the
TaikoInbox contract with BatchMetadata containing:
infoHash: A bytes32 hash containing batch infor-
mation.
proposer: The Ethereum address of the batch pro-
poser.
batchId: A 64-bit unsigned integer batch identifier.
proposedAt: A 64-bit timestamp for when the
batch was proposed.
5.2.2.Block Parameters.Individual blocks within a batch
are described by BlockParams:
numTransactions: The number of transactions in
the block (uint16).
timeShift:Time adjustment parameter (uint8).
signalSlots: Array of signal slot hashes for cross-
chain communication.
5.2.3.Batch Validation.Batch proposals undergo several
validation checks:
• Verification that the batch is within allowed fork
heights
•Validation of anchor block recency and validity
•Checking transaction data or blob availability
•Ensuring timestamp progression between blocks
•Verifying proposer has sufficient bond
•Limiting the number of blocks per batch
Transaction validation and execution details are handled
by the L2 execution layer following standard Ethereum
transaction processing rules.
(1) The txList is RLP decodable into a list of transac-
tions, and;
(2) The number of transactions is within the block’s
specified limit, and;
(3) The sum of all transactions’ gasLimit is no larger
than the protocol constantKBlockMaxGasLimit, and;
(4) Each and every transaction’s signature is valid, i.e.
it does not recover to the zero address.
Formally,V l(L) is defined as:
V l(L)≡NOERR(T≡RLP ′(L))∧(1)
∥T∥≤numTransactions∧
(
∥T∥−1∑
j=0
T[j] g)≤K BlockMaxGasLimit ∧
∥T∥−1∏
j=0
(T[j] g≥K TxMinGasLimit)∧
∥T∥−1∏
j=0
(NOERR(ECRECOVER(T[j])̸= 0))
Where NOERR(S) is a catch-error func프로젝트로 돌아가기