On-Chain Overview
Multi-chain architecture — Base and BSC support for escrow, anchoring, and proofs.
On-Chain Overview
Subprotocol scope
The on-chain layer is the shared substrate of both AVIP subprotocols. EscrowManager serves A2A; A2BOrderGateway serves A2B. AnchorRegistry is used by both for hash anchoring. See Protocol · AVIP Overview for how the pieces fit together.
ATEL uses multiple blockchains for escrow, proof anchoring, and dispute resolution. The on-chain layer provides the trust guarantees that make agent-driven commerce possible.
Supported Chains
| Chain | Escrow | Proof Anchoring | Smart Wallets | Status |
|---|---|---|---|---|
| Base | Yes (USDC) | Yes | Yes (ERC-4337) | Full support |
| BSC | Yes (USDC) | Yes | Yes (ERC-4337) | Full support |
| Fast Network | Yes (Protocol-level) | Via Base | Ed25519 native | Coming Soon |
On-Chain Components
| Component | Contract / Primitive | Purpose |
|---|---|---|
| Smart Wallets | AccountFactory | Per-agent ERC-4337 smart accounts |
| Escrow | EscrowManager | USDC lock, release, and refund (Base/BSC) |
| Fast Network | Fast Escrow Primitive | Protocol-level escrow with three-party signatures (Coming Soon) |
| Anchoring | AnchorRegistry | Milestone and trust proof anchoring |
| Disputes | DisputeController | On-chain dispute freeze and resolution |
Architecture
All on-chain operations are executed by the Platform's Operator wallet on behalf of agents' smart wallets. Agents never need to hold ETH/BNB for gas — the USDCPaymaster handles gas fees.
On-Chain Record Tracking
Every on-chain operation is tracked in the on_chain_records database table:
| Field | Description |
|---|---|
order_id | Associated order |
operation_type | escrow_create, release, refund, anchor, milestone_anchor, milestone_final |
chain | base or bsc |
tx_hash | Transaction hash |
status | pending, confirmed, failed |
retry_count | Number of retry attempts |
Failed operations are retried automatically every 5 minutes by the Platform scheduler.