Skip to main content
AVAILABLE · READ-ONLY · SIGNED SNAPSHOTIssued only when the server’s signing key is configured. Signed does not mean endorsed. See what you can use today for every surface side by side.
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.

What a packet’s recommendation says today

A packet uses the Stablecoin Vault’s recommendation vocabulary: Monitor, Prepare, Migrate, Vault Candidate, or Unsupported.
A signed packet is derived on the server from the wallet’s scheduled facts, but that derivation cannot currently use its signature exposure or dormancy and selects no recommendation state. So a server-issued packet currently reads Unsupported, with “Insufficient evidence” in place of a score and as its only risk driver. The unsigned previews on the Stablecoin Vault page and in the Migration Path panel can show any of the five states, but the server does not issue them. The signed share link beside the Stablecoin Vault preview issues the separate server packet described here.

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 detects content changes relative to the embedded hash; it is not proof of authorship. The issuer signature is the authenticity check that proves WalletWall’s signing key signed the packet bytes.
The content hash (evidence.reportHash) is SHA-256 over canonical JSON — recursively key-sorted, with no insignificant whitespace — after evidence.reportHash is set to null and issuerSignature is removed.To verify independently:
1

Download the packet JSON

Get the raw JSON payload for the packet.
2

Build the hash payload

Set evidence.reportHash to null and remove issuerSignature.
3

Canonicalize

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

Hash and compare

SHA-256 the canonical bytes and compare against the packet’s embedded evidence.reportHash. A mismatch means the packet bytes and embedded hash do not agree; a truncated link is one common cause.
Because anyone can construct a packet and recompute this hash, a valid reportHash is an integrity check, not an issuer-authenticity claim.

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 signing key signed the packet WalletWall’s server derived at the stated time, nothing more.

Where a packet sits among WalletWall’s artifacts

WalletWall produces three report-shaped artifacts, and they are deliberately different things: The progression a WallPrint belongs to is evidence → assessment → deliberate disclosure → WallPrint record → receipt and public resolver. A readiness packet is not a step on that path: it is the application’s own signed snapshot, derived from its scheduled data, and sharing one publishes it to whoever holds the link.

Where to go next

Stablecoin Vault & Vault Simulator

The readiness journey and the five recommendation states a packet’s format uses.

Migration Readiness

The shared risk tiers, and how they differ from the Stablecoin Vault’s recommendations.

WallPrint

The disclosure record for MCP evaluations, with its receipt and public resolver.

Data Serving Architecture

The scheduled data a packet is derived from, and why it carries a data instant rather than a live reading.