Search

Search projects, tokens and protocols by name or address

Badges

About

Whitechain is an Optimistic rollup based on the OP Stack, built by the WhiteBIT exchange. It migrated from an independent PoA chain to a Layer 2 in October 2026, keeping WBT as the custom gas token.


  • Total Value SecuredTVS
    $460.53 M3.67%
  • Past day UOPSDaily UOPS
    <0.010.00%
  • Gas token
    WBT
  • Type
    Other

  • Purpose
    Universal
  • Chain ID
    1875

  • Tokens breakdown

    Sequencer failureState validationData availabilityExit windowProposer failure

    Badges

    About

    Whitechain is an Optimistic rollup based on the OP Stack, built by the WhiteBIT exchange. It migrated from an independent PoA chain to a Layer 2 in October 2026, keeping WBT as the custom gas token.

    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.


    Total
    Canonically BridgedCanonically Bridged ValueCanonical
    Natively MintedNatively Minted TokensNative
    Externally BridgedExternally Bridged ValueExternal

    ETH & derivatives
    Stablecoins
    BTC & derivatives
    Other
    Compare with other projects
    Past Day UOPS
    Past Day Ops count
    Max. UOPS
    Past day UOPS/TPS Ratio
    Compare with other projects

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



    Total cost
    Avg cost per L2 UOP
    Avg cost per day

    Compare with other projects

    This section shows how much data the project publishes to Ethereum over time. It leaves out data posted to other data-availability (DA) layers. The project currently posts data toEthereumEthereum.



    Data posted
    Avg size per day
    Avg size per L2 UOP

    Compare with other projects

    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

    Avg. tx data subs. interval
    Avg. state updates interval
    Past 30 days anomalies
    100% normal uptime

    Whitechain migrates to an Ethereum L2

    26 Oct 2026

    The legacy Whitechain PoA chain becomes an OP Stack rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup., keeping WBT as gasA virtual fuel used to execute smart contracts on a rollup. The EVM (or other VM within the rollup) uses an accounting mechanism to correspond the consumption of gas to the consumption of computing resources, and to limit the consumption of computing resources. token.

    Learn more
    The fault proof systemThe infrastructure that allows projects to verify their state transitions. It is composed by onchain verifiers and offchain provers. The main two flavors are optimistic and ZK proof systems, but they can be combined in a hybrid model. In general though, if a system is able to accept state roots optimistically, even if it has a ZK component, it is considered an optimistic proof system. is deployed but is not functional. The respected game type is the super permissioned game, which runs no VM and exposes no challenger, bond or challenge clock, so no dispute can be resolved by execution. Security relies entirely on the permissioned proposerIn the context of L2s, the actor that proposes a claimed state root on L1. The term is also used in the context of Ethereum to refer to the actor that proposes a new block., with the Guardian able to blacklist games and change the respected game type.
    The fault proof systemThe infrastructure that allows projects to verify their state transitions. It is composed by onchain verifiers and offchain provers. The main two flavors are optimistic and ZK proof systems, but they can be combined in a hybrid model. In general though, if a system is able to accept state roots optimistically, even if it has a ZK component, it is considered an optimistic proof system. is deployed but is not functional. The respected game type is the super permissioned game, which runs no VM and exposes no challenger, bond or challenge clock, so no dispute can be resolved by execution. Security relies entirely on the permissioned proposerIn the context of L2s, the actor that proposes a claimed state root on L1. The term is also used in the context of Ethereum to refer to the actor that proposes a new block., with the Guardian able to blacklist games and change the respected game type.
    Sequencer failureState validationData availabilityExit windowProposer failure
    Sequencer failure
    Self sequence

    In the event of a sequencerA party responsible for ordering and executing transactions on the rollup. The sequencer verifies transactions, compresses the data into a block, and submits the data related to it to enable state reconstruction to Ethereum L1 as a single transaction. The data can be either transaction data or state diffs. failure, users can force transactions to be included in the project’s chain by sending them to L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development.. There can be up to a 12h delay on this operation.

    State validation
    None

    State rootsA cryptographic hash succinctly representing a state using a Merkle tree. are proposed as super roots by a permissioned proposerIn the context of L2s, the actor that proposes a claimed state root on L1. The term is also used in the context of Ethereum to refer to the actor that proposes a new block.. The respected game type exposes no challenger, VM or challenge clock, so proposals cannot be disputed by execution. Validity is governed by the AnchorStateRegistry, and the Guardian can blacklist games and change the respected game type.

    Data availability
    Onchain

    All of the data needed for proof construction is published on Ethereum L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development..

    Exit window
    None

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

    Proposer failure
    Cannot withdraw

    Only the whitelisted proposers can publish state rootsA cryptographic hash succinctly representing a state using a Merkle tree. on L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development., so in the event of failure the withdrawals are frozen.

    Whitechain
    Whitechain is not even a
    Stage 0
    project.
    The requirement for available nodeA software client that participates in the network. software is under review

    Learn more about Stages
    Please keep in mind that these stages do not reflect project security, this is an opinionated assessment of project 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.

    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 blobsThe data that a rollup publishes to its L1/data availability (DA) layer. They consist of the L2 transactions that are rolled up, along with some metadata. Blobs are introduced as a new transaction type within Ethereum with EIP-4844, and has rollup scaling specifically in mind. Blobs persist on Ethereum’s Beacon Chain ephemerally. or calldata. This ensures that it will be available for enough time.

    1. Derivation: Batch submission - OP Mainnet specs
    2. BatchInbox - address
    3. OptimismPortal2.sol - source code, depositTransaction function
    Learn more about the DA layer here: Ethereum logoEthereum

    State rootsA cryptographic hash succinctly representing a state using a Merkle tree. are proposed as super roots by a permissioned proposerIn the context of L2s, the actor that proposes a claimed state root on L1. The term is also used in the context of Ethereum to refer to the actor that proposes a new block.. The respected game type is the super permissioned game, which carries no bond and exposes no challenge mechanics: validity is governed by the AnchorStateRegistry, and the Guardian can blacklist games and change the respected game type.


    State root proposals

    Only the permissioned proposerIn the context of L2s, the actor that proposes a claimed state root on L1. The term is also used in the context of Ethereum to refer to the actor that proposes a new block. configured in the dispute game factory can create games of the respected type. Each proposal commits to a super root anchored to an L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups. timestamp rather than an L2 blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. number.

    Past upgrades

    The metrics include upgrades on the currently used proxy contracts. Historical proxy contracts and changes of such are not included.

    Count of upgrades
    8
    Last upgrade
    8d 18h ago
    Avg upgrade interval
    4d 9h
    17changes

    Initial discovery of Whitechain, an OP Stack L2 on op-contracts v8.0.0 (Upgrade 20) with the custom gas token feature enabled and the super permissioned game (type 5) respected.

    Initial discovery

    + Status: CREATED
    contract ProxyAdmin (eth:0x0390F00fD57E771Afa19630B4ad8CE68ddA73506) [global/ProxyAdmin]
    +++ description: None
    + Status: CREATED
    contract OptimismPortal2 (eth:0x0665f74e013b7FCcfDa6dAF8951bAf3C982a3864) [opstack/OptimismPortal2]
    +++ description: The OptimismPortal contract is the main entry point to deposit funds from L1 to L2. It also allows to prove and finalize withdrawals. It specifies which game type can be used for withdrawals, which currently is the SuperPermissionedDisputeGame.
    + Status: CREATED
    contract OptimismMintableERC20Factory (eth:0x149a093e8Fe94610586e068739E929723Ac0Cd1A) [opstack/OptimismMintableERC20Factory]
    +++ description: 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.
    + Status: CREATED
    contract SystemConfig (eth:0x1D761826ad3098D10f6dDfbd143957Aaf2b6e50C) [opstack/SystemConfig]
    +++ description: Contains configuration parameters such as the Sequencer address, gas limit on this chain and the unsafe block signer address.
    + Status: CREATED
    contract DisputeGameFactory (eth:0x1De4f415Dc5bF6e458Cf32d13452c24A35Ec90e3) [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.
    + Status: CREATED
    contract SuperchainConfig (eth:0x35aB61eE5D1C2319d1822A7bE1b6B3FaE98AD886) [opstack/SuperchainConfigFake_expiry]
    +++ description: This is NOT the shared SuperchainConfig contract of the OP stack Superchain but rather a local fork. It manages pause states for each chain connected to it, as well as a global pause state for all chains. The guardian role can pause either separately, but each pause expires after 3mo 1d if left untouched.
    + Status: CREATED
    contract Whitechain Multisig 1 (eth:0x568440132075d4E1c3E42111EF561636f4956eAd) [GnosisSafe]
    +++ description: None
    + Status: CREATED
    contract L1CrossDomainMessenger (eth:0x589cD6dEd71Cf4867351E86507A1Ce81Bde0Bc9C) [opstack/L1CrossDomainMessenger]
    +++ description: 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.
    + Status: CREATED
    contract Whitechain Multisig 3 (eth:0x5918870d5391e0610d7624837cABEd9d4AbEeeE0) [GnosisSafe]
    +++ description: None
    + Status: CREATED
    contract SuperPermissionedDisputeGame (eth:0x5C3eb47cB0174aea522a2a9Ae79487139A53D691) [opstack/SuperPermissionedDisputeGame]
    +++ description: Logic of the permissioned dispute game introduced in Upgrade 20. Only the proposer configured in the DisputeGameFactory can create games of this type, and each one commits to a super root anchored to an L2 timestamp. Unlike the permissioned game it replaces, it runs no VM and exposes no challenger, bond, clock or absolute prestate: validity is governed by the AnchorStateRegistry and the Guardian.
    + Status: CREATED
    contract AddressManager (eth:0x7b806b8A81Ba1D4d2Df62180147e40F32f1eeb49) [opstack/AddressManager]
    +++ description: Legacy contract used to manage a mapping of string names to addresses. Modern OP stack uses a different standard proxy system instead, but this contract is still necessary for backwards compatibility with several older contracts.
    + Status: CREATED
    contract L1ERC721Bridge (eth:0x7b854CBa91d3B788bc311e2326E203C0f46dB3Fe) [opstack/L1ERC721Bridge]
    +++ description: Used to bridge ERC-721 tokens from host chain to this chain.
    + Status: CREATED
    contract L1StandardBridge (eth:0x7e954f20F24b7988EA966C4E7880fe6D21dCc2D9) [opstack/L1StandardBridge]
    +++ description: The main entry point to deposit ERC20 tokens from host chain to this chain.
    + Status: CREATED
    contract AnchorStateRegistry (eth:0x860801a7766859B82b0B572f75a56d4D3903B23a) [opstack/AnchorStateRegistry_post20]
    +++ description: 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.
    + Status: CREATED
    contract Whitechain Multisig 2 (eth:0x8da4Ce0f49E472fb6F892c779b3E63C7a55B23aF) [GnosisSafe]
    +++ description: None
    + Status: CREATED
    contract ProxyAdmin (eth:0x9419a57179dEF1FBdb8e7859756e85ad0ae396c7) [global/ProxyAdmin]
    +++ description: None
    + Status: CREATED
    contract DelayedWETH (eth:0x99BbebAea69666405A8e19dF5d185fecC6BF46Fe) [opstack/DelayedWETH]
    +++ description: 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.

    The system has a centralized operator

    The operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. is the only entity that can propose blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over.. A live and trustworthy operator is vital to the health of the system.

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

    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.

    1. Sequencing Window - OP Mainnet Specs
    2. OptimismPortal2.sol - source code, depositTransaction function

    Regular exits

    The user initiates the withdrawal by submitting a regular transaction on this chain. When a state rootA cryptographic hash succinctly representing a state using a Merkle tree. containing such transaction is settled, the funds become available for withdrawal on L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. after 3d 12h. Withdrawal inclusion can be proven before state root settlementThe mechanism with which the execution of rollup blocks and the resultant state is verified and possible disputes are resolved. In the context of rollups or other modular blockchains, it often refers to the proof system used--validity (ZK) or fraud proofs, or a combination thereof. Sometimes it will refer to this mechanism along with where the mechanism's outputs are ultimately published and verified, as in Ethereum being a settlement layer by verifying the proofs and allowing for withdrawals., but a 7d period has to pass before it becomes actionable. The respected game type carries no on-chain challenge process, so settlement waits only for the delays above. Finally the user submits an L1 transaction to claim the funds. This transaction requires a merkle proof.

    1. OptimismPortal2.sol - Etherscan source code, proveWithdrawalTransaction function
    2. OptimismPortal2.sol - Etherscan source code, finalizeWithdrawalTransaction function

    Forced messaging

    If the user experiences censorship from the operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. with regular L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups.->L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. 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.

    1. Forced withdrawal from an OP Stack blockchain

    EVM compatible smart contracts are supported

    OP stack chains are pursuing the EVM EquivalenceA perfect degree of compatibility; where one system or concept is indistinguishable from another in the domain being compared. In the context of rollups, it generally refers to the proximity to the EVM and to Ethereum architecture. model. No changes to smart contracts are required regardless of the language they are written in, i.e. anything deployed on L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. can be deployed on L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups..

    1. Introducing EVM Equivalence

    Migrated gas token and external bridge

    The custom gasA virtual fuel used to execute smart contracts on a rollup. The EVM (or other VM within the rollup) uses an accounting mechanism to correspond the consumption of gas to the consumption of computing resources, and to limit the consumption of computing resources. token feature is enabled on the SystemConfig, so the OptimismPortal accepts no ETH and WBT has no canonical representation on Ethereum. The WBT balances of the legacy chain were copied into the L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups. genesis, together with a reserve held by the NativeAssetLiquidity predeploy. The reserve can only be released through the LiquidityController predeploy, whose owner is the L2 alias of the L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. ProxyAdmin owner. Assets move between Ethereum, Tron and Whitechain mostly through the Portal, a bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge. operated by Whitechain in which a single relayer key authorizes every release and an operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. multisig can withdraw the pooled liquidity.

    • Funds can be stolen if the LiquidityController owner releases WBT from the NativeAssetLiquidity reserve without a matching deposit on another chain.

    1. Migration to L2 - Whitechain docs
    2. Portal bridge - Whitechain docs
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner

    Ethereum

    Actors:

    Whitechain Multisig 10x5684…6eAd

    A Multisig with 3/5 threshold.

    • Can upgrade with no delay
      • OptimismPortal2
      • OptimismMintableERC20Factory
      • SystemConfig
      • DisputeGameFactory
      • SuperchainConfig
      • L1CrossDomainMessenger
      • L1ERC721Bridge
      • L1StandardBridge
      • AnchorStateRegistry
      • DelayedWETH
    • Can interact with DisputeGameFactory
      • set the dispute game implementation and initial bond for any game type
    • Can interact with AddressManager
      • set and change address mappings
    Whitechain Multisig 20x8da4…23aF

    A Multisig with 3/5 threshold.

    • Can interact with SystemConfig
      • it can update the preconfer address, the batch submitter (SequencerA party responsible for ordering and executing transactions on the rollup. The sequencer verifies transactions, compresses the data into a block, and submits the data related to it to enable state reconstruction to Ethereum L1 as a single transaction. The data can be either transaction data or state diffs.) address and the gasA virtual fuel used to execute smart contracts on a rollup. The EVM (or other VM within the rollup) uses an accounting mechanism to correspond the consumption of gas to the consumption of computing resources, and to limit the consumption of computing resources. configuration of the system
    Whitechain Multisig 30x5918…eeE0

    A Multisig with 3/5 threshold.

    • Can interact with SuperchainConfig
      • Allowed to pause withdrawals. In op stack systems with a proof systemThe infrastructure that allows projects to verify their state transitions. It is composed by onchain verifiers and offchain provers. The main two flavors are optimistic and ZK proof systems, but they can be combined in a hybrid model. In general though, if a system is able to accept state roots optimistically, even if it has a ZK component, it is considered an optimistic proof system., the Guardian can also blacklist dispute games and set the respected game type (permissioned / permissionlessAnyone willing should be able to join and leave the network at any time, without causing significant disturbance to the network or being detrimental to the party in question. No single entity should have the power to allowlist or blocklist participants.)
    • Can interact with DisputeGameFactory
      • Allowed to post new state rootsA cryptographic hash succinctly representing a state using a Merkle tree. of the current layer to the host chain
    • Can interact with SystemConfig
      • Allowed to commit transactions from the current layer to the host chain
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    A diagram of the smart contract architecture
    A diagram of the smart contract architecture

    Ethereum

    The OptimismPortal contract is the main entry point to deposit funds from L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. to L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups.. It also allows to prove and finalize withdrawals. It specifies which game type can be used for withdrawals, which currently is the SuperPermissionedDisputeGame.

    • Roles:
      • admin: ProxyAdmin; ultimately Whitechain Multisig 1
    The following tokens are included in the value secured calculation:
    ETH token logo
    Implementation used in:
    Ink logoOP Mainnet logoSoneium logoUnichain logo

    Contains configuration parameters such as the SequencerA party responsible for ordering and executing transactions on the rollup. The sequencer verifies transactions, compresses the data into a block, and submits the data related to it to enable state reconstruction to Ethereum L1 as a single transaction. The data can be either transaction data or state diffs. address, gas limitThe maximum amount of gas a transaction or block may consume. on this chain and the unsafe blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. signer address.

    • Roles:
      • admin: ProxyAdmin; ultimately Whitechain Multisig 1
      • batcherHash: EOA 2
      • owner: Whitechain Multisig 2
    Implementation used in:
    Ink logoOP Mainnet logoSoneium logoUnichain logo

    The dispute game factory allows the creation of dispute games, used to propose state rootsA cryptographic hash succinctly representing a state using a Merkle tree. 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 Whitechain Multisig 1
      • game5Proposer: EOA 1
      • owner: Whitechain Multisig 1
    Implementation used in:
    Aevo logoBOB logoInk logoMetal logo

    This is NOT the shared SuperchainConfig contract of the OP stack Superchain but rather a local fork. It manages pause states for each chain connected to it, as well as a global pause state for all chains. The guardian role can pause either separately, but each pause expires after 3mo 1d if left untouched.

    • Roles:
      • admin: ProxyAdmin; ultimately Whitechain Multisig 1
      • guardian: Whitechain Multisig 3
    Implementation used in:
    Celo logoCyber logoFunki logoInk logo

    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 limitThe maximum amount of gas a transaction or block may consume., it can be resubmitted via this contract’s replay function.

    • Roles:
      • admin: ProxyAdmin; ultimately Whitechain Multisig 1
    Implementation used in:
    Aevo logoBOB logoInk logoMetal logo

    Used to bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge. ERC-721 tokens from host chain to this chain.

    • Roles:
      • admin: ProxyAdmin; ultimately Whitechain Multisig 1
    Implementation used in:
    Aevo logoBOB logoInk logoMetal logo

    The main entry point to deposit ERC20 tokens from host chain to this chain.

    • Roles:
      • admin: ProxyAdmin; ultimately Whitechain Multisig 1

    All supported tokens in this escrow are included in the value secured calculation.

    Implementation used in:
    Aevo logoBOB logoInk logoMetal logo
    ProxyAdmin
    2 instances
    0x0390…35060x9419…96c7
    • Roles:
      • owner: Whitechain Multisig 1

    A helper contract that generates OptimismMintableERC20 contracts on the networkA constellation of nodes (peers) that communicate via a peer-to-peer protocol, for example, in propagating transactions and blocks to other nodes. 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 Whitechain Multisig 1
    Implementation used in:
    Aevo logoBOB logoInk logoMetal logo
    SuperPermissionedDisputeGame0x5C3e…D691

    Logic of the permissioned dispute game introduced in Upgrade 20. Only the proposerIn the context of L2s, the actor that proposes a claimed state root on L1. The term is also used in the context of Ethereum to refer to the actor that proposes a new block. configured in the DisputeGameFactory can create games of this type, and each one commits to a super root anchored to an L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups. timestamp. Unlike the permissioned game it replaces, it runs no VM and exposes no challenger, bond, clock or absolute prestate: validity is governed by the AnchorStateRegistry and the Guardian.

    Implementation used in:
    Ink logoOP Mainnet logoSoneium logoUnichain logo

    Contains the latest confirmed state rootA cryptographic hash succinctly representing a state using a Merkle tree. 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 Whitechain Multisig 1
    Implementation used in:
    Ink logoKatana logoMetal logoMode Network logo

    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 Whitechain Multisig 1
    Implementation used in:
    Ink logoKatana logoMetal logoMode Network logo

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