SKIP TO CONTENT

Ethereum standard

ERC-8203: Agent Offchain Conditional Settlement

ERC-8203 is a Draft standard for paying AI agents. Agents exchange signed messages off the chain and share one way to settle or refund them.

Status: Draft, open pull request

ERC-8203 is a Draft. It is still an open pull request (PR #1614) on the ethereum/ERCs repository. It is not merged, it has no page on eips.ethereum.org yet, and its text can still change.

Status
Draft, open pull request
My place in the author list
Co-author, 2nd of 3
What I did
Co-author, listed second among the draft's three authors. Xianrui Qin is the first author. I also wrote the reference implementation.

Checked against the primary source on .

What is it?

AI agents can make thousands of small payments to each other. Paying a network fee for each one costs too much. ERC-8203 lets two agents exchange signed promises off the chain and settle on the chain only when it is needed. It defines the message format and a small contract interface. It reuses existing payment channel systems for everything else.

Simple analogy

Think of a running account at a shop. The shop writes down each purchase, and you pay the total at the end of the month. ERC-8203 is the agreed format of that list, plus the rule for what happens if someone does not pay.

How it works

  1. Two agents open a channel

    They use an existing payment channel system. ERC-8203 does not define this step.

  2. The payer signs a conditional lock

    The lock is a signed message with the amount, the expiry time and the condition. It stays off the chain, so it costs no network fee.

  3. The receiver does the work and shows a proof

    The proof shows that the condition is met. In the normal case both agents simply update their balances off the chain.

  4. Settle or refund on the chain

    If the two sides disagree, the receiver calls settleConditional with the proof. If the expiry time passes first, the payer calls refundConditional.

Key concepts

ConditionalLock

The signed message that two agents exchange. It names the payer, the receiver, the asset, the amount, a fee, an expiry time and the condition that releases the payment.

Condition and proof

A payment is released only when a condition is met. The proof of that condition can be a signature, an attestation or a timeout. The draft does not impose one proof system.

Settle or refund

The contract interface has two actions. settleConditional pays the receiver when the proof is valid. refundConditional returns the funds to the payer after the expiry time.

Host framework

ERC-8203 does not open, close or dispute payment channels. An existing channel system does that work. ERC-8203 only adds the conditional payment on top.

Illustrative use cases

Pay per callAn agent pays a small amount each time it calls an API.
Illustrative use: the agent signs one small promise for each call. The provider settles all of them later in one transaction. My metered billing profile on GitHub describes this pattern. It is a guide, not part of the standard.
Pay when the work is provenThe payment is released only when the result is delivered.
Illustrative use: one agent locks a payment for a task. The other agent receives it when it shows the agreed proof. If no proof arrives before the expiry time, the payer gets a refund.
Streaming paymentsMany small payments in a row, without a network fee for each one.
Illustrative use: an agent pays for compute or data by the second. The two sides exchange signed updates off the chain and settle the total on the chain later.

Technical specification

Selected declarations from ERC-8203, shortened for explanation. Referenced interfaces and omitted methods are in the full text linked below.

erc-8203.sol
// From the ERC-8203 Draft (PR #1614). Shortened. The text can still change.
interface IAgentConditionalSettlementExtension {
    enum LockStatus { None, Locked, Settled, Refunded }

    // Pay the receiver when the proof is valid.
    function settleConditional(
        bytes32 channelId,
        ConditionalLock calldata lock,
        SettlementProofRef calldata proofRef,
        bytes calldata proof
    ) external;

    // Return the funds to the payer after the expiry time.
    function refundConditional(bytes32 channelId, bytes32 lockId) external;

    function lockStatus(bytes32 channelId, bytes32 lockId) external view returns (LockStatus);
    function supportsConditionType(bytes32 conditionType) external view returns (bool);
    function supportsProofType(bytes32 proofType) external view returns (bool);
}

Frequently asked questions

Is ERC-8203 a finished standard?

No. ERC-8203 is a Draft in an open pull request (PR #1614) on the ethereum/ERCs repository. It is not merged and it can still change. Do not treat it as final.

Who wrote ERC-8203?

The draft lists three authors in this order: Xianrui Qin, Adam Boudjemaa (me) and Jimmy Shi. Xianrui Qin is the first author. I am the second author and I wrote the reference implementation.

What problem does ERC-8203 solve?

AI agents make many small payments. A network fee on each payment costs too much. ERC-8203 gives agents one shared format to promise a payment off the chain and settle it on the chain later.

Does ERC-8203 replace payment channels?

No. It works on top of an existing payment channel system. That system still opens, closes and disputes the channels. ERC-8203 only defines the conditional payment and the settle and refund actions.

Can I use ERC-8203 in production today?

Be careful. The reference implementation shows that the draft can be built, but the standard is not final. An interface that changes later would break your code.