Contracts
A reference page that includes information about all contracts deployed on various networks.
Ethereum network (L1)
Details of smart contracts deployed on 🟢 Ethereum Mainnet and 🟡 Sepolia Testnet are as follows.
Name of Contract | Description | Contract Address | |
---|---|---|---|
ProxyAdmin | Owner of AddressManager, Admin of LiskPortal, SystemConfig, L2OutputOracle, L1StandardBridge. | 0xeC432c4F1d0E12737f3a42a459B84848Af979b2d | 🟢 |
0x5Db9F05921d8d5a6a157F6f49c411cc0e46c6330 | 🟡 | ||
SystemConfig | It contains configuration parameters such as the Sequencer address, the L2 gas limit, and the unsafe block signer address. | 0x05f23282FFDCA8286E4738C1aF79079f3d843750 | 🟢 |
0xF54791059df4a12BA461b881B4080Ae81a1d0AC0 | 🟡 | ||
AddressManager | The Address Manager is a built-in actor that manages Ethereum's address space. | 0x2dF7057d3F25212E51aFEA8dA628668229Ea423f | 🟢 |
0x27Bb4A7cd8FB20cb816BF4Aac668BF841bb3D5d3 | 🟡 | ||
L1ERC721Bridge | Handles the sending and receiving of ERC 721 tokens between L1 and L2. | 0x3A44A3b263FB631cdbf25f339e2D29497511A81f | 🟢 |
0xb4E988CF1aD8C361D56118437502A8f11C7FaA01 | 🟡 | ||
L2OutputOracle | It contains a list of proposed state roots that the Proposers assert to be a result of block execution. | 0x113cB99283AF242Da0A0C54347667edF531Aa7d6 | 🟢 |
0xA0E35F56C318DE1bD5D9ca6A94Fe7e37C5663348 | 🟡 | ||
OptimismPortal | It is the main entry point for depositing funds from L1 to L2. It also allows proving and finalizing withdrawals. | 0x26dB93F8b8b4f7016240af62F7730979d353f9A7 | 🟢 |
0xe3d90F21490686Ec7eF37BE788E02dfC12787264 | 🟡 | ||
L1StandardBridge | It is the main entry point for depositing ERC20 tokens from L1 to L2. This contract can store any token. | 0x2658723Bf70c7667De6B25F99fcce13A16D25d08 | 🟢 |
0x1Fb30e446eA791cd1f011675E5F3f5311b70faF5 | 🟡 | ||
ProtocolVersions | It is used to manage superchain protocol version information. | 0xDd9C27910327d3f4A4007Ad8f7B53332DB6f1079 | 🟢 |
0x1Bb17EB31bDdFd30F63D4FAe6c8Eb85D9e9b1f48 | 🟡 | ||
L1CrossDomainMessenger | Sends messages from L1 to L2 and relays messages from L2 onto L1. | 0x31B72D76FB666844C41EdF08dF0254875Dbb7edB | 🟢 |
0x857824E6234f7733ecA4e9A76804fd1afa1A3A2C | 🟡 | ||
OptimismMintableERC20Factory | It is responsible for creating ERC20 contracts on L1 that can be used for depositing native L2 tokens into. | 0xc1dA06CC5DD5cE23bABa924463de7F762039252d | 🟢 |
0x269d632C1E518a922C30C749cFD3f82Eb5C779B0 | 🟡 | ||
L1LiskToken | Contains the implementation of LSK as an ERC20 token. | 0x6033F7f88332B8db6ad452B7C6D5bB643990aE3f | 🟢 |
0x16B840bA01e2b05fc2268eAf6d18892a11EC29D6 | 🟡 | ||
L1VestingWallet | This contract handles the Vesting functionality of the LSK token for the Ethereum network. | 0xd590c2e71739c551eba7aebe00e7855df4cf5fb7 | 🟢 |
0x76f1cD8436373fa9f3c17Da1e39740fE9dB9a04B | 🟡 | ||
DisputeGameFactory | The dispute game factory is responsible for creating new DisputeGame contracts given a GameType and a root Claim . Challenger agents listen to the DisputeGameCreated events in order to keep up with on-going disputes in the protocol and participate accordingly. | 0x0CF7D3706a27CCE2017aEB11E8a9c8b5388c282C | 🟢 |
AnchorStateRegistry | A registry where DisputeGame contracts can store and register their results so that these results could be used as the starting states for new DisputeGame instances. | 0x7ad0d165B9607960AD850090DDd7B9eB381D9c1e | 🟢 |
DelayedWETHPermissionedGame | The DelayedWETH contract manages bonds posted by participants during disputes. It delays payouts to allow time for verification, ensuring that funds are distributed correctly. This mechanism ensures participants are financially committed and disputes are finalized securely. | 0x31eFC2c8012c56E007E5Bdb8E5B7955D197C168e | 🟢 |
OptimismMintableERC20Factory | The OptimismMintableERC20Factory is responsible for creating ERC20 contracts on L2 that can be used for depositing native L1 tokens into. These ERC20 contracts can be created permissionlessly and implement the interface required by the StandardBridge to just work with deposits and withdrawals. | 0xD00e38514d66bf1B761a8937559c6b2854A5B3ad | 🟢 |
Lisk network (L2)
Predeploys on Lisk
A predeployed contract is included in the L2 genesis state, and it exists from the very beginning of the blockchain. On Lisk Network, these contracts are located at specific addresses that are determined in advance and are part of the genesis state. For more information on Predeploys, see Predeploys' README.
Details of predeployed contracts deployed on 🔵 Lisk Mainnet and 🟣 Lisk Sepolia Testnet are as follows.
Lisk features-specific contracts
Details of Lisk features-specific contracts deployed on 🔵 Lisk Mainnet and 🟣 Lisk Sepolia Testnet are as follows.
Name of Contract | Description | Contract Address | |
---|---|---|---|
L2Airdrop | L2Airdrop is an implementation of the Lisk v4 migration airdrop on L2. It is responsible for the airdrop computation and distribution of LSK tokens to the recipient's accounts that have migrated to L2. | 0xC7315f4FaaB2F700fc6b4704BB801c46ff6327AC | 🔵 |
0xDdE1998B8842b1C925Eef7eDFDAA2Df24A75048a | 🟣 | ||
L2Claim (Proxy) | Proxy contract for claiming LSK tokens from the legacy Lisk chain and receive the appropriate amount on Lisk L2. | 0xC7315f4FaaB2F700fc6b4704BB801c46ff6327AC | 🔵 |
0xDdE1998B8842b1C925Eef7eDFDAA2Df24A75048a | 🟣 | ||
L2Claim (Implementation) | Enables users to claim their LSK tokens from the legacy Lisk chain and receive the appropriate amount on Lisk L2 using Merkle proofs, with support for both regular and multisig accounts. | 0x60790Dc2d45BaA8B36282889569BbB301F4D0c41 | 🔵 |
0xAE4A95E412d7d669AbE6bB23031Ae0250B832710 | 🟣 | ||
L2Governor (Proxy) | Proxy contract for the governance-related operations of Lisk L2. | 0x58a61b1807a7bDA541855DaAEAEe89b1DDA48568 | 🔵 |
0xf9181aaD773d423A2cc0155Cb4263E563D51B467 |