For the complete documentation index, see llms.txt. This page is also available as Markdown.

Deployed Contracts

Canonical EVM ecosystem preinstall contracts on Gravity Mainnet (L1).

Gravity L1 ships the standard EVM ecosystem contracts at their universal cross-chain addresses — the same addresses they occupy on Ethereum, Base, Arbitrum, and most other EVM chains. Because tooling (viem, ethers, wagmi, Foundry, wallet SDKs, ERC-4337 bundlers, Safe UI, …) hardcodes these addresses, any dapp that relies on them works on Gravity with zero per-chain configuration.

These are the standard, audited ecosystem deployments — distinct from Gravity's own system runtime contracts in the 0x1625Fxxxx range. For those, see System Contracts.

Live on Gravity Mainnet (L1, chain ID 127001)

Contract
Address
Role

Arachnid Deterministic Deployment Proxy

0x4e59b44847b379578588920cA78FbF26c0B4956C

CREATE2 deployer factory

CreateX

0xba5Ed099633D3B313e4D5F7bdc1305d3c28ba5Ed

CREATE2 / CREATE3 deployer factory

Multicall3

0xcA11bde05977b3631167028862bE2a173976CA11

Batched reads/writes in a single call

Permit2

0x000000000022D473030F116dDEE9F6B43aC78BA3

Uniswap signature-based token approvals

Wrapped G (wG)

0xBB859E225ac8Fb6BE1C7e38D87b767e95Fef0EbD

ERC-20 wrapper for native G

ERC-4337 EntryPoint v0.6

0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789

Account-abstraction entrypoint

ERC-4337 SenderCreator v0.6

0x7fc98430eAEdbb6070B35B39D798725049088348

EntryPoint v0.6 account-deployment helper

Not yet live (pending the Safe Singleton Factory)

Contract
Address
Role

Safe Singleton Factory

0x914d7Fec6aaC8cd542e72Bca78B30650d45643d7

CREATE2 deployer factory (per-chain presigned)

ERC-4337 EntryPoint v0.7

0x0000000071727De22E5E9d8BAf0edAc6f37da032

Account-abstraction entrypoint

ERC-4337 SenderCreator v0.7

0xEFC2c1444eBCC4Db75e7613d20C6a62fF67A167C

EntryPoint v0.7 account-deployment helper

ERC-4337 EntryPoint v0.8

0x4337084D9E255Ff0702461CF8895CE9E3b5Ff108

Account-abstraction entrypoint

The Safe Singleton Factory is deployed from a per-chain EIP-155-signed transaction that only the Safe team can publish, so it cannot be deployed permissionlessly. EntryPoint v0.7 and v0.8 are deployed through it (and SenderCreator v0.7 is created by the v0.7 constructor), so all three wait on it.

Verify before you hardcode

Confirm an address has code before relying on it:

A non-empty result means the contract is live; an empty 0x means it is not deployed yet.

See also

Last updated

Was this helpful?