Contract Addresses

Read addresses at runtime from GET https://api.motoswap.org/config. That endpoint is the canonical source. Every address below was checked against it and against code on chain (eth_getCode plus one identifying call). If this page and /config ever disagree, /config wins.

The plain-language list for users, with Etherscan links and one line on what each contract does, is Contracts.

Deployment status on Ethereum (chain 1)

Status is per contract. A contract is either deployed at the address shown, or not deployed yet. A contract that is not deployed reads back from /config as 0x0000000000000000000000000000000000000000. The key is always present. Branch on the address being 0x0, never on a key being absent, never send a transaction to a 0x0 address, and do not integrate against any other address for a contract this table lists as not deployed.

/config returns addresses lowercase; the checksummed form is shown here.

Third-party contracts that /config also serves:

/config.launchPhase summarises the same thing. It reads dex once the DEX contracts are deployed, and it reads vamp only while the farm is deployed and the DEX is not, which is how it read before the DEX opened.

Read /config.addresses.masterChef rather than assuming what is behind it. While launchPhase was vamp it held the same address as vampChef, and that contract is a VampChef, not a MasterChef: VampChef.withdraw returns your LP in one call, it has no claimWithdrawal and no deposit fee, and its PoolAdded and PoolSet events carry no depositFeeBps. Every row of GET /farms carries a chef field, so use that as the deposit target instead of assuming a key.

VampChef, RewardVestingEscrow, MotoStaking, TreasuryVesting and MotocatStaking are ERC-1967 proxies. MotoToken is not upgradeable and has no owner.

Verify any of these yourself with one call each: symbol() on motoToken returns MOTO, rewardToken() on vampChef returns the MOTO address, vestingEscrow() on vampChef returns the rewardVestingEscrow address, and collection() on motocatStaking returns the motocatNft address.

Notes on the zero keys

permit2 is a feature switch as much as an address. Canonical Permit2 is deployed on chain 1 at 0x000000000022D473030F116dDEE9F6B43aC78BA3, and the key carries that address once FeeRouter, which owns the Permit2 path, is deployed. Use the value /config gives you. A 0x0 there is a configuration fault worth reporting, not a phase.

launchpadCurve and launchpadLens also read 0x0 whenever motofunEnabled is false, so gating on the address alone is correct.

Keys that stay zero

The rest of the response

/config also returns chainId, launchPhase (prelaunch, vamp or dex), splitSwapEnabled, motofunEnabled, motofunUrl, bridgeMotoEnabled, pveComboEnabled (dead: nothing reads it), and misconfigured: string[] (empty in normal operation; it names any address a transaction would target that is unset for the current phase). It does not return an RPC URL. Bring your own.

Not exposed by /config

Only the Snapshotter (operational tooling) has no /config key. Everything else is served directly, with no on-chain getter chase needed.

Deriving pairs

Derive any Motoswap pair from the factory rather than hard-coding it: factory.getPair(tokenA, tokenB). The Uniswap V2 pools the farm used during vamp derive the same way, from uniswapV2Factory.

rewardVestingEscrow also has an on-chain getter, vestingEscrow() on the chef, which is worth preferring since it survives a redeploy that /config has not caught up with.

If an address is not in /config and not discoverable from a /config contract's getters, do not integrate against it. Contracts published under Motoswap-adjacent repos are sibling experiments, not the Motoswap DEX.

Local development

There is no public local stack and no public test deployment of the Motoswap contracts. To work locally, fork Ethereum mainnet with your own node tooling and use the chain 1 addresses from GET https://api.motoswap.org/config. A fork only carries what was already deployed at the block you fork from, so pin a recent block, and read the interfaces in the contracts inventory when you need the shape of a call before you make it.

Sanity check: addresses vary per environment

MOTO and every Motoswap contract have a different address on every environment, and sibling experiments carry their own mocks. Always resolve via /config, and check chainId in the same response. Never assume addresses match across projects or deploys.