Deployed addresses
Every contract Mitoshi deployed on Tempo testnet and Base Sepolia, straight from the deployment fragments the app itself reads.
These tables are generated from contracts/deployments/<chainId>/<area>.json — the same fragments pnpm codegen turns into the app's @cwf/clients. The docs build checks the copy against them, so an address here is the address the app calls. Each links to the explorer; a replaced address stays listed under its successor, because the indexer still reads it.
Predeployed by Tempo and used as-is: pathUSD 0x20C0000000000000000000000000000000000000, the TIP-20 factory, the fee manager, the stablecoin DEX, the access-key keychain, and the ERC-8004 registries (Identity 0x8004…BD9e, Reputation 0x8004…8713).
Tempo testnet (Moderato, chain 42431)
Stock pools
0xe16fc2…80aca20xac7dbb…835b900x43da0e…50bde00x6ded81…38c3dd0x59fca6…5a386aBase Sepolia (chain 84532) — the testnet bridge hop
Nothing is deployed on Tempo mainnet or Robinhood Chain yet.
The relay and your keys
How Mitoshi pays your network fees without being able to spend your money, and how one-tap keys stay inside their limits.
Built on Tempo
What each platform does for Mitoshi today — Tempo's chain and accounts, RedStone's signed prints, LayerZero's bridge, Robinhood Chain's Stock Tokens, Uniswap v4 — and where each stands on testnet.