What changed
Accord completed a live Base Sepolia pilot for its EVM contract rail. The run used a deployed AgentPayReserveV0 contract, Circle test USDC, live transaction hashes, Accord verification receipts, settlement receipts and conformance output.
The goal was narrow and important: prove that an AI-agent payment flow can move from agreement to verification to settlement with external on-chain evidence.
What was tested
The pilot validated a full paid-tool lifecycle. A buyer funded a Base Sepolia reserve with test USDC, Accord created an agreement for a paid task, the Base rail issued an on-chain Note, a verifier accepted the task output, the seller redeemed the Note and Accord produced a settlement receipt that referenced the verification receipt.
The reserve contract used in the run was 0x08e27593a6e89ed04eB0eBAe249A460657d3Cc89. The token contract was Circle test USDC at 0x036CbD53842c5426634e7929541eC2318f3dCF7e.
The receipt chain
The Accord record starts with an Agreement Object. That agreement binds the buyer, seller, task, price, rail and verification requirements. The live run then produced an accepted Verification Receipt for the task output and a settled Settlement Receipt for the redeemed Base Sepolia Note.
The passing run also checked that a wrong task output was rejected with TASK_HASH_MISMATCH. That negative check matters because payment alone is not completion; settlement should remain bound to the verified work.
External transaction evidence
The external evidence includes contract deployment, ERC-20 approval, reserve top-up, Note issuance and Note redemption on Base Sepolia. The settlement transaction is 0xf6ab7267f1ff489524d06884effa045f9430858509348cbf30970f34cb741f92.
The deployed reserve contract can be inspected on BaseScan at 0x08e27593a6e89ed04eb0ebae249a460657d3cc89.
Safety posture
This pilot does not certify Accord for mainnet use. That boundary is deliberate. Base Sepolia writes are allowed for this testnet rail, but Base mainnet remains default-deny unless exact deployed bytecode is approved through signed audit manifests.
The live run explicitly confirmed the audit gate: Base Sepolia writes were allowed, Base mainnet default writes were denied and the mainnet denial code was UNAUDITED_CONTRACT.
Result
The pilot passed. Accord conformance reached L4: L0 26/26, L1 13/13, L2 24/24, L3 12/12 and L4 16/16.
The important outcome is not that testnet tokens moved. The important outcome is that the movement was tied to an agreement, a verifier decision, a settlement receipt and a conservative mainnet gate.
FAQ
Is this a mainnet launch?
No. This is live Base Sepolia testnet evidence. Accord remains not certified for mainnet until signed audit manifests explicitly allow exact deployed bytecode.
What did the pilot prove?
It proved a live agreement, verification and settlement lifecycle on the Base Sepolia EVM rail, including on-chain Note issuance and redemption.
Why does the audit gate matter?
It prevents a successful testnet proof from being mistaken for permission to use unaudited mainnet contracts.
Sources and references
Base Sepolia live pilot evidence
Dated pilot record with receipts, transaction links, audit-gate result and conformance output.
AgentPayReserveV0 on Base Sepolia
Deployed reserve contract used for the live testnet rail pilot.
Settlement transaction
Live Base Sepolia redemption transaction from the passing run.
Open live pilot evidence
Inspect the dated Base Sepolia result with receipts, explorer links and conformance output.