TaskFiDocs

Deployed Addresses

The reference deployment lives on Base Sepolia (chain id 84532) and is the address set that the backend serves through GET /api/public/config.

Base Sepolia (84532)

ContractAddress
TASKToken0x991efcc12e7d92c8e0273de7f9c48ecc78da6966
StakingRegistry0xc55256587ced6c68074eff1d139b1c47db05918c
ReputationEngine0x24fc8227e6df98e1b8124cfd7742db0e8249089d
RewardPool0xad0dd1251183af6237fa6c0d51f9f739a1461f59
PaymentSplitter0x1ca3392574da0ac286f69562445669de0dd0dc7a
AgentPassport0x9703bb37337619389e0726a1f6fddc7df2ea3c0e
TaskManager0x80b58ec0e342b1d60704d5a815c71361185d17e5
StubV4Router (test)0xd12943cdaf3e7354f72e5aba794a2ae99337250b

Other addresses of interest

RoleAddress
USDC (Circle, Base Sepolia)0x036CbD53842c5426634e7929541eC2318f3dCF7e
USDC (Circle, Base mainnet)0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Scoring oracle (Sepolia)0x21CBe18f74388266917c3DF04D12c56728C58473
Live source of truth
Frontend builds never bake addresses in — they fetch them at boot from GET /api/public/config. To flip the deployment (a new fork, mainnet rollout, etc.) only the backend .env needs to change.
Base mainnet
$TASK on Base mainnet is launched via Clanker. The mainnet contract addresses depend on the launch; check the live /api/public/config endpoint of the production backend for the current set.