ADI Chain

The main contract defining the Layer 2. Operator actions like commiting blocks, providing ZK proofs and executing batches ultimately target this contract which then processes transactions. During batch execution it processes L1 --> L2 and L2 --> L1 transactions.

• Roles:
  • getAdmin: ChainAdminOwnable; ultimately ADI Multisig 1

[FORK] This contract is not the standard hub contract from the Elastic network but a local fork for ADI chain. Defines L2 diamond contract versions, creation and upgrade data and the proof system for all ZK stack chains connected to it. ZK chains are children of this central contract and can only upgrade to versions that were previously registered here. The current protocol version is 0,29,0.

• Roles:
  • admin: ChainAdminOwnable, ProxyAdmin; ultimately ADI Multisig 2, Governance
  • owner: Governance

Contract that verifies the data availability of ethereum calldata and blobs. Can be used by ZK stack rollups as the L1 part of a DAValidator pair.

Contract responsible for bookkeeping L1 bridging transactions. Used to finalize withdrawals and reclaim failed deposits. Does not escrow funds.

• Roles:
  • admin: ProxyAdmin; ultimately Governance
  • owner: EOA 4

Aggregates remote bridge message roots from all ZK stack chains. To be used with the Gateway when deployed.

• Roles:
  • admin: ProxyAdmin; ultimately Governance

[FORK] This contract is not the standard hub contract from the Elastic network but a local fork for ADI chain. The main registry (hub) for chain contracts (supports more than ADI chain) and central entrypoint for bridge transactions. Stores important mappings like from chainId to diamond address, from chainId to parent CTM, from chainId to base token etc. A clone of Bridgehub is also deployed on each L2 chain, but this clone is only used on settlement layers.

• Roles:
  • admin: ChainAdminOwnable, ProxyAdmin; ultimately ADI Multisig 2, Governance
  • owner: Governance

Simple registry for allowed DA address pairs for the ‘rollup’ data availability mode (can be permanently enforced with isPermanentRollup=true). Rollup DA address pairs (especially the L1 part) usually point to contracts that validate if data was made available on Ethereum.

• Roles:
  • owner: Governance

Asset deployment tracker where the ‘asset’ is a ChainTypeManager. The registering of asset IDs for ChainTypeManagers is necessary to be able to migrate them to a given settlement layer, for example the Gateway.

• Roles:
  • admin: ProxyAdmin; ultimately Governance

Intermediary contract between the Validators and the central diamond contract that delays block execution (ie withdrawals and other L2 --> L1 messages) by 0s.

• Roles:
  • admin: ProxyAdmin; ultimately Governance
  • validatorVTL: EOA 1, EOA 2, EOA 3, EOA 5

A governance proxy that lets ADI Multisig 1 act through it.

• Roles:
  • owner: ADI Multisig 1
  • tokenMultiplierSetter: EOA 6

A governance proxy that lets ADI Multisig 2 act through it.

• Roles:
  • owner: ADI Multisig 2

Legacy bridge for depositing ERC20 tokens to ADI Chain.

Canonical central asset escrow for all ZK stack chains.

• Roles:
  • admin: ProxyAdmin; ultimately Governance
  • owner: EOA 7
• This contract can store any token.

A router contract for verifiers. Routes verification requests to the corresponding fflonk or plonk verifiers depending on the supplied proof type and version.

• Roles:
  • owner: ChainAdminOwnable

Verifies a zk-SNARK proof using an implementation of the fflonk proof system.

• Roles:
  • owner: Governance

Verifies a zk-SNARK proof using an implementation of the PlonK proof system.

Specialized contract for managing chain assets, i.e. chain migrations.

• Roles:
  • admin: ProxyAdmin; ultimately Governance

A simple contract that can be called by the ChainAdmin to emit notifications about chain migrations.

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