Metal L2 is a general-purpose OP stack rollup by Metallicus focused on banking and compliance.
$155.76 K
3.13%
Metal L2 is a general-purpose OP stack rollup by Metallicus focused on banking and compliance.
Currently the system permits invalid state roots. More details in project overview.
There is no window for users to exit in case of an unwanted regular upgrade since contracts are instantly upgradable.
Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
Ultimately, OP stack chains will use interactive fraud proofs to enforce state correctness. This feature is currently in development and the system permits invalid state roots.
Funds can be stolen if an invalid state root is submitted to the system (CRITICAL).
All the data that is used to construct the system state is published on chain in the form of cheap blobs or calldata. This ensures that it will be available for enough time.
The operator is the only entity that can propose blocks. 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.
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 user initiates the withdrawal by submitting a regular transaction on this chain. When the block containing that transaction is finalized the funds become available for withdrawal on L1. The process of block finalization takes a challenge period of 7d to complete. Finally the user submits an L1 transaction to claim the funds. This transaction requires a merkle proof.
Funds can be frozen if the centralized validator goes down. Users cannot produce blocks themselves and exiting the system requires new block production (CRITICAL).
If the user experiences censorship from the operator with regular exit they can submit their withdrawal requests directly on L1. The system is then obliged to service this request or halt all withdrawals, including forced withdrawals from L1 and regular withdrawals initiated on L2. Once the force operation is submitted and if the request is serviced, the operation follows the flow of a regular exit.
OP stack chains are pursuing the EVM Equivalence model. No changes to smart contracts are required regardless of the language they are written in, i.e. anything deployed on L1 can be deployed on L2.
Owner of AddressManager. Admin of OptimismPortal, SystemConfig, L2OutputOracle, L1ERC721Bridge, OptimismMintableERC20Factory, L1StandardBridge.
Central actor allowed to post new L2 state roots to L1.
Central actor allowed to delete L2 state roots proposed by a Proposer.
Used in:
This is a Gnosis Safe with 4 / 7 threshold. Designated as the owner of the SystemConfig, meaning it can update the preconfer address, the batch submitter address and the gas configuration of the system.
Used in:
Those are the participants of the ConduitMultisig.
This is a Gnosis Safe with 2 / 2 threshold. Owner of the ProxyAdmin and SuperchainProxyAdmin.
Used in:
Those are the participants of the SuperchainProxyAdminOwner.
This is a Gnosis Safe with 1 / 1 threshold. It uses the following modules: DeputyGuardianModule (allows the FoundationMultisig_2, called the deputy guardian, to act on behalf of the Gnosis Safe). Address allowed to pause withdrawals in case of an emergency. It is controlled by the Security Council multisig, but a deputy module allows the Foundation to act through it. The Security Council can disable the module if the Foundation acts maliciously.
Used in:
Those are the participants of the GuardianMultisig.
This is a Gnosis Safe with 5 / 7 threshold. Member of the ProxyAdminOwner.
Used in:
Those are the participants of the FoundationMultisig_1.
This is a Gnosis Safe with 10 / 13 threshold. It uses the following modules: LivenessModule (used to remove members inactive for 98d while making sure that the threshold remains above 75%. If the number of members falls below 8, the FoundationMultisig_1 takes ownership of the multisig). Member of the ProxyAdminOwner. It implements a LivenessModule used to remove inactive (0s) members while making sure that the threshold remains above 75%. If the number of members falls below 8, the Foundation takes ownership of the Security Council.
Used in:
Those are the participants of the SecurityCouncilMultisig.
This is a Gnosis Safe with 5 / 7 threshold. Deputy to the GuardianMultisig.
Used in:
Those are the participants of the FoundationMultisig_2.
The L2OutputOracle contract contains a list of proposed state roots which Proposers assert to be a result of block execution. Currently only the PROPOSER address can submit new state roots.
Upgrade delay: No delay
Proxy used in:
The L1CrossDomainMessenger (L1xDM) contract sends messages from L1 to L2, and relays messages from L2 onto L1. In the event that a message sent from L1 to L2 is rejected for exceeding the L2 epoch gas limit, it can be resubmitted via this contract’s replay function.
Upgrade delay: No delay
Proxy used in:
Upgrade delay: No delay
Proxy used in:
The SuperchainConfig contract is used to manage global configuration values for multiple OP Chains within a single Superchain network. The SuperchainConfig contract manages the PAUSED_SLOT
, a boolean value indicating whether the Superchain is paused, and GUARDIAN_SLOT
, the address of the guardian which can pause and unpause the system.
Upgrade delay: No delay
Proxy used in:
Main entry point for users depositing ERC20 token that do not require custom gateway.
Upgrade delay: No delay
Proxy used in:
Main entry point for users depositing ETH.
Upgrade delay: No delay
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).