A quick check before any argument: pick one of my proven actions and verify it in your browser — no server, no account, and every prefilled trust input is disclosed and replaceable with your own. That is the shape of the thing this post is about.
The payment stack is real — and it stops at the payment
Two efforts are standardizing how autonomous agents transact. x402
revives HTTP 402 as a payment rail: a resource replies 402, the agent settles
on-chain, and retries. Its community is actively standardizing payment receipts —
an offline
proof-of-payment-conditions draft (with a
research-coalition
liaison toward the individual IETF submission draft-vauban-x402-stark-receipts),
a Bitcoin-anchored
provenance proposal, and a
post-quantum
extension proposal. AP2 — the Agent Payments Protocol, donated
to the FIDO Alliance in April 2026 — sits one layer up, producing authorization
evidence for commerce: mandates expressed as W3C Verifiable Credentials, chained into a
non-repudiable, auditable record of what a user authorized an agent to buy.
Both are real, and both are good at their job. I'll say the honest things plainly: x402's core settlement response is a transaction hash, but signed receipts exist as an extension and the ecosystem is standardizing more — so it is not true that "x402 has no receipt." And AP2 is a genuine, auditable authorization trail, not "just a signature." Two facts remain, though. Both are scoped to payment and commerce by design. And AP2's signatures are classical, with no published post-quantum roadmap.
The gap they leave is the same one: none of them prove an agent's non-payment acts — the commit, the deploy, the model it published, the config it changed. That is not a flaw; it is out of scope. But it is the part that matters when you are trying to prove, later, what an agent actually did.
The seam already has a name
The payment-receipt draft names this seam for itself. Its receipt carries an
action_ref — 32 opaque bytes whose preimage, in the draft's
own words, "the receipt format does not interpret… [it is] defined by the work layer."
Elara is such a work layer. A payment receipt can point at an act digest; something has to
be that act's proof. (That draft is an individual IETF submission — prior art
naming the seam, not an endorsed standard; I cite it as exactly that.)
What Elara puts there
Elara is shipped work-layer proof for any signed agent act: post-quantum
(FIPS 204 ML-DSA / FIPS 205 SLH-DSA), bound to a revocable on-mesh
mandate from a named principal, and verifiable fully offline by a
signing-incapable MIT/Apache verifier. It composes with the payment receipts above through
that action_ref field rather than competing with them: the payment stack proves
the money moved; the work layer proves the act — the commit, the deploy — happened, under
whose authority, and whether that authority still held.
Honest status
The mandate layer is an observational v0, and the docs say so wherever it matters. What it enforces today: the who (agent-identity binding), the when (validity window), revocation (read-time, front-run-proof, keyed to the principal), and the sub-delegation chain-walk. Out-of-mandate acts are recorded and flagged, never silently dropped — but those flags carry zero consensus weight in v0, and fine-grained scope enforcement waits on a multi-validator network and a signed scope taxonomy. The mesh behind this site is a small self-hosted testnet run by one operator; the trust-minimization is in the cryptography you can check, not in a decentralized network we haven't built yet. And the demonstrated path is the offline envelope — a self-contained proof the verifier checks with no network — not a live queryable feed, since acts age out of the hot tier like everything else on the mesh.
See it run
You can check a proof of this exact shape right now: the
in-browser verifier takes a signed bundle and returns
CONSISTENT or NOT AUTHORIZED, with its honest-scope caveats visible
(offline it proves the chain given the bundle — never that a record is on-chain, or
that a revocation wasn't withheld; that is the node's answer). A minimal runnable demo pairs
an x402 testnet payment with an Elara work-layer proof end to end and shows the same offline
verdict verbatim — navigatorbuilds/x402-elara-demo. And
how this compares — precisely, conceding every point worth conceding — to x402, AP2, W3C
Verifiable Credentials, sigstore, C2PA, Certificate Transparency and "just a blockchain"
lives in the
differentiation
FAQ.