Gateway Nanopayments Primer
Circle Developer Notes / 0.002400 USDCreceipt evidence
0x83d68619...ecc87f
paid to creator0.002400USDC
forum routed
Circle Developer Notes
This receipt binds a source payment to the answer that used it. The previous hash links it into the append-only attribution ledger.
receipt hash0x83d68619c1c42f5d4746ab970f4b3287f9c92a735ed40d20e1ab8bab4decc87f
previous hash0x2f28928c568be532e0106322b55e4c7b4ecdd9b145f265538a6fdb326674eccb
query id0xcfa83524563443f2
source idcircle-gateway-nano
creator wallet0x2222...2222
created at2026-06-23T14:54:41.275Z
payment resourceforum-fee-router:0xeff9bc359e8f2a5eabce55af3f1bb24f98eabf59
query payment hashnot reader-paid
payer0x4164F5B52ecc6F847f03071A287b0B59954cbcEe
transaction0x143e51f5...dce0fc
FeeRouter split27
FeeRouter createSplit0x47d4841e...347aea
FeeRouter pay0x143e51f5...dce0fc
answer context
How do Forum covenant mandates enforce agent spend control on Arc?
Forum covenant mandates enforce agent spend control on Arc through enforceable budget bounds and receipt publication. Forum-style mandates bind an agent's budget, publish cryptographic receipts of all transactions, and make spend controls enforceable rather than advisory. This works on Arc because Arc is designed for stablecoin-native settlement with USDC, sub-second finality, and app kits for payment workflows. When combined with x402 payment protocols (which enable sub-cent nanopayments), agents can make granular, auditable purchases while staying within their mandated budget envelope. The receipts are published on-chain or in a verifiable ledger, making violations transparent and enforceable by the protocol or governing entity.
Open answer evidenceExplains the x402 payment mechanism (EIP-3009 batching) that enables sub-cent enforcement without per-payment gas, critical for granular spend control at scale.