Search

Search for projects by name

X Layer logoX Layer

Badges

About

X Layer is a Layer 2 by OKX with seamless integration with OKX products. It is powered by the Polygon CDK.


  • Total Value SecuredTVS
    $44.20 M13.0%
  • Past day UOPSDaily UOPS
    8.4239.8%
  • Gas token
    OKB
  • Type
    Other

  • Purpose
    Universal
  • Chain ID
    196

  • Tokens breakdown

    Value secured breakdown

    View TVS breakdown
    Sequencer failureState validationData availabilityExit windowProposer failure

    Badges

    About

    X Layer is a Layer 2 by OKX with seamless integration with OKX products. It is powered by the Polygon CDK.

    Why is the project listed in others?

    There are less than 5 external actors that can attest data availability

    Consequence: projects without a sufficiently decentralized data availability committee rely on few entities to safely attest data availability on Ethereum. A small set of entities can collude with the proposer to finalize an unavailable state, which can cause loss of funds.

    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.

    2024 Aug 29 — 2025 Aug 28


    Total
    $44.20 M13.0%
    Canonically BridgedCanonically Bridged ValueCanonical
    $44.20 M13.0%
    Natively MintedNatively Minted TokensNative
    $0.000.00%
    Externally BridgedExternally Bridged ValueExternal
    $0.000.00%

    ETH & derivatives
    $15.67 M35.1%
    Stablecoins
    $27.78 M3.31%
    BTC & derivatives
    $719.87 K28.5%
    Other
    $23.50 K62.0%

    2024 Aug 28 — 2025 Aug 27

    Migration to Pessimistic Proofs

    2025 Aug 5th

    X Layer stops validating the full L2 state and moves to bridge accounting proofs.

    Learn more

    X Layer Public Launch

    2024 Apr 16th

    X Layer is live on mainnet, integrated with Agglayer.

    Learn more
    Sequencer failureState validationData availabilityExit windowProposer failure
    Sequencer failure
    No mechanism

    There is no mechanism to have transactions be included if the sequencer is down or censoring.

    State validation
    None

    Currently the system permits invalid state roots. ‘Pessimistic’ proofs only validate the bridge accounting.

    Data availability
    External

    Proof construction and state derivation rely fully on data that is NOT published onchain.

    Exit window
    None

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

    Proposer failure
    Cannot withdraw

    Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.

    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner

    Ethereum

    Roles:

    Trusted Aggregator (Proposer) (2) 0x20A5…51dE0x6329…f7ab

    Permissioned to post new state roots and global exit roots accompanied by ZK proofs.

    Actors:

    PolygonAdminMultisig 0x242d…3e21

    A Multisig with 5/12 threshold.

    • Can upgrade with 3d delay
      • AggLayerGateway
      • PolygonSharedBridge
      • PolygonRollupManager
      • PolygonGlobalExitRootV2
    • Can interact with AggLayerGateway
      • add new routes from proof selector to verifier / pessimisticVkey for pessimistic proofs with 3d delay
      • add or update default aggchain verification keys (aggchainVkey) for any given selectors
      • freeze routes from proof selector to verifier / pessimisticVkey for pessimistic proofs
    • Can interact with PolygonSharedBridge
      • upgrade the implementation of wrapped tokens deployed by the bridge with 3d delay
    • Can interact with PolygonRollupManager
      • deploy new projects that use predefined rollup types (implementations) and connect them or other Agglayer chains to the PolygonRollupManager
      • manage all access control roles, add new rollup types (which are implementation contracts that can then be upgraded to by connected projects), update any connected projects to new rollup types, migrate to pessimistic proofs and rollback batches, connect existing rollups to the PolygonRollupManager with 3d delay
      • manage parameters like fees for all connected projects, set the trusted aggregator, stop the emergency state, update projects and obsolete rollup types
    • Can interact with Timelock
      • propose, cancel and execute transactions in the timelock, manage all access control roles and change the minimum delay with 6d delay or with 3d delay
    Used in:
    PolygonSecurityCouncil 0x37c5…Dcb6

    A Multisig with 6/8 threshold.

    • Can interact with PolygonRollupManager
      • activate the emergency state in the PolygonRollupManager and in the shared bridge immediately, effectively pausing all projects connected to them and making system contracts instantly upgradable
    Used in:
    PolygonCreateRollupMultisig 0xC74e…79dB

    A Multisig with 3/8 threshold.

    • Can interact with PolygonRollupManager
      • deploy new projects that use predefined rollup types (implementations) and connect them or other Agglayer chains to the PolygonRollupManager
    Used in:
    • Can interact with PolygonPessimisticConsensus
      • sole address that can force batches
    • Can interact with PolygonPessimisticConsensus
      • must provide a signature for each pessimistic proof, attesting to a valid state transition
    • Can interact with PolygonPessimisticConsensus
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner

    Ethereum

    System contract defining the X Layer logic. It only enforces bridge accounting (pessimistic) proofs and is otherwise kept minimal as the layer 2 state transitions are not proven.

    • Roles:
      • admin: EOA 3
      • forceBatchAddress: EOA 1
      • trustedSequencer: EOA 2

    A verifier gateway for pessimistic proofs. Manages a map of chains and their verifier keys and is used to route proofs based on the first 4 bytes of proofBytes data in a proof submission. The SP1 verifier is used for all proofs.

    • Roles:
      • addPpRoute: Timelock; ultimately PolygonAdminMultisig
      • admin: SharedProxyAdmin; ultimately PolygonAdminMultisig
      • aggchainDefaultVKey: PolygonAdminMultisig
      • freezePpRoute: PolygonAdminMultisig
    Proxy used in:

    The shared bridge contract, escrowing user funds sent to Agglayer participants. It is usually mirrored on each chain and can be used to transfer both ERC20 assets and arbitrary messages.

    • Roles:
      • admin: SharedProxyAdmin; ultimately PolygonAdminMultisig
      • proxiedTokensManager: Timelock; ultimately PolygonAdminMultisig
    • This contract can store any token.
    Proxy used in:

    The central shared managing contract for Polygon Agglayer chains. This contract coordinates chain deployments and proof validation. All connected Layer 2s can be globally paused by activating the ‘Emergency State’. This can be done by the PolygonSecurityCouncil or by anyone after 1 week of inactive verifiers.

    • Roles:
      • admin: SharedProxyAdmin; ultimately PolygonAdminMultisig
      • createRollup: PolygonAdminMultisig, PolygonCreateRollupMultisig
      • defaultAdmin: Timelock; ultimately PolygonAdminMultisig
      • emergencyCouncilAdmin: PolygonSecurityCouncil
      • trustedAggregator: EOA 4, EOA 5
      • tweakParameters: PolygonAdminMultisig
    Proxy used in:

    A merkle tree storage contract aggregating state roots of each participating Layer 2, thus creating a single global merkle root representing the global state of the Agglayer, the ‘global exit root’. The global exit root is synchronized to all connected Layer 2s to help with their interoperability.

    • Roles:
      • admin: SharedProxyAdmin; ultimately PolygonAdminMultisig
    Proxy used in:
    Timelock 0xEf14…A4EF

    A timelock with access control. In the case of an activated emergency state in the PolygonRollupManager, all transactions through this timelock are immediately executable. The current minimum delay is 3d.

    • Roles:
      • timelockAdmin: PolygonAdminMultisig (no delay if in emergency state), Timelock (no delay if in emergency state); ultimately PolygonAdminMultisig (no delay if in emergency state)
    Implementation used in:
    SP1Verifier 0x0459…C459

    Verifier contract for SP1 proofs (v5.0.0).

    Implementation used in:
    SharedProxyAdmin 0x0F99…CC4A
    • Roles:
      • owner: Timelock
    Implementation used in:

    Value Secured is calculated based on these smart contracts and tokens:

    Proxy used in:

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