Tzer0 testnet contract addresses
A contract lookup needs both the full address and the network. The addresses below belong to the published Base Sepolia deployment of Tzer0, chain ID 84532. Use them to identify which component a testnet receipt refers to.
Reviewed
Base Sepolia address directory
Match the entire address, including all characters after 0x. Compare the labelled contract role as well, especially for Mission 000, where the token and staking entries refer to different contracts.
| Contract | Published testnet address |
|---|---|
| Mission 000 · $T0 token | 0x15522727F10Ea666Ebb4fD4c23B394580F10FED4 |
| $T0 staking | 0x221De22612E65093Fc43164dae84fa6Bd79E6239 |
| Launchpad | 0xbce48917C41BB45Ad15f859E4Bf0e4EEa74bAd5c |
| TzeroSwap factory | 0xf9CE1F9D20d5d42515b27fE2A5380B89A0Be927E |
| TzeroSwap router | 0x21BbD201c69d0091707d0367D3AD6875cEc150e1 |
| Fee splitter | 0x1C69a90c69fdb2F2E459fCA23cA6B22ACD707B3b |
| Wrapped native · WETH | 0x4200000000000000000000000000000000000006 |
Match the role to the question
Use the token contract when identifying Mission 000 in a token list. Use the staking contract when tracing a position. The factory identifies the system that creates pools, while the router handles swap routing. A mission’s individual pool is a separate address.
For a fee breakdown, trace the fee splitter. For a new mission, start with the launchpad and the creation receipt. This lets you read several events in one transaction without treating every address in the receipt as the same entity.
A read-only address check
- Set the explorer to Base Sepolia and search for the complete address.
- Compare the address and role against the project’s published Contracts directory.
- For a transaction, read both the destination and the events. A routed swap can involve the router, a pool and token contracts within the same receipt.
Tzer0 Contracts questions
How do I identify the $T0 token when the ticker is reused?
Use the Mission 000 token address and chain ID 84532 together. The ticker alone is insufficient because another mission can choose the same symbol.
Is the staking contract the $T0 token contract?
They are separate entries. The token contract records token balances and transfers. The staking contract accounts for positions and fee rewards.
Can I use this table for a mainnet deployment?
This directory covers Base Sepolia. A mainnet address needs to be confirmed against a directory for that specific chain.
Why are several contract addresses visible for one swap?
The router can send a trade to a pool, which interacts with the mission token and WETH. Those components can each appear in one transaction’s records.
Sources
- Tzero protocol documentation · Contractshttps://testnet.tzer0.fun/docs/contracts
- Base documentation · Network chain IDshttps://docs.base.org/base-chain/api-reference/ethereum-json-rpc-api/eth_chainId
- Tzero protocol documentation · TzeroSwaphttps://testnet.tzer0.fun/docs/tzeroswap
- Tzero protocol documentation · $T0 and stakinghttps://testnet.tzer0.fun/docs/t0-staking