Networks and deployments
Which networks run ATP today, the public BSC Testnet contract addresses, and how to read them in the Explorer.
ATP 2.4.0 has one public network: BSC Testnet. Everything else is either local or not approved. This page lists each network and the public contract addresses you can check yourself.
Implementation candidate
Network status
| Network | Status | Notes |
|---|---|---|
| BSC Testnet (chain id 97) | Deployed | The only public ATP deployment. For testing only |
| Solana | Local only | Runs on a local validator. No public deployment, and nothing on devnet or mainnet |
| Mainnet (any chain) | Not approved | Production promotion is blocked. See Conformance and release gates |
Testnet only
Testnet tokens have no value. Do not send real funds to any address on this page. A name or ticker is not proof that a contract is authentic, so check an address against this page or an official Sinera page before you use it.
BSC Testnet deployment
The active ATP 2.4.0 deployment on BSC Testnet has the deployment id bsc-testnet-20261008. It is a fresh stack deployed on 8 October 2026. The ATP Explorer, the Developer Portal and the ATP MCP server all read this deployment.
After deployment, a live test run on testnet recorded every check as passing, with every transaction finalized and no reverted receipts. The evidence review only read the recorded files. It did not approve the deployment for production. Canary settlement and a soak test are still outstanding, and the award committee on this testnet is controlled by one party. See Security model.
An earlier testnet stack
An earlier ATP 2.4.0 stack was deployed on BSC Testnet on 20 September 2026. It is not the deployment the Sinera products read. Use the addresses below.
Contract addresses
| Contract | Address |
|---|---|
ProtocolConfigRegistry | 0xe13eb0ab51da756a3595644b3b8ba9620131a181 |
IntentValidator | 0xf93fd14b260e240e01d3aadb2b8ac2541619ee9b |
AtomCore | 0x5db8ce9604c03cc43a5dc9dc20fb76583ba5a46c |
EscrowVault | 0x0edeeb286d338dea2a8315f7de7aba096e59649b |
SettlementFeePolicy | 0x8f75695794d47cb9c53b0494bb6038bfd534531a |
SettlementEngine | 0x47bd36ed2d09ad945faafc4b6cca7cfaba125e33 |
AssetRegistry | 0x321176242797a9a07b5c317bdbba647d3e3be514 |
DelegationManager | 0x1624463de4727d91d027fcc16c6b3d932cbd38d5 |
ArbitrationCaseManager | 0xd507edd7a0cde5f6980afadba1798c57e2093b2b |
ArbitrationAwardAuthority | 0x60a5c7cfcf5a09a36e8311fbd36246d2cfe7c959 |
TimeExecutor | 0xef3903f44b40a5253454bc0339a3ab13efe43cd2 |
ATPMetadataRegistry | 0x750308185dc93f3d0e2892dc592f7659e96b5abe |
ATPReceipt | 0xba7dd2eb89c47a686e8c6c8f0f5125351d5036f8 |
SessionExecutorFactory | 0x1721b784acdd2f1f691ec032dca3b86a030b2294 |
The active configuration id is:
0x7abc539244cf4517dc09c0ea4bb3458eddecf79a2c37249e740da03f3d5b36bdThe deployment spans blocks 135492193 to 135492730. Each module's runtime code hash is recorded with the deployment, and the Explorer's Verify a deployment page checks the live code against those hashes.
SIN is a planned token. It has not been issued and has no contract address listed here. See SIN token (planned).
Read the deployment in the Explorer
The ATP Explorer reads this deployment without a wallet. Use the network control in its header to switch networks. The whole Explorer follows your choice, and you can link to a network with ?network=<id>, for example /atoms?network=solana.
| Explorer shows | Meaning |
|---|---|
| On-chain badge | Records were read from the chain at the snapshot block |
| Ledger unavailable | The chain could not be read, or the contracts did not match the deployment record. No records are shown |
| Not deployed | The selected network has no recorded deployment. Solana shows this |
| Sample data badge | This copy runs on example records. Treat figures as examples |
A snapshot is the chain at one finalized block. Before it shows any record, the Explorer checks that the contracts on chain match the deployment record. Some values are not stored on chain, so the Explorer shows them differently:
- Deadlines are rebuilt from the Atom's verified history.
- Assets appear by id, not by name or unit.
- Object labels are not on chain.
For a walkthrough, see Explorer getting started.