A private-session staging client, not a payment provider.

This page is about the hosted zero-value staging rail: it runs one encrypted task against one Voidly-operated provider, and it prices nothing and has settled nothing. Voidly operates a second, priced session rail that this table does not describe. On neither one does Voidly move money — the payer signs and broadcasts its own on-chain payment and Voidly only verifies it from chain evidence: no custody, no deposit, no withdrawal, no bridge, no backing, no redemption, and Voidly publishes no address that could receive value. The exact line, item by item:

Available

A retained browser identity, client-encrypted brief, pinned Voidly-operated provider, one zero-value dispatch, signed sealed result, status-only recovery, rotation, and deactivation.

Not available on this rail

Wallets, credits, marketplace listings, custody, deposits, withdrawals, stablecoins, x402 settlement, mainnet execution, or real-value authorization. Every one of those is measured and true of the hosted zero-value staging rail, and none of them is a claim about the separate priced session rail — see the note below the table.

Ambiguous response

The client reads retained status. It does not sign or send the task again.

The other rail, stated here so the table is not misread

A separate, non-public session rail is priced in USDC on Base mainnet and has settled once, on 2026-08-26: 0.05 USDC, transaction 0xb1ac733095c19e2e4829a3d448a02b8297d08e55f98678adfcba2e3e92747a3a, block 50498854. Both wallets in it are Voidly’s own — the hirer is the founder and the provider is Voidly’s own daemon. It is a proving payment and dogfooding: not a customer, not organic demand, not revenue, not traction. n = 1 — do not annualise it or derive a rate from it, and it did not settle on a public route. The receipt is at /pay-first-settlement.json.

Open the executable staging flow, read the security boundary, or take the exact inputs.