Search

Search projects, tokens and protocols by name or address

There are impactful changes and part of the information might be outdated.

Badges

About

Katana is a Layer 2 specializing on DeFi. Its unique architecture combines an OP stack base with Agglayer shared bridge interoperability and OP-Succinct SP1 validity proofs.



Badges

About

Katana is a Layer 2 specializing on DeFi. Its unique architecture combines an OP stack base with Agglayer shared bridge interoperability and OP-Succinct SP1 validity proofs.


Total
Canonically bridgedCanonically bridged valueCanonical
Natively mintedNatively minted tokensNative
Externally bridgedExternally bridged valueExternal

ETH & derivatives
Stablecoins
BTC & derivatives
Other
Compare with other projects
Avg value per second, all flows shown ≈ $7.69 K/s1 particle ≈ $150
Chain stats
StatsLast 24h · 15 of 26 chains
Total volume
$2.02 M
Volume in
$27.16 K
Volume out
$1.99 M
Net flow
−$1.97 M
Total transfers
71
Unique tokens
8
Transfers in
32
Transfers out
39
Avg. transfer value
$28.54 K
Avg. transfer time
45m 18s
Connected
9 chains
Avg. value per second
$23.45/s
Top routes
Transfer size
Under $100
$100–$1K
$1K–$10K
$10K–$100K
Over $100K
Transfer type distribution

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 to EthereumEthereum.



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 submission interval
Avg proof submission interval
Avg state update interval
Anomalies in the past 30 days
99% normal uptime

Anomalies in the past 30 days

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 2h 23m (from until ). These typically occur every 7m 52s on average.

No Tx data submissions were performed for 15m 48s (from until ). These typically occur every 7m 52s on average.

No Tx data submissions were performed for 20m (from until ). These typically occur every 7m 52s on average.

Katana Launch

1 Jul 2025

Katana is live on mainnet, integrated with Agglayer.

Learn more
Sequencer failureState validationData availabilityExit windowProposer failure
Sequencer failure
Self sequence
The self-sequencing delay is configured offchain and the nodeA software client that participates in the network. source and config are unverified.

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
Validity proofs (ST, SN)

STARKs and SNARKs are zero knowledge proofs that ensure state correctness. STARKs proofs are wrapped in SNARKs proofs for efficiency. SNARKs require a trusted setupGeneration of a piece of data that must then be used for some cryptographic protocol to run. Generating this data requires some secret information. The "trust" comes from the fact the secret must be destroyed after the ceremony, otherwise cryptographic properties of the protocol could be broken. Once the data is generated, and the secrets are forgotten, no further participation from the creators of the ceremony is required. There are two types of trusted setups for SNARKs: (i) trusted setup per circuit where it is generated from scratch for each circuit, (ii) trusted universal setup per proving system where it can be used for several circuits..

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
Even though there is a 3d Timelock for non-emergency upgrades, self-proposing is disabled.

There is no window for users to exit in case of an unwanted upgrade since the Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and ETHBEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups. can remove the delay on upgrades.

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.

Katana
Katana is a
Stage 0
ZK Rollup.
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. batchInbox - Etherscan address
Learn more about the DA layer here: Ethereum logoEthereum
Prover Architecture

Katana uses the Agglayer CDK in CDK-opgeth-zkrollup configuration. This combines an OP-Succinct zk 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. base with Agglayer shared 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. interoperabilityRefers to the capability of different blockchain networks to communicate and share data. It enables the transfer of assets and information between blockchains, facilitating functionality and collaboration between blockchain ecosystems.. Both parts are verified in a single nested proof using the Succinct Sp1Verifier. This proof is called the pessimistic proof by Agglayer which contains 1) the bridge accounting proof proving only the secure accounting of the Agglayer shared bridge and can have 2) a reference to an ‘aggchain proof’, which can define additional programs to be proven. In the case of Katana, these are the op-succinct 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. range proofs as an aggregated proof proving the state transitions of 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., resulting in a full validity proofThe output of a cryptographic proving system attesting to correct computation. ZK-Rollups use succinct validity proofs (also called zero-knowledge proofs) to prove a batch of rollup transactions and blocks were properly executed. Validity proofs are submitted to a verifier, such as an Ethereum smart contract, which accepts them if properly constructed. of L2 execution and agglayer bridge accounting.

  1. CDK-opgeth-zkrollup architecture
Validity proofs

Each update to the 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. state must be accompanied by a ZK proof that ensures that the new state was derived by correctly applying a series of valid user transactions to the previous state. These proofs are then verified on Ethereum by a smart contract.

  • Funds can be stolen if the state transition validity proof cryptography is broken or implemented incorrectly.

  • Funds can be stolen if A malicious state transition is finalized by activating the permissioned optimistic mode.

  • Funds can be stolen if the proposer routes proof verification through a malicious or faulty verifier by specifying an unsafe route id.

  • Funds can be frozen if the AggLayerGateway is unable to route proof verification to a valid verifier.

  1. Op-Succinct architecture
Pessimistic Proofs

The pessimistic proofs that are used to prove correct accounting in the Agglayer shared 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. (minimum security guarantee) are using the SP1 zkVM by Succinct.

  • Funds can be stolen if the pessimistic proof cryptography is broken or implemented incorrectly.

Prover

Trusted setups

Onchain verifier

Used in

X Layer logoKatana logoHaust Network logoLumia Prism logo

Onchain verifier

Used in

X Layer logoKatana logoHaust Network logoLumia Prism logo

Program hashes

Hash
Repository
Verification
Used in
0x0007...363b
Katana logo
0x5ae1...75b1
Katana logo
0x713f...fa1f
Katana logo
0x374e...dac6
Katana logo
0x6e38...1b53
Katana logo
0x7767...6f70
Katana logo
0x679b...7915
Katana logo
0x00ef...cc30
X Layer logoKatana logoHaust Network logoLumia Prism logo
0x0000...b639
X Layer logoKatana logoHaust Network logoLumia Prism logo
0x00d1...578e
X Layer logoKatana logoHaust Network logoLumia Prism logo

Scroll sideways to see the whole diagram, or tap to open it.

A diagram of the upgrades and governance

The regular upgrade process for all system contracts (shared and 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.-specific) starts at the PolygonAdminMultisig. For the shared contracts, they schedule a transaction that targets the ProxyAdmin via the Timelock, wait for 3d and then execute the upgrade. An upgrade of the Layer 2 specific 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.- or validiumAn off-chain solution that uses validity proofs for settlement and publishes the data offchain, therefore requiring an additional trust assumption. contract requires first adding a new rollupType through the Timelock and the AgglayerManager (defining the new implementation and verifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. contracts). Now that the rollupType is created, either the local admin or the PolygonAdminMultisig can immediately upgrade the local system contracts to it.

The PolygonSecurityCouncil can expedite the upgrade process by declaring an emergency state. This state pauses both the shared 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. and the AgglayerManager and allows for instant upgrades through the timelock. Accordingly, instant upgrades for all system contracts are possible with the cooperation of the SecurityCouncil. The emergency state has been activated 1 time(s) since inception.

Furthermore, the PolygonAdminMultisig is permissioned to manage the shared trusted aggregator (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. and proverAn entity that generates the cryptographic proof to convince the verifier that the statement is true. In a ZK-Rollup, the prover generates the ZK (validity) proof to submit to the verifier contract.) for all participating Layer 2s, deactivate the emergency state, obsolete rollupTypes and manage operational parameters and fees in the AgglayerManager directly. The local admin of a specific Layer 2 can manage their chain by choosing the trusted 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., manage forced batches and set the data availabilityThe property of a rollup's data being reachable by any node retrieving the data that were rolled up and executed to reach the proposed state. Data availability (DA), specifically decoupling it from the rollup nodes themselves, is one of the preeminent factors which allows a rollup to scale securely. A rollup is faced with a decision of what to use as a DA layer to guarantee that any node can retrieve this data--permissionlessly under any circumstance. For this reason, using Ethereum for DA currently provides the strongest security guarantees. If data is stored somewhere other than a permissionless L1, then the project is not a rollup, but rather a validium or an optimium. config. Creating new Layer 2s (of existing rollupType) is outsourced to the PolygonCreateRollupMultisig but can also be done by the PolygonAdminMultisig. Finally, it can manage SP1 verification keys for pessimistic proofs and aggchain proofs, which defines the affected chains’ state validation. Custom non-shared bridge escrows have their custom upgrade admins listed in the permissions section.

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
58
Last upgrade
1mo 29d ago
Avg upgrade interval
4mo 2d

Ossification

Contracts our research team classifies as critical form the project's critical perimeter. Its clock starts at the ossification genesis, and every critical change resets it (changes within 24 hours count as one). The ossification score is the share of recorded code-bug exploits whose exploited code was younger than this perimeter is today. Battle-tested exposure is the value secured, summed over that unchanged period.

Ossification %
56since 30 Sep 2026
TVS & changes (1Y)
Battle-tested exposure
Battle-tested exposure
30 Sep — 22 Nov 2026
$48.81 M average TVS × 0.144 years unchanged.TVS now $37.66 M, peaking at $703.89 M over the past year.
Critical changes / year
21across 34 contracts
Exit window

Discovery updates

8changes

The Safe katana:0xd0673F989bc3BA9314d0AAF28BfC84e99B7898CC added a sixth signer with the threshold unchanged, now 3 of 6. It upgrades the L2 predeploys directly and the L2 bridge and exit root manager through the L2Timelock. Its signers now equal those of the Safe at the same address on Ethereum (Polygon Multisig 2, eth:0xd0673F989bc3BA9314d0AAF28BfC84e99B7898CC). The Safe eth:0x261a25ec6c396389B75B6b22BD4A8227070E3B50, which only receives the yield of the vault bridge tokens, removed two of its four owners and is now 1 of 2. One of its two owners, the Katana yieldRecipient Multisig, swapped one signer and stays 2 of 6. No code or threshold changes.

- Status: DELETED
EOA (eth:0x227D9Ea843910Edd305c42e7bB9Ce6D9f369238c)
+++ description: None
contract Safe (eth:0x261a25ec6c396389B75B6b22BD4A8227070E3B50) [GnosisSafe] {
+++ description: None
values.$members.0:
- "eth:0x3e86A8bcAF0A96DD16Ec8160532DA13b2C0f6e21"
values.$members.1:
- "eth:0x227D9Ea843910Edd305c42e7bB9Ce6D9f369238c"
values.multisigThreshold:
- "1 of 4 (25%)"
+ "1 of 2 (50%)"
}
- Status: DELETED
contract Safe (eth:0x3e86A8bcAF0A96DD16Ec8160532DA13b2C0f6e21) [GnosisSafe]
+++ description: None
contract Katana yieldRecipient Mulsitig (eth:0x67C912fF560951526BffDff66dFbD4DF8AE23756) [GnosisSafe] {
+++ description: None
values.$members.5:
- "eth:0x227D9Ea843910Edd305c42e7bB9Ce6D9f369238c"
+ "eth:0x73D8846324B30477EA3Ac055589e40F39DE497F8"
}
contract SafeL2 (katana:0xd0673F989bc3BA9314d0AAF28BfC84e99B7898CC) [GnosisSafe] {
+++ description: None
values.$members.0:
+ "katana:0x21a2Db679b4e9f6183E3143cc7Dcfef955b400a6"
values.multisigThreshold:
- "3 of 5 (60%)"
+ "3 of 6 (50%)"
}
8changes

Conduit Multisig 1 removed a member and is 4 of 10. The Safe eth:0xFA58659F64a393A6E1A548ABc70Ad2CfE1e8f9Cb, a member of the 1/4 Safe eth:0x261a25ec6c396389B75B6b22BD4A8227070E3B50, swapped three members and removed two, now 2 of 10. Thresholds are unchanged.

contract Conduit Multisig 1 (eth:0x4a4962275DF8C60a80d3a25faEc5AA7De116A746) [GnosisSafe] {
+++ description: None
values.$members.8:
- "eth:0xa0C600a6e85bf225958FFAcC70B5FDDF9A059038"
values.multisigThreshold:
- "4 of 11 (36%)"
+ "4 of 10 (40%)"
}
contract Safe (eth:0xFA58659F64a393A6E1A548ABc70Ad2CfE1e8f9Cb) [GnosisSafe] {
+++ description: None
values.$members.3:
- "eth:0x1319279d6d54dB0883F7bAF822191c7184Db0c3d"
+ "eth:0x97E3e9e9d5087CBf1fF5e7A68402F86e9C13B99b"
values.$members.6:
- "eth:0xF045025C845E786E343Df30cC6f67ec6BB822b34"
values.$members.7:
- "eth:0x6B2Ba82994A1606605af1F11E50DA0b2B0cee6e6"
+ "eth:0xb20d2bA1C74744a0Df7852f62BF802AbC8e4d91E"
values.$members.8:
- "eth:0x6624307a4f672ec5C289fBA196952902BB518dc0"
+ "eth:0x5F050BECf0746E4E95C4dB3254eA0E9a56268C0d"
values.$members.11:
- "eth:0xdEb97974dfCC73178672205A1eadDc2BDeAc1Bd4"
values.multisigThreshold:
- "2 of 12 (17%)"
+ "2 of 10 (20%)"
}
2changes

Polygon Multisig 2, the SystemConfig owner, raised the minimum L2 base fee from 0.001 to 0.05 gwei and the operator fee scalar from 100000 to 600000. Under Jovian the operator fee is gasUsed × scalar × 100 wei, so it rises from 0.01 to 0.06 gwei per gas. The minimum execution cost rises tenfold, from 0.011 to 0.11 gwei per gas, before the L1 data fee. Fee parameters only, no change to code or trust assumptions. The allocator EOA of the Morpho vault behind vbETH emptied the vault's supply queue, so it accepts no deposits. New ETH deposits (555 ETH, 21% of the vbETH backing) stay idle in the vbETH reserve and earn no yield. The vbETH reserve fields are now ignored in watch mode.

contract SystemConfig (eth:0xb6e1f8B589A14B79DDD3aD7F0589AB548c70C174) [opstack/SystemConfig] {
+++ description: Contains configuration parameters such as the Sequencer address, gas limit on this chain and the unsafe block signer address.
values.minBaseFee:
- 1000000
+ 50000000
values.operatorFeeScalar:
- 100000
+ 600000
}
2changes

The Polygon Labs Engineering/Security Multisig added an EOA signer and is now 2/8. It upgrades and administers the MigrationManager and is a signer of the three 2/3 Katana vaultBridge multisigs.

contract Polygon Labs Engineering/Security Multisig (eth:0x9d851f8b8751c5FbC09b9E74E6e68E9950949052) [GnosisSafe] {
+++ description: None
values.$members.0:
+ "eth:0xFD621b24968F64E3f14E7a099538ae13e1381417"
values.multisigThreshold:
- "2 of 7 (29%)"
+ "2 of 8 (25%)"
}
3changes

Yearn Strategist Multisig (a member of Katana vaultBridge Multisig 2) removed two signers, now 3 of 6.

contract Yearn Strategist Multisig (eth:0x16388463d60FFE0661Cf7F1f31a7D658aC790ff7) [GnosisSafe] {
+++ description: None
values.$members.3:
- "eth:0xFcc3796370e1538F8cC60bec19A8be5457f2C74F"
values.$members.4:
- "eth:0xFafFb75e14faFf9f11315E44a2E54A22872c7a34"
values.multisigThreshold:
- "3 of 8 (38%)"
+ "3 of 6 (50%)"
}

The system has a centralized operator

Only a trusted 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. is allowed to submit transaction batches. A mechanism for users to submit their own batches is currently disabled. Only a trusted 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. can propose and prove new state rootsA cryptographic hash succinctly representing a state using a Merkle tree..

  • Funds can be frozen if the permissioned proposer fails to publish state roots to the L1.

  1. batcherHash - Etherscan address

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. The self-sequencing delay is configured offchain and the nodeA software client that participates in the network. source and config are unverified.

  1. depositTransaction() in OptimismPortal2 - Etherscan source code

Regular messaging

The user initiates 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. messages by submitting a regular transaction on this chain. When the 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. containing that transaction is settled, the message becomes available for processing on L1. ZK proofs are required to settle blocks.

Shared bridge and Pessimistic Proofs

Polygon Agglayer uses a shared 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. escrow for Rollups, Validiums and external chains that opt in to participate in interoperabilityRefers to the capability of different blockchain networks to communicate and share data. It enables the transfer of assets and information between blockchains, facilitating functionality and collaboration between blockchain ecosystems.. Each participating chain needs to provide zk proofs to access any assets in the shared bridge. In addition to the full execution proofs that are used for the state validation of Rollups and Validiums, accounting proofs over the bridges state (Polygon calls them ‘Pessimistic Proofs’) are used by external chains (‘cdk-sovereign’ and aggchains). Using the SP1 zkVMA special type of zk proving system that proves the correctness of state transitions of a virtual machine. Computation is represented by a program in a specific instruction language, it can have private and public inputs and public outputs. Most of zkVMs are STARKs. by Succinct, projects without a full 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. on Ethereum or custom proof systems are able to share the bridge with the zkEVM Agglayer projects.

  • Funds can be lost if the accounting proof system for the bridge (pessimistic proofs, SP1) is implemented incorrectly.

  1. Pessimistic Proof - Polygon Knowledge Layer
  2. Etherscan: AgglayerManager.sol - verifyPessimisticTrustedAggregator() function
A dashboard to explore contracts and permissions
Go to Disco
Disco UI Banner

Ethereum

Actors

PolygonAdminMultisig0x242d…3e21

A Multisig with 5/9 threshold.

  • Can upgrade with 3d delay
    • AgglayerGateway
    • AgglayerBridge
    • AgglayerManager
    • AgglayerGER
  • Can interact with AgglayerGateway
    • add new routes from proof selector to verifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. / pessimisticVkey for pessimistic proofs with 3d delay
    • add or update default aggchain verification keys (aggchainVkey) for any given selectors
    • change the aggchainSigners and threshold (a multisig used for permissioned state transitions)
    • freeze routes from proof selector to verifier / pessimisticVkey for pessimistic proofs
  • Can interact with AgglayerBridge
    • upgrade the implementation of wrapped tokens deployed by the 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. with 3d delay
  • Can interact with AgglayerManager
    • deploy new projects that use predefined 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. 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:
Haust Network logoLumia Prism logoPentagon Chain logoPolygon zkEVM logoX Layer logo
Polygon Multisig 20xd067…98CC

A Multisig with 3/6 threshold. Member of Katana vaultBridge Multisig 1, Katana vaultBridge Multisig 2, Katana vaultBridge Multisig 3.

  • Can upgrade with no delay
    • L1ERC721Bridge
    • L1CrossDomainMessenger
    • OptimismPortal2
    • SuperchainConfig
    • L1StandardBridge
    • DelayedWETH
    • OptimismMintableERC20Factory
    • AnchorStateRegistry
    • SystemConfig
    • DisputeGameFactory
  • Can interact with AggchainFEP
    • change verification keys (aggregationVkey, rangeVkeyCommitment, aggchainVkey) and the rollupConfigHash, manage multisig signers for permissioned state transitions and change critical configs for state validation
    • toggle the ‘optimisticMode’
  • 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
  • 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
AgglayerManager0x5132…7aB2

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.

  • Can upgrade with no delay
    • AggchainFEP
Used in:
Haust Network logoLumia Prism logoPentagon Chain logoPolygon zkEVM logoX Layer logo
Katana Foundation Engineering/Security Multisig0x4e98…C38a

A Multisig with 2/5 threshold.

  • Can interact with SuperchainConfig
    • pause the OptimismPortal and L1CrossDomainMessenger of Katana (pauses expire automatically after the configured pause expiry)
Used in:
Polygon PoS logo
PolygonSecurityCouncil0x37c5…Dcb6

A Multisig with 6/8 threshold.

  • Can interact with AgglayerManager
    • activate the emergency state in the PolygonRollupManager and in the shared 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. immediately, effectively pausing all projects connected to them and making system contracts instantly upgradable
Used in:
Haust Network logoLumia Prism logoPentagon Chain logoPolygon zkEVM logoX Layer logo
PolygonCreateRollupMultisig0xC74e…79dB

A Multisig with 3/5 threshold.

  • Can interact with AgglayerManager
    • deploy new projects that use predefined 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. types (implementations) and connect them or other Agglayer chains to the PolygonRollupManager
Used in:
Haust Network logoLumia Prism logoPentagon Chain logoPolygon zkEVM logoX Layer logo
Katana vaultBridge Multisig 10x2De2…40ec

A Multisig with 2/3 threshold.

  • Can upgrade with no delay
    • vbWBTC
    • vbETH
    • vbUSDT
Polygon Labs Engineering/Security Multisig0x9d85…9052

A Multisig with 2/8 threshold. Member of Katana vaultBridge Multisig 1, Katana vaultBridge Multisig 2, Katana vaultBridge Multisig 3.

  • Can upgrade with no delay
    • MigrationManager
Used in:
Polygon PoS logo
Katana vaultBridge Multisig 20xA8C3…C5Ff

A Multisig with 2/3 threshold.

  • Can upgrade with no delay
    • vbUSDS
Katana vaultBridge Multisig 30xf4F2…C04E

A Multisig with 2/3 threshold.

  • Can upgrade with no delay
    • vbUSDC
Yearn Strategist Multisig0x1638…0ff7

A Multisig with 3/6 threshold. Member of Katana vaultBridge Multisig 2.

A Multisig with 1/2 threshold.

Katana yieldRecipient Mulsitig0x67C9…3756

A Multisig with 2/6 threshold. Member of Safe.

Katana Steakhouse Financial / Morpho Multisig0x827e…eCdB

A Multisig with 3/9 threshold. Member of Katana vaultBridge Multisig 3.

  • Can interact with SystemConfig
    • Allowed to commit transactions from the current layer to the host chain
  • Can interact with AggchainFEP
    • sign state transitions (replaces state validation for this aggchain)
  • Can interact with AgglayerManager
    • Permissioned to post new state rootsA cryptographic hash succinctly representing a state using a Merkle tree. and global exit roots accompanied by ZK proofs
Used in:
Haust Network logoLumia Prism logoPentagon Chain logoPolygon zkEVM logoX Layer logo

Katana

Actors

GnosisSafeL20x4e98…C38a

A Multisig with 2/5 threshold.

  • Can upgrade with 12h delay
    • AgglayerBridgeL2
    • GlobalExitRootManagerL2SovereignChain
  • Can interact with AgglayerBridgeL2
    • manage token mappings and deployments
    • own and upgrade default 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. token contracts deployed by the 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.
    • pause the bridge
    • unpause the bridge
  • Can interact with GlobalExitRootManagerL2SovereignChain
    • manage ‘claimed’ status of global deposit indexes (can freeze bridge transactions), remove global exit roots (used for L2 deposits)
    • roll back or insert leaves into the local exit tree (LET) that enables withdrawals from the L2. (can steal)
  • Can interact with L2Timelock
    • propose, cancel and execute transactions in the timelock, manage all access control roles and change the minimum delay with 12h delay

A Multisig with 3/6 threshold.

  • Can upgrade with no delay
    • DeployerWhitelist
    • L2CrossDomainMessenger
    • GasPriceOracle
    • L2StandardBridge
    • SequencerFeeVault
    • OptimismMintableERC20Factory
    • L1BlockNumber
    • L2ERC721Bridge
    • L1Block
    • L2ToL1MessagePasser
    • OptimismMintableERC721Factory
    • L2ProxyAdmin
    • BaseFeeVault
    • L1FeeVault
    • OperatorFeeVault
    • SchemaRegistry
    • EAS
  • Can upgrade with 12h delay
    • AgglayerBridgeL2
    • GlobalExitRootManagerL2SovereignChain
  • Can interact with SequencerFeeVault
    • change the fee recipient, the minimum withdrawal amount and whether fees are withdrawn 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. or 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.
  • Can interact with BaseFeeVault
    • change the fee recipient, the minimum withdrawal amount and whether fees are withdrawn on L1 or L2
  • Can interact with L1FeeVault
    • change the fee recipient, the minimum withdrawal amount and whether fees are withdrawn on L1 or L2
  • Can interact with OperatorFeeVault
    • change the fee recipient, the minimum withdrawal amount and whether fees are withdrawn on L1 or L2
  • Can interact with L2Timelock
    • propose, cancel and execute transactions in the timelock, manage all access control roles and change the minimum delay with 12h delay
BaseFeeVault0x4200…0019

Collects the EIP-1559 base fees, which anyone can withdraw to the recipient 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. or 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. once the minimum withdrawal amount is reached.

  • Can interact with OperatorFeeVault
    • receive fees

A Multisig with 3/6 threshold.

  • Can interact with SequencerFeeVault
    • receive fees
  • Can interact with BaseFeeVault
    • receive fees
  • Can interact with L1FeeVault
    • receive fees
  • Can interact with GlobalExitRootManagerL2SovereignChain
    • update the global exit root (GER) that is used for 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. deposits
Note: Contracts presented in this section had their implementations updated since the last time our team looked at this project. The information presented may be inaccurate.

The current deployment carries some associated risks:

  • Funds can be stolen if the contracts or their dependencies (e.g. AggLayerGateway) receive a malicious code upgrade. There is no delay on upgrades.

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

Scroll sideways to see the whole diagram, or tap to open it.

A diagram of the smart contract architecture

Ethereum

Stores the configuration of the OP stack components and 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.. Specifies which game type is used for state validation, which currently is the PermissionedDisputeGame. This contract is modified to disable asset bridging, but it allows forced transactions.

  • Roles:
    • admin: ProxyAdmin; ultimately Polygon Multisig 2

Can be upgraded by: Polygon Multisig 2 with no delay

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 Polygon Multisig 2
    • batcherHash: EOA 1
    • owner: Polygon Multisig 2

Can be upgraded by: Polygon Multisig 2 with no delay

Implementation used in:
Aevo logoBOB logoBoba Network logoCodex 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 Polygon Multisig 2
    • guardian: Katana Foundation Engineering/Security Multisig

Can be upgraded by: Polygon Multisig 2 with no delay

Implementation used in:
Aevo logoBOB logoBoba Network logoCodex logo

A verifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. 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
    • alMultisig: PolygonAdminMultisig
    • freezePpRoute: PolygonAdminMultisig

Can be upgraded by: PolygonAdminMultisig with 3d delay

Proxy used in:
Haust Network logoLumia Prism logoPentagon Chain logoPolygon zkEVM logoX Layer logo

The shared 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. contract, escrowing user funds sent to Agglayer chains. 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

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

Can be upgraded by: PolygonAdminMultisig with 3d delay

Proxy used in:
Haust Network logoLumia Prism logoPentagon Chain logoPolygon zkEVM logoX Layer logo

A merkle treeA hash-based data structure in which each leaf node is a hash of a block of data, and each non-leaf node is a hash of its children. The root of the tree is a cryptographic fingerprint of the entire data structure. Merkle trees (Merkle Patricia Tries) are used in Ethereum to efficiently store key-value pairs. storage contract aggregating state rootsA cryptographic hash succinctly representing a state using a Merkle tree. of each participating Layer 2Layer 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., 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 interoperabilityRefers to the capability of different blockchain networks to communicate and share data. It enables the transfer of assets and information between blockchains, facilitating functionality and collaboration between blockchain ecosystems..

  • Roles:
    • admin: SharedProxyAdmin; ultimately PolygonAdminMultisig

Can be upgraded by: PolygonAdminMultisig with 3d delay

Proxy used in:
Haust Network logoLumia Prism logoPentagon Chain logoPolygon zkEVM logoX Layer logo

A timelock with access control. In the case of an activated emergency state in the AgglayerManager, 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:
Haust Network logoLumia Prism logoPentagon Chain logoPolygon zkEVM logoX Layer logo

This token contract uses a standard ‘vault 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. token’ implementation created by Agglayer CDK. It keeps deposited assets in a vault and issues an IOU token (Vault Bridge WBTC) which can be deposited to Agglayer. The underlying asset is generating yield, which does not accrue to the vbWBTC-IOU but is sent to Safe.

  • Roles:
    • admin: ProxyAdmin; ultimately Katana vaultBridge Multisig 1

Can be upgraded by: Katana vaultBridge Multisig 1 with no delay

This token contract uses a standard ‘vault 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. token’ implementation created by Agglayer CDK. It keeps deposited assets in a vault and issues an IOU token (Vault Bridge ETH) which can be deposited to Agglayer. The underlying asset is generating yield, which does not accrue to the vbETH-IOU but is sent to Safe.

  • Roles:
    • admin: ProxyAdmin; ultimately Katana vaultBridge Multisig 1

Can be upgraded by: Katana vaultBridge Multisig 1 with no delay

This token contract uses a standard ‘vault 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. token’ implementation created by Agglayer CDK. It keeps deposited assets in a vault and issues an IOU token (Vault Bridge USDS) which can be deposited to Agglayer. The underlying asset is generating yield, which does not accrue to the vbUSDS-IOU but is sent to Safe.

  • Roles:
    • admin: ProxyAdmin; ultimately Katana vaultBridge Multisig 2

Can be upgraded by: Katana vaultBridge Multisig 2 with no delay

Helper contract for the vaultBridge tokens on Layer 2Layer 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.. If any vbTokens are minted ‘natively’ on Layer 2, this contract can receive the underlying assets and lock them in the Layer 1Layer 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. vaults.

  • Roles:
    • admin: ProxyAdmin; ultimately Polygon Labs Engineering/Security Multisig

Can be upgraded by: Polygon Labs Engineering/Security Multisig with no delay

This token contract uses a standard ‘vault 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. token’ implementation created by Agglayer CDK. It keeps deposited assets in a vault and issues an IOU token (Vault Bridge USDC) which can be deposited to Agglayer. The underlying asset is generating yield, which does not accrue to the vbUSDC-IOU but is sent to Safe.

  • Roles:
    • admin: ProxyAdmin; ultimately Katana vaultBridge Multisig 3

Can be upgraded by: Katana vaultBridge Multisig 3 with no delay

This token contract uses a standard ‘vault 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. token’ implementation created by Agglayer CDK. It keeps deposited assets in a vault and issues an IOU token (Vault Bridge USDT) which can be deposited to Agglayer. The underlying asset is generating yield, which does not accrue to the vbUSDT-IOU but is sent to Safe.

  • Roles:
    • admin: ProxyAdmin; ultimately Katana vaultBridge Multisig 1

Can be upgraded by: Katana vaultBridge Multisig 1 with no delay

  • Roles:
    • owner: Katana vaultBridge Multisig 1
ProxyAdmin
2 instances
0x19Db…88320x6d0f…9a52
  • Roles:
    • owner: Polygon Multisig 2
PreimageOracle0x1E1d…b1E0

The PreimageOracle contract is used to load the required data 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. for a dispute game.

Implementation used in:
Boba Network logoCodex logoDoma logoInk logo
ProxyAdmin0x263b…ED56
  • Roles:
    • owner: Polygon Labs Engineering/Security Multisig
ProxyAdmin0x8970…FE30
  • Roles:
    • owner: Katana vaultBridge Multisig 3

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 Polygon Multisig 2

Can be upgraded by: Polygon Multisig 2 with no delay

Implementation used in:
Boba Network logoCodex logoDoma logoMetal 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 Polygon Multisig 2

Can be upgraded by: Polygon Multisig 2 with no delay

Implementation used in:
Boba Network logoCodex logoDoma logoMetal logo

The MIPS contract is used to execute the final step of the dispute game which objectively determines the winner of the dispute.

Implementation used in:
Boba Network logoCodex logoDoma logoInk logo
ProxyAdmin0xD1e3…a832
  • Roles:
    • owner: Katana vaultBridge Multisig 2
PermissionedDisputeGame0xe1dF…b87e

Same as FaultDisputeGame, but only two permissioned addresses are designated as 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. and challenger.

Implementation used in:
Boba Network logoCodex logoDoma logoMetal logo
SP1Verifier0x0459…C459

VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. contract for SP1 proofs (v5.0.0).

Implementation used in:
Facet logoHaust Network logoLumia Prism logoPentagon Chain logo
SharedProxyAdmin0x0F99…CC4A
  • Roles:
    • owner: Timelock
Implementation used in:
Haust Network logoLumia Prism logoPentagon Chain logoPolygon zkEVM logoX Layer logo
BridgeLib0x3622…8aB3

Extension contract of the AgglayerBridge for asset metadata…

Implementation used in:
Haust Network logoLumia Prism logoPentagon Chain logoPolygon zkEVM logoX Layer logo
SP1Verifier0xc3c6…AF2A

VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. contract for SP1 proofs (v6.1.0).

Implementation used in:
Base Chain logoMantle logoX Layer logoCelo logo
There are impactful changes to the following contracts, and part of the information might be outdated.

The main system contract defining the katana Aggchain logic. This contract, based on the OP-Succinct L2OutputOracle, supports validity proofs and OP stack outputRoots (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. state rootsA cryptographic hash succinctly representing a state using a Merkle tree.) are saved here.

  • Roles:
    • admin: AgglayerManager
    • aggchainManager: Polygon Multisig 2
    • aggchainSigners: EOA 2 optimisticMode is enabled by the optimisticModeManager
    • optimisticModeManager: Polygon Multisig 2

Can be upgraded by: AgglayerManager with no delay

Katana

Agglayer 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. contract. Supports interop with Ethereum and blockchains connected to Agglayer. Escrows all preminted ETH because it cannot mint on 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.. The globalExitRootManager is used as an oracle to validate bridge messages against.

  • Roles:
    • admin: ProxyAdmin; ultimately GnosisSafeL2, SafeL2
    • bridgeManager: GnosisSafeL2
    • emergencyBridgePauser: GnosisSafeL2
    • emergencyBridgeUnpauser: GnosisSafeL2
    • getProxiedTokensManager: GnosisSafeL2

Can be upgraded by: GnosisSafeL2 with 12h delay, SafeL2 with 12h delay

GlobalExitRootManagerL2SovereignChain0xa40D…B8fAImplementation (Upgradable)Admin

Manages Layer 2Layer 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. and global merkle roots (exit roots). It stores exit roots written during 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. deposits, accepts imported global exit roots from a permissioned address, and manages historical roots.

  • Roles:
    • admin: ProxyAdmin; ultimately GnosisSafeL2, SafeL2
    • globalExitRootRemover: GnosisSafeL2, GnosisSafeL2 if the bridge is paused
    • globalExitRootUpdater: EOA 3

Can be upgraded by: GnosisSafeL2 with 12h delay, SafeL2 with 12h delay

L2Timelock0xBBa0…6d13

A timelock with access control. The current minimum delay is 12h.

  • Roles:
    • timelockAdmin: GnosisSafeL2 (no delay if in emergency state), SafeL2 (no delay if in emergency state)
ProxyAdmin0x0F99…CC4A
  • Roles:
    • owner: L2Timelock
  • Roles:
    • admin: L2ProxyAdmin; ultimately SafeL2

Can be upgraded by: SafeL2 with no delay

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

  • Roles:
    • admin: L2ProxyAdmin; ultimately SafeL2

Can be upgraded by: SafeL2 with no delay

Provides the current gas pricePrice of one unit of gas specified in a transaction. The token used to pay for gas is usually Ether, but rollups can use other custom tokens. for 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. transactions.

  • Roles:
    • admin: L2ProxyAdmin; ultimately SafeL2

Can be upgraded by: SafeL2 with no delay

Collects 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. fees, which anyone can withdraw to the recipient 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. or 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. once the minimum withdrawal amount is reached.

  • Roles:
    • admin: L2ProxyAdmin; ultimately SafeL2
    • proxyAdminOwner: SafeL2
    • recipient: SafeL2

Can be upgraded by: SafeL2 with no delay

Simple contract that returns the latest 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. 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.

  • Roles:
    • admin: L2ProxyAdmin; ultimately SafeL2

Can be upgraded by: SafeL2 with no delay

Simple contract that returns information about the latest 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. 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., which is derived permissionlessly from the L1 chain.

  • Roles:
    • admin: L2ProxyAdmin; ultimately SafeL2

Can be upgraded by: SafeL2 with no delay

Contract used internally by the L2CrossDomainMessenger to send messages 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., including withdrawals. It can also be used directly as a low-level interface.

  • Roles:
    • admin: L2ProxyAdmin; ultimately SafeL2

Can be upgraded by: SafeL2 with no delay

Administration contract for 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. predeploy proxies. Adds upgradePredeploys(address), which can only be called by the system depositor account and delegatecalls an L2ContractsManager to upgrade every predeploy in a single networkA constellation of nodes (peers) that communicate via a peer-to-peer protocol, for example, in propagating transactions and blocks to other nodes. upgrade transaction.

  • Roles:
    • admin: L2ProxyAdmin; ultimately SafeL2
    • owner: SafeL2

Can be upgraded by: SafeL2 with no delay

Collects 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. data portion of 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. transaction fees, which anyone can withdraw to the recipient on L1 or L2 once the minimum withdrawal amount is reached.

  • Roles:
    • admin: L2ProxyAdmin; ultimately SafeL2
    • proxyAdminOwner: SafeL2
    • recipient: SafeL2

Can be upgraded by: SafeL2 with no delay

Collects 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. fees, which anyone can withdraw to the recipient 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. or 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. once the minimum withdrawal amount is reached.

  • Roles:
    • admin: L2ProxyAdmin; ultimately SafeL2
    • proxyAdminOwner: SafeL2
    • recipient: BaseFeeVault

Can be upgraded by: SafeL2 with no delay

Contracts to register schemas for the Ethereum Attestation Service (EAS).

  • Roles:
    • admin: L2ProxyAdmin; ultimately SafeL2

Can be upgraded by: SafeL2 with no delay

Contract containing the main logic for the Ethereum Attestation Service (EAS).

  • Roles:
    • admin: L2ProxyAdmin; ultimately SafeL2

Can be upgraded by: SafeL2 with no delay

BridgeLib0xb30C…E124

Utility library contract for the AgglayerBridgeL2.

TokenWrappedBridgeUpgradeable0xF077…1a2c

An ERC-20 implementation designed for cross-chain assets on 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.. It restricts token minting or burning strictly to the primary 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. contract. The bridge address is set on each token proxy during initialization.

Program hashes

Hash
Repository
Verification
Used in
0x0007...363b
Katana logo
0x5ae1...75b1
Katana logo
0x713f...fa1f
Katana logo
0x374e...dac6
Katana logo
0x6e38...1b53
Katana logo
0x7767...6f70
Katana logo
0x679b...7915
Katana logo
0x00ef...cc30
X Layer logoKatana logoHaust Network logoLumia Prism logo
0x0000...b639
X Layer logoKatana logoHaust Network logoLumia Prism logo
0x00d1...578e
X Layer logoKatana logoHaust Network logoLumia Prism logo