Overview

Motoswap is a Uniswap-V2-style AMM plus a set of surrounding modules (farming, staking, Rakeback, token launches, NFT staking) with a public REST API served from a Hono backend. Everything is open to external integrators.

Which contracts are deployed

Deployment status is per contract, and Contract addresses owns the table. In short, on Ethereum (chain 1):

• Deployed: MotoToken (MOTO), the launch farming (ended) contract (VampChef, which took Uniswap V2 LP tokens or MOTO on its own and paid MOTO over one 14-day window), UniswapZap, RewardVestingEscrow, MotoStaking, TreasuryVesting, the Motocat collection and MotocatStaking.
• Deployed with the DEX: MotoSwapFactory, MotoSwapRouter02, FeeRouter, pairs, MotoSwapZap, Collector, QuoteAssetRegistry, RakebackV2, MasterChef, the creator fee pair, PveVault, BuybackBurner, and the moto.fun contracts. Read their addresses from GET /config.

A key that reads 0x0000000000000000000000000000000000000000 from GET /config is unset for the current phase. Do not integrate against any address /config did not give you, and never send a transaction to a zero address.

What you can do

• Trade - quote and execute swaps through FeeRouter (the fee-enforcing front door) or MotoSwapRouter02 (the raw V2 router - gated by a per-caller perimeter, so integrators route through FeeRouter in practice).
• Provide liquidity - call addLiquidity / removeLiquidity on MotoSwapRouter02, or use MotoSwapZap for single-sided entry.
• Farm - no farm program is running or planned. VampChef, the launch farming (ended) contract for Uniswap V2 LP or MOTO on its own, ran its one flat 14-day window, and its rewards paid half liquid and half through RewardVestingEscrow over 180 days. MasterChef is deployed but not running: no emission campaign is running and none is planned. LP already staked in it can be withdrawn at any time.
• Stake MOTO - lock MOTO in MotoStaking (3 / 6 / 12 / 24 months, boost 1× / 2× / 4× / 8×) and collect multi-token revshare from Collector. The deployed implementation has no reward tokens registered yet; registering them arrives with a contract upgrade, and until then the staking share is held at the Collector (see the MOTO staking guide).
• Stake Motocat NFTs - escrow-stake into MotocatStaking; staked cats receive PvE airdrop credits (claimed from PveVault, snapshot-sized, no expiry) and boost your swap Points.
• Launch tokens - on moto.fun.
• Claim Rakeback - 2/7 of each protocol fee goes to Rakeback, paid weekly (epochs roll Sunday) against an on-chain merkle root. The 50/25/25 vest is baked into the leaf. Unclaimed Rakeback expires after 30 days and is swept to the treasury.
• Read state - every pool / token / farm / vault / user metric is served from the REST API (https://api.motoswap.org) with ETag caching. Chain state is also readable directly via RPC.

The mental model

       ┌──────────────────────────────────────────────────────────┐
       │                     User's wallet                        │
       └───────────┬──────────────────────────────┬───────────────┘
                   │                              │
     writes: swap, LP, stake, claim…     reads: prices, TVL, positions, points
                   │                              │
                   ▼                              ▼
       ┌───────────────────────┐        ┌────────────────────────┐
       │ FeeRouter (front door)│        │ Backend REST API       │
       │  ├── protocol fee     │        │ api.motoswap.org         │
       │  └── router.swap …    │◀──────▶│ /config /chain/head    │
       └────────┬──────────────┘        │ /tokens /dex /farms    │
                │                       │ /portfolio /rakeback…  │
                │                       └──────────┬─────────────┘
                ▼                                  │
       ┌───────────────────────┐                   │
       │ Motoswap V2 core      │  emits events     │
       │ Factory · Pair · Rtr  │─────────────────▶ │
       └──────────┬────────────┘                   │
                  │ split fees                     │
                  ▼                                │
       ┌───────────────────────┐                   │
       │ Collector             │─────┐             │
       └─┬────┬────┬────┬─────┘      │             │
         ▼    ▼    ▼    ▼            │             │
      Stake Treas Rake Buy           │  the indexer streams events into
      -ing  -ury -back back          │  Postgres + RisingWave; the API
                                     │  reads from those.
       ┌──────────────────────────────────────────────────────────┐
       │              MasterChef / MotoStaking / etc.             │
       │                (independent modules)                     │
       └──────────────────────────────────────────────────────────┘

Every meaningful state change happens on-chain, is picked up by the indexer, and is queryable via REST within seconds. There is no off-chain state you can't reconstruct from the chain.

The three surfaces

1. Smart contracts (write path)

Solidity contracts on Ethereum (see addresses). Call them directly with viem / ethers.

Most-used entrypoints:

Every contract's full ABI, functions, events, errors and access controls are in reference/contracts-full-inventory.

2. REST API (read path)

Every list, chart, price, per-user metric and derived stat is served from the backend. Base URL:

https://api.motoswap.org

Highlights:

Full endpoint reference: reference/api-full-inventory.

Cached GETs carry Cache-Control and a weak ETag: send the tag back in If-None-Match and expect 304. Two exceptions: /config carries Cache-Control but no ETag, and /health/live and /version are private, no-store. See caching.

3. TypeScript SDK

The Motoswap TypeScript SDK - pure functions used by the frontend and backend. It has no network I/O; feed it live reserves from your own RPC / API reads and it returns the same math the app uses. The package is not published yet, so the quickstart examples do not depend on it.

Highlights:

• bestRoute(tokenIn, tokenOut, pairs, amountIn, maxHops) - the canonical multi-hop router.
• optimalSwapInput - closed-form zap math.
• priceImpactBps - sandwich-safe price-impact bps.
• amountOutMin, amountInMax, submitAmountOutMin - slippage helpers.
• computeMasterChefPoolAPR, computeVaultAPR - APR math.

Full SDK reference: reference/sdk-full-inventory.

Fee model

These are the values the contracts launched with. Several are owner-settable, so read the live ones from the contracts rather than trusting this page. On a FeeRouter trade:

• LP fee: 0.30% - kept by liquidity providers (V2 pair invariant fee).
• Protocol fee: 0.70% - charged by FeeRouter on the quote leg only (WETH > USDT > USDC > MOTO). Forwarded to Collector, which splits it by weight into four buckets:
  • 2 / 7 → MotoStaking (revshare to locked MOTO stakers).
  • 2 / 7 → Treasury.
  • 2 / 7 → Rakeback (paid to the trader by merkle claim, 50/25/25 vest).
  • 1 / 7 → buyback and burn.
• Creator fee: 0% to 0.50% (contract cap) - optional per-registered-token; same quote leg. Motoswap sets it to 0.30%; the range here is MAX_CREATOR_FEE_BPS, the registry's hard ceiling.

Total: 1.00% on a one-hop route with no registered moto.fun token: the 0.30% pair fee plus the 0.70% protocol fee. The pair fee is paid per hop and the protocol fee once per trade. Each path endpoint that is a registered moto.fun token adds the creator fee (0.30%), so a route between two registered tokens pays it twice. The trader gets ~0.20% back via Rakeback. The fee table on the aggregators page has every combination.

Full fee constants: reference/addresses-config-events.

Gas

This page carries no gas figures. Estimate gas per call against the deployed contracts (eth_estimateGas, or viem's estimateContractGas) rather than budgeting from a published number.

Where to go next

• Building an aggregator, bot, scanner, or AI agent? → pick your path.
• New here? → quickstart.
• Need to call a specific contract? → reference/contracts-full-inventory.
• Building a UI on top of Motoswap data? → reference/api-full-inventory.
• Doing swap math? → reference/sdk-full-inventory.
• Watching events? → guides/watch-events.