Skip to Content
SupraNova (Bridge)Contract Addresses

Contract Addresses

This page lists the addresses of the SupraNova contracts and Move packages on each network. For token addresses, see Supported Tokens.

  • EVM chains. Each contract is deployed behind an ERC1967Proxy. Always call the proxy address listed here. To find the current implementation, read the proxy’s EIP-1967 implementation slot. Each wrapped token is a BeaconProxy, and all wrapped tokens share one WrappedToken implementation, listed in its own row.
  • SupraMVM. SupraNova is a set of Move modules, published under one or more packages. Each module has a resource account, listed below, and most modules keep their state in it. hypernova_core is the exception: it keeps its light-client state under the package address, and uses its resource account for its signer capability and collected fees.

Addresses change when contracts are redeployed. Verify an address against this page before integrating with it.

Network

Ethereum Mainnet (chain ID 1)

Deployed from the EVM contracts v2.0.0 release.

ContractAddress
TokenBridge0x4ef3DE5d92C9d5D49205C3Ee16F84A1F538e70f5
Hypernova0x96AbCABA0236eCC166c8aDf2b5797ad3D32f5367
TokenVault0x4A4B47c6296b20790daF30B529469a46d48C51Ad
FeeOperator0x017bE40790A232651Af8C5ac08439280d412EeE2
WrappedTokenFactory0x1108470109E12345626B29be71751a1c9F7e12b0
WrappedToken (implementation)0x09f04De95D91a797Db47bE8764Eb66488FD7F783

For the admin multisig addresses, see Roles and Permissions.

Last updated on