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.
Deployer factories (L1, chain ID 127001)
127001)Arachnid Deterministic Deployment Proxy
0x4e59b44847b379578588920cA78FbF26c0B4956C
CREATE2 deployer factory
CreateX
0xba5Ed099633D3B313e4D5F7bdc1305d3c28ba5Ed
CREATE2 / CREATE3 deployer factory
Safe Singleton Factory
0x914d7Fec6aaC8cd542e72Bca78B30650d45643d7
CREATE2 deployer factory (used by the Safe suite)
Core infrastructure
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 account abstraction
EntryPoint v0.6
0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789
Account-abstraction entrypoint
SenderCreator v0.6
0x7fc98430eAEdbb6070B35B39D798725049088348
EntryPoint v0.6 account-deployment helper
EntryPoint v0.7
0x0000000071727De22E5E9d8BAf0edAc6f37da032
Account-abstraction entrypoint
SenderCreator v0.7
0xEFC2c1444eBCC4Db75e7613d20C6a62fF67A167C
EntryPoint v0.7 account-deployment helper
EntryPoint v0.8
0x4337084D9E255Ff0702461CF8895CE9E3b5Ff108
Account-abstraction entrypoint (EIP-7702 era)
All three EntryPoint versions are live, so bundlers, paymasters, and smart-wallet SDKs work on Gravity regardless of which version they target.
Safe{Wallet} smart-account suite (v1.4.1)
The full canonical Safe contract suite is deployed at its universal addresses, so the Safe SDK / Transaction Service and any Safe-based tooling work on Gravity.
Safe (L1 singleton)
0x41675C099F32341bf84BFc5382aF534df5C7461a
Safe master copy (mainnet-style)
SafeL2 (L2 singleton)
0x29fcB43b46531BcA003ddC8FCB67FFE91900C762
Safe master copy emitting events for indexers
SafeProxyFactory
0x4e1DCf7AD4e460CfD30791CCC4F9c8a4f820ec67
Deploys Safe proxies (createProxyWithNonce)
CompatibilityFallbackHandler
0xfd0732Dc9E303f09fCEf3a7388Ad10A83459Ec99
Default fallback handler (EIP-1271, token receivers)
MultiSend
0x38869bf66a61cF6bDB996A6aE40D5853Fd43B526
Batch multiple calls in one Safe tx
MultiSendCallOnly
0x9641d764fc13c8B624c04430C7356C1C7C8102e2
Batch CALL-only txs (no delegatecall)
CreateCall
0x9b35Af71d77eaf8d7e40252370304687390A1A52
Deploy contracts from within a Safe
SignMessageLib
0xd53cd0aB83D845Ac265BE939c57F53AD838012c9
On-chain EIP-1271 message signing
SimulateTxAccessor
0x3d4BA2E0884aa488718476ca2FB8Efc291A46199
staticcall tx simulation
On Gravity, point Safe proxies at the SafeL2 singleton (0x29fc…0C762) rather than the L1 Safe — the L2 variant emits the events the Safe Transaction Service and indexers rely on (the L1 singleton is the mainnet/gas-optimised variant).
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
System Contracts — Gravity's system runtime and bridge contracts (
0x1625Fxxxx).Token Contracts on Gravity — canonical ERC-20 list (G, wG, USDT, …).
Gravity Skill — the agent skill that bundles these addresses for AI coding tools.
Gravity Mainnet (L1) — network connection parameters.
Last updated
Was this helpful?