Skip to main content

Contract on Verse

Th Verse Layer is also EVM compatible. Therefore, any contract in the Ethereum ecosystem can be migrated to the Oasys without any additional modifications. Furthermore, any existing developer tools such as Truffle or web3.js are also compatible. Thus, there is no friction for developers. The development experience is the same as with Ethereum.

Preset Contracts

The Verse layer is under the control of each Verse's builders. Therefore, contracts deployed on the Verse are also under their control.

However, there is a set of preset contracts that are common across all Verses. These contracts are used to facilitate the bridging process. They help establish a standardized ecosystem across all Verses. Here is the list:

NameDescriptionAddressReferenced Code
L2CrossDomainMessengerThe L2 Cross Domain Messenger contract sends messages from L2 to L1, and is the entry point0x4200000000000000000000000000000000000007L2CrossDomainMessenger.sol
L2StandardBridgeThe L2 Standard bridge is a contract which works together with the L1 Standard bridge to enable OAS and ERC20 transitions between L1 and L20x4200000000000000000000000000000000000010L2StandardBridge.sol
L2ERC721BridgeThe L2 ERC721 bridge is a contract which works together with the L1 Standard bridge to enable NFT transitions between L1 and L20x6200000000000000000000000000000000000001L2ERC721Bridge.sol
L2StandardTokenFactoryFactory contract for creating standard L2 token representations of L1 ERC20s compatible with and working on the standard bridge0x4200000000000000000000000000000000000012L2StandardTokenFactory.sol