ALPHANET POC·x402 over account blocks

A live demonstration on Zenon

The payment rides inside the request.

Ask this server for something and it answers 402 with a price. Your browser signs a Zenon transaction and never broadcasts it — the signed block goes out as an HTTP header instead. The server publishes it, waits for a Momentum, and only then answers. Real blocks, real settlement, paid in ZBTOKEN.

Demo keys

Do not send anything to the addresses below. Each wallet's key is generated in the browser, single-use, with no recovery path, so anything sent to it is gone. Plasma fusion is safe — a refundable deposit, not a transfer.

01 · The loop

Six steps, no human in the middle.

Nothing below asks you to approve, connect or confirm anything. The client reads the price, pays it and carries on — which is the whole point: software that can buy what it needs, one request at a time.

  1. 01Walleta keypair, in this tab
  2. 02Faucetone payment’s worth
  3. 03Receivemaking it spendable
  4. 04402asking, unpaid
  5. 05Signa block, unpublished
  6. 06Settlepublished, confirmed
02 · The terms

The server names its price.

Price, asset, payee, chain. Machine-readable, so the client can decide whether to pay without asking anyone.

Run the flow to see a real 402 and its terms.

03 · Signed, not broadcast

The transaction travels as a header.

A normal Zenon UserSend, with a digest of the terms sealed into its data field. The browser signs it and stops. Only the server being paid broadcasts it, so payment and delivery are one round trip instead of two.

Run the flow to sign one.

Built on

The protocol is edgepillar/zenon-x402-poc. The wire format, the intent digest and the preflight are its design, ported here. It ships mock mode only; this page adds a pinned Alphanet chain profile and settles for real. Its limitations still apply.