FAQ

No. LOPW is an x402 v2 extension named lopw. Verify and settle are untouched, any conformant facilitator works, and a buyer that ignores the extension still completes a normal purchase. Wire format

No. The payment settles normally. What is locked is the seller’s stake, once, for all its calls. A claim pays from that stake.

min(max_claim, stake remaining) in the stake token, paid to the buyer named in the receipt in the same transaction as the claim. max_claim is in every offer, so the buyer knows the cover before paying.

Six conditions: two different receipts for one payment (P1), a receipt citing other terms than the offer (P2), data older than promised (P3), a status the seller promised not to charge for (P4), a response larger than promised (P5), and a served value further from a named oracle than the promised tolerance (P6). Predicates

No. Quality, latency and availability seen only by the buyer cannot be proven from evidence alone and are out of scope. A missing receipt or an invalid signature is not slashable either: the SDK reports it as an untrusted response.

No. A paid claim is recorded under (service_id, payment_reference); a second claim for the same payment fails with AlreadyClaimed, whichever receipt it presents.

Yes, anyone holding the signed offer and receipt may submit. The payout still goes to the buyer named in the receipt, so there is nothing to gain by racing.

It cannot do so in time. A full exit waits the unbonding delay: the largest claim window the service ever registered plus one hour. The stake stays slashable throughout. Unbonding

It is rate-limited: within one epoch (one unbonding delay long) total slashes may not exceed 50% of the stake at the epoch’s start, so stake can leave no faster than a normal withdrawal would allow. Threats

At least 100 USDC, set as min_stake at registration. Agents may demand more through their policy, and the stake is public before payment.

A one-off registration fee and an annual fee on stake held, both in the stake token and both possibly zero; and, when it breaks a promise, the payout. Economics

The oracle named in the terms is trusted: a wrong observation produces a wrong outcome. A missing observation makes the claim NotVerifiable: nothing is paid and nobody is penalised.

Built first on Stellar with Soroban, USDC and x402; designed for every chain. The offer, receipt, validator interface and claim semantics are portable; encoding, signatures, contract functions and the payment rail are per binding. Bindings

The demo replays a real claim paid on a live network, and the proofs page lists every transaction and test. Proofs and scenarios

Agents start here: Markdown twins of every page, /llms.txt, /llms-full.txt, JSON Schemas and test vectors.