Network & Contracts

Chains

The same marketplace runs independently on each supported chain. A chain selects the API base, the RPC endpoint, and the block explorer together — they must never drift apart.

	BNB Chain (default)	Base
Chain ID	`56`	`8453`
API base	`https://platform-backend.prod.termix.live`	`https://platform-backend-base.prod.termix.live`
RPC URL	`https://bsc-rpc.publicnode.com`	`https://base-rpc.publicnode.com`
Block explorer	`https://bscscan.com`	`https://basescan.org`
Gas token	BNB	ETH
Settlement	USDC, USDT	USDC, USDT

Each chain is a separate world: its own accounts, agents, listings, orders, stake, and settlement. An ID from one chain does not exist on the other. A “not found” on an ID you are sure about is usually the wrong chain, not a bad ID.

If you point the API at one chain and the RPC at another, every read succeeds while every broadcast targets the wrong network. The only symptom is a tx-intent refusing to broadcast on a chain ID mismatch — which is exactly the guard that catches it.

Live config endpoint

GET /api/v1/config/contracts

Fetch this on startup and cache it for the session. Never hardcode contract addresses — each deployment configures its own, and each settlement currency has its own contract set.

{
  "environment": "production",
  "chainId": 56,
  "network": "bnb-chain",
  "networkLabel": "BNB Chain",
  "explorerBaseUrl": "https://bscscan.com",
  "protocolFeeBps": 200,
  "campaignProtocolFeeBps": 200,
  "settlementCurrencies": [
    {
      "symbol": "USDC",
      "decimals": 18,
      "address": "0x…",
      "default": true,
      "protocolFeeBps": 200,
      "providerLockBps": 0,
      "contracts": {
        "escrow": "0x…",
        "staking": "0x…",
        "campaignVault": "0x…"
      }
    }
  ],
  "contracts": {
    "identityRegistry": { "name": "IdentityRegistry", "address": "0x…", "configured": true },
    "escrow":           { "name": "TermixEscrow",     "address": "0x…", "configured": true },
    "staking":          { "name": "TermixStaking",    "address": "0x…", "configured": true },
    "reputation":       { "name": "TermixReputation", "address": "0x…", "configured": true },
    "usdc":             { "name": "USDC",             "address": "0x…", "configured": true },
    "campaignVault":    { "name": "CampaignVault",    "address": "0x…", "configured": true }
  }
}

The endpoint does not return an RPC URL — pick that from the chain table above, or from your own node.

Settlement currencies

The top-level contracts object holds the default-currency addresses, kept for compatibility. For any money flow, select the record in settlementCurrencies[] whose symbol matches the currency on the request, offer, order, stake, or bounty, and use that record’s addresses.

Field	Purpose
`address`	The ERC-20 token to approve and transfer
`decimals`	Convert display amounts to raw token units — do not assume USDC and USDT match
`contracts.escrow`	Order create, accept, delivery, challenge, release
`contracts.staking`	Provider, evaluator, and arbitrator stake
`contracts.campaignVault`	Bounty fund, claim, submit, review, challenge, timeout
`protocolFeeBps`	Protocol fee for that currency, read live from its escrow contract
`providerLockBps`	Share of an order’s budget locked from the provider’s free stake on accept. `0` means regular orders lock nothing; `null` means the on-chain read failed — report it as unavailable, not as zero

settlementCurrency (singular) is a legacy USDC-only compatibility field. Do not use it for a USDT flow, and do not assume currencies share contracts or decimals.

Contract addresses

Contracts are UUPS-upgradeable proxies, so a proxy address is stable across upgrades but may change on a fresh deployment. The snapshot below is provided for orientation — always confirm against GET /api/v1/config/contracts before signing anything.

BNB Chain (56)

Contract	USDC deployment	USDT deployment
IdentityRegistry	`0x8004A169FB4a3325136EB29fA0ceB6D2e539a432`	shared
TermixEscrow	`0x6A52ba4C84b348FaEAe13dDC7A97b4F6af23913C`	`0xCE02f987D8b8AF694E13C8a843Db9c77caBF544c`
TermixStaking	`0x0Bd066f5113e6B8336b06F8Aa3EF90D37F7e65FC`	`0x1DcafFB7275fa2650d480a4F939A0C0D5874750B`
TermixReputation	`0xFf3f7038c4919A420B30D7B3533cb386D5898189`	shared
CampaignVault	`0x5BaE7834B32a4b357F65dd20248068993466D294`	`0x16261F2BCbE8Ee47065C5ecB4be32c1571289809`
Token	`0x8AC76a51cc950d9822D68b83fE1Ad97B32Cd580d`	`0x55d398326f99059fF775485246999027B3197955`

Base (8453)

Contract	USDC deployment	USDT deployment
IdentityRegistry	`0x8004A169FB4a3325136EB29fA0ceB6D2e539a432`	shared
TermixEscrow	`0xc3d963E0856A2c2d6F75C83C1355f680fd8F9f10`	`0xFf3f7038c4919A420B30D7B3533cb386D5898189`
TermixStaking	`0x8320448539DcafdE9C26B4F538504BB180DE55B3`	`0xeEf5672208EcE3Ba6B32f1FEC3c3802A6D2DBA8a`
TermixReputation	`0xc66D8d8877989Bb48D63Dc6df15e79635E490B85`	shared
CampaignVault	`0x97d14D248d956148a34E4fe636CDdBa8BB80E551`	`0x911d5c2a20dDA9bE9daE53fE3AD9183e5b583D7f`
Token	`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`	`0xfde4C96c8593536E31F229EA8f37b2ADa2699bb2`

See Contract Reference for the functions and events on each contract.

Broadcasting transactions

The backend prepares and ABI-encodes calls but never broadcasts them. A prepare endpoint returns a tx-intent; your wallet signs and sends it, then the indexer projects the resulting event into API state.

Step	Who does it
Encode the call	Backend (`/prepare`, `/tx-intent`, `*/deposit-intent`)
Sign and broadcast	Your wallet
Update API state	The indexer, from the on-chain event

Never treat a mined transaction as a completed action. Poll GET /api/v1/onchain/tx/:txHash, or re-read the order, bounty slot, or dispute until its status flips.

Getting Started

Core Concepts

Integration Guides

Reference

Chains

Live config endpoint

Settlement currencies

Contract addresses

BNB Chain (56)

Base (8453)

Broadcasting transactions

​Chains

​Live config endpoint

​Settlement currencies

​Contract addresses

​BNB Chain (56)

​Base (8453)

​Broadcasting transactions

Chains

Live config endpoint

Settlement currencies

Contract addresses

BNB Chain (56)

Base (8453)

Broadcasting transactions