Skip to content
SineraDocs

ATP binding and chain reads

How the MCP server pins one ATP deployment, verifies every chain read, and reports provenance.

The ATP MCP server reads one pinned ATP deployment and refuses to answer if the chain does not match the pin. This page explains the pin, the checks on each read, and what the server never writes. For the protocol itself, see Networks and Atoms and lifecycle.

Not deployed

No live read yet

The server is not deployed and has been tested locally against fakes only. No live chain read has been performed, so the pin has never been compared with the actual chain. The pin and the ABI fragments are checked against source material offline. The live match is unverified. There has been no independent security review yet.

The pinned deployment

Nothing about the deployment is learned from the RPC at runtime. The reader compares the chain with its built-in pin and fails with UNSUPPORTED_DEPLOYMENT on any mismatch.

ItemValue
Deployment idbsc-testnet-20261008
Protocol version2.4.0
ChainBSC Testnet, chain id 97
Config id0x7abc539244cf4517dc09c0ea4bb3458eddecf79a2c37249e740da03f3d5b36bd
AtomCore0x5db8ce9604c03cc43a5dc9dc20fb76583ba5a46c
DelegationManager0x1624463de4727d91d027fcc16c6b3d932cbd38d5
Also pinnedIntentValidator, ProtocolConfigRegistry, ArbitrationCaseManager

An older testnet deployment with a different config id and addresses exists. It is a distinct deployment and is not supported. ATP 2.4.0 is an implementation candidate and mainnet is not approved.

What is checked on every read

  1. Read the finalized block (number, hash, timestamp) and eth_chainId.
  2. Refuse a finalized block older than 120 seconds, or dated more than 30 seconds in the future. The window defaults to 120 seconds and can be set from 5 to 900 seconds. The error is STALE_STATE.
  3. Verify the runtime code of every contract the read executes, at that block number. Length, keccak256 and SHA-256 must all agree with the pin.
  4. Make every eth_call at that same block number. Decode strictly and re-encode canonically.
  5. Re-read the header by number and require the same block hash.

Unknown enum ordinals, unknown session action bits, an empty action mask, a foreign config id or protocol version, and non-canonical ABI words all fail closed. Only the exact AtomNotFound(atomId) and SessionUnknown(sessionId) errors for the queried id mean "not found".

ABI provenance

The reader calls a small set of hand-reviewed ABI fragments and nothing else:

ContractFunctions read
AtomCoreatomStatus, receiptData
DelegationManagersessionTerms, isSessionActive, sessionEpoch, rootEpoch, lifetimeSpent, protocolVersion

There is no write, simulation, log scan, multicall or caller-chosen target. Each pinned value was derived offline from read-only sources and recorded with its file path and SHA-256. The runtime was rebuilt from compiler output plus immutable values and matched to the recorded hashes for every pinned module. Enum order follows the ABI ordinals, for example AtomState is PENDING_ACCEPTANCE, PENDING_REACCEPTANCE, ACTIVE, DISPUTED, FINALIZED.

Provenance returned to callers

Every chain result carries an evidence object. It always reports finality: "FINALIZED" and runtimeVerified: true. A read that cannot establish them fails instead of returning a weaker value.

"evidence": {
  "source": "ATP_CHAIN_READ",
  "chainId": 97,
  "deploymentId": "<pinned deployment id>",
  "protocolVersion": "2.4.0",
  "configId": "0x7abc...36bd",
  "blockNumber": "1000000",
  "blockHash": "0xbbbb...bbbb",
  "blockTimestamp": "1800000000",
  "finality": "FINALIZED",
  "runtimeVerified": true
}

The values are illustrative and the hashes are shortened. Block finality is not the Atom state FINALIZED. See Tool reference.

What MCP never writes

MCP reads and reports. It does not write Atom lifecycle, escrow, settlement, inventory or job state.

DomainControlling authorityMCP does
Atom lifecycle and outcomeAtomCoreReads with block provenance, never writes derived lifecycle
Escrow and settlementEscrowVault and SettlementEngineNever treats a tool result or transaction hash as settled
Registered inventoryAssetRegistryKeeps business quantity apart from registered inventory
Delegated action scopeRoot-created DelegationManager sessionReports session facts. The backend and signer verify before executing.
Orders, approved terms, jobs, idempotencyThe owning application's backendConsumes its adapter API

An AtomId is bound to contract, chain, Root and salt. It is not an order id, so use the full locator: chain id, AtomCore address and Atom id. See Authority model and Delegation.