Search
Search for projects by name or address
Base Chain
Badges
About
Base is an Optimistic Rollup built with the OP Stack. It offers a low-cost and builder-friendly way for anyone, anywhere, to build onchain.
Interop protocols used
Tokens by volume
Badges
About
Base is an Optimistic Rollup built with the OP Stack. It offers a low-cost and builder-friendly way for anyone, anywhere, to build onchain.
Stages changes
The project will move to Stage 0 because:
The proof system does not meet the minimum trusted setup requirements defined in the L2BEAT trusted setup assessment framework.
2025 Jun 27 — 2026 Jun 27
The section shows the operating costs that L2s pay to Ethereum.
2025 Jun 27 — 2026 Jun 27
This section shows how much data the project publishes to its data-availability (DA) layer over time. The project currently posts data toEthereum.
2025 Jun 27 — 2026 Jun 27
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.
2026 May 28 — Jun 27
Last 30 day anomalies
All liveness anomalies detected for this project in the last 30 days, helping you review recent downtime and availability issues.
No Tx data submissions were performed for 1h 18m 12s (from 2026 Jun 25, 16:05 UTC until 2026 Jun 25, 17:23 UTC). These typically occur every 47s on average.
No Tx data submissions were performed for 1h 36m 24s (from 2026 Jun 25, 07:23 UTC until 2026 Jun 25, 09:00 UTC). These typically occur every 47s on average.
No Tx data submissions were performed for 7h 2m 36s (from 2026 Jun 05, 13:57 UTC until 2026 Jun 05, 21:00 UTC). These typically occur every 47s on average.
No State updates were performed for 43h 48m (from 2026 May 29, 01:02 UTC until 2026 May 30, 20:50 UTC). These typically occur every 17min 31s on average.
Base Azul: multi-proof
2026 May 26th
Base activates the multiproof system combining TEE attestations and SP1 ZK proofs.
Base leaves the Superchain
2026 Mar 4th
Base decouples from Optimism Superchain governance with its own upgrade path.
Fraud proofs allow actors watching the chain to prove that the state is incorrect. Single round proofs (1R) prove the validity of a state proposal, only requiring a single transaction to resolve. A fault proof eliminates a state proposal by proving that any intermediate state transition in the proposal results in a different state root. For either, a ZK proof is used.
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. Upgrades need to be approved by 2 parties: the Base Coordinator Multisig and the Base Security Council.
New requirements coming soon
The proof system does not meet the minimum trusted setup requirements defined in the L2BEAT trusted setup assessment framework.
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 cheap blobs or calldata. This ensures that it will be available for enough time.
- Derivation: Batch submission - OP Mainnet specs
- BatchInbox - address
- OptimismPortal2.sol - source code, depositTransaction function
Ethereum
State roots are proposed by calling DisputeGameFactory.create with the AggregateVerifier game type, posting a bond of 0.05 ETH. Each proposal must include an initial proof (TEE attestation or ZK proof) over the range of 600 L2 blocks split into sub-ranges of 30 blocks. With a single proof, the game resolves after 5d; if both proof arms commit, the window collapses to 1d.
Any party that produces a valid ZK proof of an incorrect intermediate root can call AggregateVerifier.challenge, contradicting a TEE-only proposal. The challenger’s proof is verified onchain via the SP1 verifier gateway. If the challenge stands until the resolution window closes, the original proposer’s bond is awarded to the challenger and the game resolves CHALLENGER_WINS. Soundness contradictions within a single proof arm are caught by AggregateVerifier.nullify, which permanently disables that arm’s verifier contract for all games.
All contracts are upgradable by a ProxyAdmin contract controlled by a nested 2/2 Base Governance Multisig composed of the Base Coordinator Multisig and the Base Security Council. Upgrades require approval from both parties. There is no delay on upgrades. The Guardian role for the SuperchainConfig is assigned to the Base Governance Multisig, which can pause and unpause withdrawals. Base Multisig 1 serves as Incident Responder and can pause withdrawals but cannot unpause or extend pauses. Each pause automatically expires after 3 months if not extended by the Guardian. The single Sequencer actor can be modified by Base Multisig 1 via the SystemConfig contract. The Base Governance multisig can also recover dispute bonds in case of bugs that would distribute them incorrectly.
State validation runs through the AggregateVerifier game type (621), which accepts either an AWS Nitro TEE attestation or an SP1 ZK proof. The TEE prover allowlist in the TEEProverRegistry is managed solely by the Base Coordinator Multisig (without Base Security Council approval), and a separate Manager EOA can register or deregister enclave signers. The ZK arm routes through a Base-owned SP1 verifier gateway; the Base Governance Multisig can add or freeze verifier routes. The Base Governance Multisig can swap the AggregateVerifier implementation, change the respected game type, blacklist individual games, or retire all in-flight games via the AnchorStateRegistry.
Past upgrades
The metrics include upgrades on the currently used proxy contracts. Historical proxy contracts and changes of such are not included.
2026 June 25, 08:49 UTCHigh severity10changesBase Beryll upgrade: https://x.com/buildonbase/status/2067693904909189141. Reduced optimistic path finalization 7d - 5d: https://disco.l2beat.com/diff/eth:0xeEcb8A5944B217585817E802702b1262a049D259/eth:0x1bd8db5139Ba7aC9277684650c15e6E341761919. Also deployed a new AggregateVerifier with new program hashes and upgraded the TEE Image hash. All programs are reproduced.
Base Beryll upgrade: https://x.com/buildonbase/status/2067693904909189141.
Reduced optimistic path finalization 7d -> 5d: https://disco.l2beat.com/diff/eth:0xeEcb8A5944B217585817E802702b1262a049D259/eth:0x1bd8db5139Ba7aC9277684650c15e6E341761919.
Also deployed a new AggregateVerifier with new program hashes and upgraded the TEE Image hash. All programs are reproduced.
| contract TEEProverRegistry (eth:0x1af2A7E537DE2eE795DE5B8BfbB1Ad0DD513A5aA) [base/TEEProverRegistry] { | |
| +++ description: Registry of authorized TEE enclave signers and proposer addresses used by the TEEVerifier. Owner can add or remove allowlisted proposers via setProposer (onlyOwner) and set the AggregateVerifier game type lookup. Owner and Manager can register or deregister enclave signers via registerSigner / deregisterSigner. Registration requires a Risc0 ZK proof of a valid AWS Nitro attestation document verified by the NITRO_VERIFIER. | |
| +++ severity: HIGH | |
| values.getExpectedImageHash: | |
| - | "0xc9536fb5b1387f30d16f6b95a5a26de352f8056866482bca632f7219896ea74c" |
| + | "0x58557c709e93357a135041297107aecc4bc6ba616509098a4aa8dbef774d212a" |
| +++ severity: LOW | |
| values.getRegisteredSigners.0: | |
| - | "eth:0x8a2B99252bad63813e704237Bf2A40A6a4cEBda9" |
| + | "eth:0xBb82fe2b294F7a9F74aF2ad32DF3B2d61abd4BEC" |
| +++ severity: LOW | |
| values.getRegisteredSigners.1: | |
| - | "eth:0xf3aef21F74AD989812D066ad3e51b986ED312875" |
| + | "eth:0x1A095fE4895D142955c36F958be2a9e53c41224f" |
| } |
| contract DisputeGameFactory (eth:0x43edB88C4B80fDD2AdFF2412A7BebF9dF42cB40e) [opstack/DisputeGameFactory_v2] { | |
| +++ description: The dispute game factory allows the creation of dispute games, used to propose state roots and eventually challenge them. This variant exposes per-type reads only; the legacy array views (gameImpls[], initBonds[]) were removed in the new implementation. | |
| +++ severity: HIGH | |
| values.game621: | |
| - | "eth:0xeEcb8A5944B217585817E802702b1262a049D259" |
| + | "eth:0x1bd8db5139Ba7aC9277684650c15e6E341761919" |
| } |
| - | Status: DELETED |
| contract AggregateVerifier (eth:0xeEcb8A5944B217585817E802702b1262a049D259) [opstack/AggregateVerifier] | |
| +++ description: Game type implementation that combines a TEE attestation arm and a ZK proof arm. A single un-nullified proof of either type can resolve a game (PROOF_THRESHOLD = 1). When both arms commit, the finalization window collapses from SLOW_FINALIZATION_DELAY (7d) to FAST_FINALIZATION_DELAY (1d). |
| + | Status: CREATED |
| contract AggregateVerifier (eth:0x1bd8db5139Ba7aC9277684650c15e6E341761919) [opstack/AggregateVerifier] | |
| +++ description: Game type implementation that combines a TEE attestation arm and a ZK proof arm. A single un-nullified proof of either type can resolve a game (PROOF_THRESHOLD = 1). When both arms commit, the finalization window collapses from SLOW_FINALIZATION_DELAY (5d) to FAST_FINALIZATION_DELAY (1d). |
2026 June 23, 10:14 UTC2changesFeeDisburser admin rotated. Not security critical.
FeeDisburser admin rotated. Not security critical.
| contract FeeDisburser (base:0x09C7bAD99688a55a2e83644BFAed09e62bDcCcBA) [opstack/Layer2/FeeDisburser] { | |
| +++ description: Contract used to disburse funds from system FeeVault contracts, shares revenue with Optimism and bridges the rest of funds to L1. | |
| values.$admin: | |
| - | "base:0xaD5B57FEB77e294fD7BF5EBE9aB01caA0a90B221" |
| + | "base:0xa966054731540a48b28990b63Dcf4f33d8aE57B2" |
| } |
2026 June 10, 15:32 UTC4changesRotated TEE signers.
Rotated TEE signers.
| contract TEEProverRegistry (eth:0x1af2A7E537DE2eE795DE5B8BfbB1Ad0DD513A5aA) [base/TEEProverRegistry] { | |
| +++ description: Registry of authorized TEE enclave signers and proposer addresses used by the TEEVerifier. Owner can add or remove allowlisted proposers via setProposer (onlyOwner) and set the AggregateVerifier game type lookup. Owner and Manager can register or deregister enclave signers via registerSigner / deregisterSigner. Registration requires a Risc0 ZK proof of a valid AWS Nitro attestation document verified by the NITRO_VERIFIER. | |
| +++ severity: LOW | |
| values.getRegisteredSigners.0: | |
| - | "eth:0xBeF9176fa15489735Cc8B1ddD97E53b4a656287e" |
| + | "eth:0x8a2B99252bad63813e704237Bf2A40A6a4cEBda9" |
| +++ severity: LOW | |
| values.getRegisteredSigners.1: | |
| - | "eth:0xB830004297a91c10ed7428f462FCf0cc5073e9A2" |
| + | "eth:0xf3aef21F74AD989812D066ad3e51b986ED312875" |
| } |
2026 June 08, 13:23 UTCHigh severity2changesRotated TEE signer.
Rotated TEE signer.
| contract TEEProverRegistry (eth:0x1af2A7E537DE2eE795DE5B8BfbB1Ad0DD513A5aA) [base/TEEProverRegistry] { | |
| +++ description: Registry of authorized TEE enclave signers and proposer addresses used by the TEEVerifier. Owner can add or remove allowlisted proposers via setProposer (onlyOwner) and set the AggregateVerifier game type lookup. Owner and Manager can register or deregister enclave signers via registerSigner / deregisterSigner. Registration requires a Risc0 ZK proof of a valid AWS Nitro attestation document verified by the NITRO_VERIFIER. | |
| +++ severity: HIGH | |
| values.getRegisteredSigners.0: | |
| - | "eth:0xA200e289262F76dD422f688e65C453F5aeF7709B" |
| +++ severity: HIGH | |
| values.getRegisteredSigners.1: | |
| + | "eth:0xB830004297a91c10ed7428f462FCf0cc5073e9A2" |
| } |
2026 June 05, 13:53 UTCHigh severity2changesRotated TEE signer.
Rotated TEE signer.
| contract TEEProverRegistry (eth:0x1af2A7E537DE2eE795DE5B8BfbB1Ad0DD513A5aA) [base/TEEProverRegistry] { | |
| +++ description: Registry of authorized TEE enclave signers and proposer addresses used by the TEEVerifier. Owner can add or remove allowlisted proposers via setProposer (onlyOwner) and set the AggregateVerifier game type lookup. Owner and Manager can register or deregister enclave signers via registerSigner / deregisterSigner. Registration requires a Risc0 ZK proof of a valid AWS Nitro attestation document verified by the NITRO_VERIFIER. | |
| +++ severity: HIGH | |
| values.getRegisteredSigners.0: | |
| - | "eth:0xA4F50DA2549C7E79C175a1359e7DAa97139Dd611" |
| +++ severity: HIGH | |
| values.getRegisteredSigners.1: | |
| + | "eth:0xBeF9176fa15489735Cc8B1ddD97E53b4a656287e" |
| } |
Users can force any transaction
Because the state of the system is based on transactions submitted on the underlying host chain and anyone can submit their transactions there it allows the users to circumvent censorship by interacting with the smart contract on the host chain directly.
Forced messaging
If the user experiences censorship from the operator with regular L2->L1 messaging they can submit their messages directly on L1. The system is then obliged to service this request or halt all messages, including forced withdrawals from L1 and regular messages initiated on L2. Once the force operation is submitted and if the request is serviced, the operation follows the flow of a regular message.
EVM compatible smart contracts are supported
OP stack chains are pursuing the EVM Equivalence model. No changes to smart contracts are required regardless of the language they are written in, i.e. anything deployed on L1 can be deployed on L2.
Ethereum
Actors:
A Multisig with 2/2 threshold.
- Can upgrade with no delay
- OptimismMintableERC20Factory ProxyAdmin
- TEEProverRegistry ProxyAdmin
- L1StandardBridge ProxyAdmin
- DisputeGameFactory ProxyAdmin
- OptimismPortal2 ProxyAdmin
- L1ERC721Bridge ProxyAdmin
- DelayedWETH ProxyAdmin
- SystemConfig ProxyAdmin
- L1CrossDomainMessenger ProxyAdmin
- AnchorStateRegistry ProxyAdmin
- SuperchainConfig ProxyAdmin
- DelayedWETH ProxyAdmin
- Can interact with AddressManager
- set and change address mappings ProxyAdmin
- Can interact with SuperchainConfig
- Allowed to pause withdrawals. In op stack systems with a proof system, the Guardian can also blacklist dispute games and set the respected game type (permissioned / permissionless)
- Can interact with SP1VerifierGateway
A Multisig with 3/5 threshold.
- Can interact with TimelockController
- cancel queued transactions
- execute transactions that are ready
- manage all access control roles with 3d delay TimelockController with 3d delay
- propose transactions
- Can interact with RiscZeroVerifierEmergencyStop
- pause the verifier
- Can interact with RiscZeroVerifierEmergencyStop
- pause the verifier
- Can interact with RiscZeroVerifierEmergencyStop
- pause the verifier
- Can interact with RiscZeroVerifierRouter
- add/remove verifiers and the selectors they are mapped to with 3d delay TimelockController with 3d delay
- Can interact with RiscZeroVerifierEmergencyStop
- pause the verifier
- Can interact with RiscZeroVerifierEmergencyStop
- pause the verifier
A Multisig with 8/11 threshold. Member of Base Governance Multisig.
A Multisig with 3/6 threshold. Member of Base Governance Multisig.
- Can interact with SystemConfig
- Allowed to commit transactions from the current layer to the host chain
Base Chain
Actors:
- Can upgrade with no delay
- L2CrossDomainMessenger ProxyAdmin
- L2StandardBridge ProxyAdmin
- SequencerFeeVault ProxyAdmin
- OptimismMintableERC20Factory ProxyAdmin
- L1BlockNumber ProxyAdmin
- L2ERC721Bridge ProxyAdmin
- L1Block ProxyAdmin
- L2ToL1MessagePasser ProxyAdmin
- OptimismMintableERC721Factory ProxyAdmin
- ProxyAdmin ProxyAdmin
- BaseFeeVault ProxyAdmin
- L1FeeVault ProxyAdmin
- SchemaRegistry ProxyAdmin
- EAS ProxyAdmin
- Can upgrade with no delay
- FeeDisburser
Ethereum
The dispute game factory allows the creation of dispute games, used to propose state roots and eventually challenge them. This variant exposes per-type reads only; the legacy array views (gameImpls[], initBonds[]) were removed in the new implementation.
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig
Base’s own SuperchainConfig, used to manage pause states for the Base chain. The guardian and incident responder roles are immutable and set at construction time. The guardian can pause, unpause, and extend pauses, while the incident responder can only pause. Each pause automatically expires after 3 months.
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig
- guardian: Base Governance Multisig
- incident_responder: Base Multisig 1
The main entry point to deposit ERC20 tokens from host chain to this chain.
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig
All supported tokens in this escrow are included in the value secured calculation.
Used to bridge ERC-721 tokens from host chain to this chain.
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig
Sends messages from host chain to this chain, and relays messages back onto host chain. In the event that a message sent from host chain to this chain is rejected for exceeding this chain’s epoch gas limit, it can be resubmitted via this contract’s replay function.
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig
- Roles:
- owner: Base Governance Multisig
A helper contract that generates OptimismMintableERC20 contracts on the network it’s deployed to. OptimismMintableERC20 is a standard extension of the base ERC20 token contract designed to allow the L1StandardBridge contracts to mint and burn tokens. This makes it possible to use an OptimismMintableERC20 as this chain’s representation of a token on the host chain, or vice-versa.
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig
A timelock with access control. The current minimum delay is 3d.
- Roles:
- canceller: Safe
- defaultAdmin: TimelockController; ultimately Safe
- executor: Safe
- proposer: Safe
Registry of authorized TEE enclave signers and proposer addresses used by the TEEVerifier. Owner can add or remove allowlisted proposers via setProposer (onlyOwner) and set the AggregateVerifier game type lookup. Owner and Manager can register or deregister enclave signers via registerSigner / deregisterSigner. Registration requires a Risc0 ZK proof of a valid AWS Nitro attestation document verified by the NITRO_VERIFIER.
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig
Game type implementation that combines a TEE attestation arm and a ZK proof arm. A single un-nullified proof of either type can resolve a game (PROOF_THRESHOLD = 1). When both arms commit, the finalization window collapses from SLOW_FINALIZATION_DELAY (5d) to FAST_FINALIZATION_DELAY (1d).
Stateless verifier that validates AggregateVerifier TEE proofs by recovering an ECDSA signature over the journal and checking the recovered signer against TEEProverRegistry. Enforces PCR0 match by comparing the signer’s registered image hash to the AggregateVerifier’s TEE_IMAGE_HASH. Can be permanently nullified by a successful AggregateVerifier.nullify call.
Set verifier contract for RISC Zero proofs (version 0.9.0). It allows verifying a whole set of proofs identified with a Merkle root at once, afterwards each individual proof could be efficiently verified just by checking Merkle inclusion against the verified root.
Same as FaultDisputeGame, but only two permissioned addresses are designated as proposer and challenger.
Contract designed to hold the bonded ETH for each game. It is designed as a wrapper around WETH to allow an owner to function as a backstop if a game would incorrectly distribute funds.
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig
Simple escrow that accepts tokens and allows to configure permissioned addresses that can access the tokens.
ZK-based verifier of AWS Nitro Enclave attestation documents. Used by TEEProverRegistry to validate new enclave signer registrations against the AWS Nitro PKI.
A router proxy that routes to verifiers based on selectors. The mapping can be changed by a permissioned owner (TimelockController).
- Roles:
- owner: TimelockController; ultimately Safe
Contains the latest confirmed state root that can be used as a starting point in a dispute game. This variant stores respectedGameType, retirementTimestamp, and disputeGameFinalityDelaySeconds locally and drops the legacy *FromGame fields, since the AggregateVerifier model does not expose vm()/weth()/absolutePrestate() on its game implementation.
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig
Escrow for custom external tokens that use the canonical bridge for messaging but are governed externally.
Custom bridge for USDS and sUSDS managed by Sky governance.
Thin router that forwards SP1 ZK proof verification from the AggregateVerifier game to the SP1 verifier gateway. Can be permanently nullified by a successful AggregateVerifier.nullify call.
Contract designed to hold the bonded ETH for each game. It is designed as a wrapper around WETH to allow an owner to function as a backstop if a game would incorrectly distribute funds.
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig
Base Chain
Contract used to disburse funds from system FeeVault contracts, shares revenue with Optimism and bridges the rest of funds to L1.
- Roles:
- admin: EOA 2
The L2CrossDomainMessenger (L2xDM) contract sends messages from L2 to L1, and relays messages from L1 onto L2 with a system tx. In the event that a message sent from L2 to L1 is rejected for exceeding the L1 gas limit, it can be resubmitted via this contract’s replay function.
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig - L2 Alias
Contracts to register schemas for the Ethereum Attestation Service (EAS).
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig - L2 Alias
Contract containing the main logic for the Ethereum Attestation Service (EAS).
- Roles:
- admin: ProxyAdmin; ultimately Base Governance Multisig - L2 Alias
The current deployment carries some associated risks:
Funds can be stolen if a contract receives a malicious code upgrade. Upgrades must be approved by 2 parties: the Base Coordinator Multisig and the Base Security Council. There is no delay on upgrades.
Base Chain