Skip to main content
A readiness packet is a dated, versioned, read-only snapshot of one wallet’s stablecoin vault-readiness assessment — the artifact you can hand to a treasury committee, a DAO forum, or a due-diligence thread. It travels as a link:

​
What a packet is — and is not

A packet is

A self-describing summary: recommendation, score band, risk drivers, evidence references, data-freshness stamps, generation time, and WalletWall’s boundary statements embedded in the data itself.

A packet is not

A packet is not an endorsement, attestation, or certification of the wallet it describes, and never a custody, insurance, or return claim. Readiness signals are research heuristics. A packet with a missing score honestly reads “insufficient evidence” — never zero.
Boundary statements are non-strippable: a payload without them is rejected as invalid by the packet page.

​
The privacy model

Everything after the # is a URL fragment. Fragments are never sent in HTTP requests, so the packet content — including the wallet address — never reaches WalletWall’s servers, CDN logs, or analytics when a link is opened. Analytics page-view URLs additionally redact any payload-sized fragment.
Sharing a link is still publishing: anyone holding it can read the packet. A “share without address” variant is issued separately for redacted sharing.

​
Two independent checks

Every issued packet carries two verifiable properties: The hash alone proves a link wasn’t corrupted; only the signature proves WalletWall issued the content.
The content hash (evidence.reportHash): SHA-256 over the packet’s canonical JSON — recursively key-sorted, no insignificant whitespace, with evidence.reportHash set to null and the issuerSignature field removed before hashing.To verify independently:
1

Download the packet JSON

Get the raw JSON payload for the packet.
2

Apply the two exclusions

Set evidence.reportHash to null and remove the issuerSignature field.
3

Canonicalize

Recursively key-sort the JSON with no insignificant whitespace.
4

Hash and compare

SHA-256 the canonical bytes and compare against evidence.reportHash. A mismatch usually means a truncated link — ask for the JSON file.

​
Fail-closed by design

Issuance is server-side only and fail-closed: a deployment without a signing key answers 503 and never issues an unsigned packet. Clients ship without a pinned verification key until one is published, and until then treat every payload as unverified. Signed still does not mean endorsed — the signature proves WalletWall’s server derived the content from its data at the stated time, nothing more.