Skip to content
SineraDocs

ATP overview

What the Atomic Transaction Protocol is, which version Sinera documents, and which contracts make up the protocol.

The Atomic Transaction Protocol (ATP) is Sinera's settlement protocol for commercial commitments. It holds the funds for a deal in escrow, tracks the deal through a fixed lifecycle, and pays out the result by rule. No discretionary admin picks an outcome.

Implementation candidate

Maturity

ATP version 2.4.0 is an implementation candidate. Its only public deployment is BSC Testnet (chain id 97). Mainnet is not approved, and the release gates are still open. See Conformance and release gates.

What ATP does

ATP is built around the Commercial Atom: one commitment between a Buyer and a Seller that can reach its own final result independently of any other commitment. Each Atom has:

  • two fixed principals, called the root Buyer and the root Seller;
  • a payer, the address that funds escrow (the payer never replaces either root);
  • an escrowed amount in an approved ERC-20 token;
  • optional inventory tied to the deal, tracked by the asset registry;
  • deadlines for acceptance, execution and challenge; and
  • one terminal outcome: RELEASE, REFUND, SPLIT, CANCELLED or EXPIRED.

The model that describes commercial commitments in general is called CAEM. ATP is the reference protocol that realizes it as on-chain state transitions. Applications, agreements and AI planning sit above ATP. External systems such as wallets, funding providers, indexers and document stores sit around it. None of them is a source of commercial truth for an Atom.

Version and scope

ItemValue
Protocol version2.4.0
Signing standardEIP-712, domain version 2.4.0
StatusImplementation candidate
Public deploymentBSC Testnet (chain id 97)
SolanaRuns on a local validator only. No public deployment
ProductionNot approved

ATP 2.4.0 is a fresh deployment. It is not an upgrade of an earlier stack, and it reuses no earlier address, balance or signature.

Contracts

The protocol is split into modules. Each module owns one domain and is forbidden from acting outside it. The table lists the contracts you meet most often.

ContractWhat it ownsWhat it cannot do
AtomCoreAtom identity, lifecycle state, deadlines, terminal outcomeSettle by admin discretion
EscrowVaultExact ERC-20 escrow accounting and transfersChoose an outcome
SettlementEngineValidating and executing a terminal decision that Core authorizedStart an outcome of its own
AssetRegistryInventory, reservations and conserved final disposition of assetsChoose a dispute decision
SettlementFeePolicyWhich tokens are admitted and which fee rates applyChange a live Atom's fee terms
DelegationManagerBounded sessions created by a root, and their spend trackingOpen or resolve a dispute
SessionExecutorAn optional prefunded payer that can only create an Atom for its own sessionAct as a root or hold broader authority

The deployment also includes a protocol config registry, an intent validator, an arbitration case manager, an award authority, a time executor, a receipt contract and a metadata registry. Their roles appear in the pages below.

AtomCore is the only writer of an Atom's lifecycle state. SettlementEngine is the only terminal coordinator for a configuration. Everything else reads or serves one of those two.

How the pieces fit together

  1. A Buyer and a Seller agree on terms. The Buyer signs an intent and the payer funds escrow through the EscrowVault. Creation, escrow and any inventory reservation happen in one transaction.
  2. The Atom moves through its lifecycle. See Atoms and lifecycle.
  3. A Buyer can act through a bounded session instead of signing each step. See Delegation sessions.
  4. When the Atom finalizes, the settlement engine pays Buyer and Seller and records any fees. See Fees and settlement.

For definitions of terms such as Atom, root and escrow, see the glossary.