Mode Network
Badges
About
Mode is an OP stack Optimistic Rollup building the AIFi economy. Their mission is to scale DeFi to billions of users through onchain agents and AI powered financial applications to build a more open, efficient, and inclusive financial future.
Badges
About
Mode is an OP stack Optimistic Rollup building the AIFi economy. Their mission is to scale DeFi to billions of users through onchain agents and AI powered financial applications to build a more open, efficient, and inclusive financial future.
Recategorisation
The project will be classified as "Other" due to its specific risks that set it apart from the standard classifications.
The project will move to Others because:
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.
Funds can be stolen if
Funds can be frozen if
MEV can be extracted if
Sequencer failure
Self sequenceState validation
NoneCurrently the system permits invalid state roots. More details in project overview.
Exit window
NoneThere is no window for users to exit in case of an unwanted regular upgrade since contracts are instantly upgradable.
Proposer failure
Cannot withdrawOnly the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
Mode Network is a Fraud proofs are not enabled
OP Stack projects can use the OP fault proof system, already being deployed on some. This project though is not using fault proofs yet and is relying on the honesty of the permissioned Proposer and Challengers to ensure state correctness. The smart contract system permits invalid state roots.
Funds can be stolen if an invalid state root is submitted to the system (CRITICAL).
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 blobs or calldata. This ensures that it will be available for enough time.
The system has a centralized operator
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.
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.
Regular exit
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).
Forced exit
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.
EVM compatible smart contracts are supported
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.
The system uses the following set of permissioned addresses:
Challenger is an actor allowed to challenge or delete state roots proposed by a Proposer.
Guardian is an actor allowed to pause deposits and withdrawals.
Proposer is an actor allowed to post new state roots of the current layer to the host chain.
- Can act on behalf of SecurityCouncilMultisig.
- A Guardian (acting via SuperchainGuardianMultisig, SecurityCouncilMultisig).
- 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 OpFoundationUpgradeSafe takes ownership of the multisig
Used in:
- A Gnosis Safe with 4 / 6 threshold.
- A Challenger.
Those are the participants of the ModeMultisig.
Those are the participants of the ConduitMultisig.
- A Gnosis Safe with 2 / 2 threshold.
- Can act on behalf of ProxyAdmin, SuperchainProxyAdmin.
- Can change the configuration of AddressManager (acting via ProxyAdmin) - set and change address mappings.
- Can change the configuration of Lib_AddressManager (acting via SuperchainProxyAdmin) - set and change address mappings.
- Can upgrade the implementation of L1ERC721Bridge, L2OutputOracle, SystemConfig, OptimismMintableERC20Factory, OptimismPortal (acting via ProxyAdmin).
- Can upgrade the implementation of L1StandardBridge (acting via ProxyAdmin) - upgrading the bridge implementation can give access to all funds escrowed therein.
- Can upgrade the implementation of SuperchainConfig (acting via SuperchainProxyAdmin).
Used in:
Those are the participants of the SuperchainProxyAdminOwner.
- A Gnosis Safe with 5 / 7 threshold.
- Can act on behalf of DeputyGuardianModule.
- A Guardian (acting via SuperchainGuardianMultisig, DeputyGuardianModule).
Used in:
Those are the participants of the OpFoundationOperationsSafe.
- 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 OpFoundationUpgradeSafe takes ownership of the multisig).
- Member of SuperchainGuardianMultisig, SuperchainProxyAdminOwner.
- A Guardian (acting via SuperchainGuardianMultisig).
Used in:
Those are the participants of the SecurityCouncilMultisig.
- A Gnosis Safe with 1 / 1 threshold. It uses the following modules: DeputyGuardianModule (allows the OpFoundationOperationsSafe, called the deputy guardian, to act on behalf of the Gnosis Safe).
- Can act as a Guardian.
Used in:
Those are the participants of the SuperchainGuardianMultisig.
- A Gnosis Safe with 2 / 2 threshold.
- Member of OpFoundationUpgradeSafe, OpFoundationOperationsSafe.
Used in:
Those are the participants of the GnosisSafe.
- A Gnosis Safe with 5 / 7 threshold.
- Member of SuperchainProxyAdminOwner.
Used in:
Those are the participants of the OpFoundationUpgradeSafe.
A Proposer.
A Sequencer.
The system consists of the following smart contracts on the host chain (Ethereum):
Implementation used in:
Used to bridge ERC-721 tokens from host chain to this chain.
Upgrade delay: No delay
Implementation used in:
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
Implementation used in:
- Can be used to configure AddressManager - set and change address mappings.
- Can be used to upgrade implementation of L1ERC721Bridge, L2OutputOracle, SystemConfig, OptimismMintableERC20Factory, OptimismPortal.
- Can be used to upgrade implementation of L1StandardBridge - upgrading the bridge implementation can give access to all funds escrowed therein.
Legacy contract used to manage a mapping of string names to addresses. Modern OP stack uses a different standard proxy system instead, but this contract is still necessary for backwards compatibility with several older contracts.
- Can be used to configure Lib_AddressManager - set and change address mappings.
- Can be used to upgrade implementation of SuperchainConfig.
Implementation used in:
A helper contract that generates OptimismMintableERC20 contracts on the network it’s deployed to. OptimismMintableERC20 is a standard extension of the base ERC20 token contract designed to allow the L1StandardBridge contracts to mint and burn tokens. This makes it possible to use an OptimismMintablERC20 as this chain’s representation of a token on the host chain, or vice-versa.
Upgrade delay: No delay
Implementation used in:
The main entry point to deposit ERC20 tokens from host chain to this chain. This contract can store any token. This contract can store any token.
Upgrade delay: No delay
Implementation used in:
The main entry point to deposit funds from host chain to this chain. It also allows to prove and finalize withdrawals. This contract stores the following tokens: ETH.
Upgrade delay: No delay
Implementation used in:
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:
Sends messages from host chain to this chain, and relays messages back onto host chain. In the event that a message sent from host chain to this chain is rejected for exceeding this chain’s epoch gas limit, it can be resubmitted via this contract’s replay function.
Implementation used in:
Legacy contract used to manage a mapping of string names to addresses. Modern OP stack uses a different standard proxy system instead, but this contract is still necessary for backwards compatibility with several older contracts.
Implementation used in:
Value Locked is calculated based on these smart contracts and tokens:
Main entry point for users depositing ERC20 token that do not require custom gateway.
Upgrade delay: No delay
Implementation used in:
Main entry point for users depositing ETH.
Upgrade delay: No delay
Implementation 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).
