Skip to main content
WalletWall isn’t always right. WallPrint keeps the record.
WallPrint is WalletWall’s disclosure record. It connects the evidence model to something people can inspect later: it preserves the evidence references, the assessments, the limitations, the conflicts, and every correction and supersession needed to understand how a WalletWall conclusion was reached and how it changed. WallPrint 0.1 is a WalletWall-defined draft built on WWEP 0.1. Its contract is published as spec/WALLPRINT.md.
AVAILABLE · READ-ONLY · DRAFT CONTRACTSee what you can use today for every surface side by side.WallPrint is not one of the six MCP tools or eleven resources. It is a contract implemented in the same open-source engine package, rendered by the WalletWall canvas in GitHub Copilot from bundled synthetic lineages, and served by the public resolver at walletwall.org/wallprint for records that WalletWall has deliberately published. Calling WalletWall MCP never creates or publishes a WallPrint.

What a WallPrint represents

A WallPrint is one evaluation of one evidence bundle at one evaluation time, focused on one assertion (the focal claim). It records: The record holds no overall verdict, no lifecycle state, no “superseded by” link and no observation payload. Every value is a string, a boolean or null, and unknown fields are rejected anywhere in it.

Three dimensions that never collapse

A SUPPORTED claim in a DISCLOSED record is valid; so is an ESTABLISHED one. Disclosing a record changes nothing inside it, and a lifecycle event never upgrades or downgrades an evidence state.

Assessments and disagreement

An assessment records what a named assessor concluded under a named policy at a particular time.
  • WalletWall’s own assessment is never supplied by the caller. It is generated from the focal claim’s computed support state, attributed to walletwall-rules under the claim’s policy, and a record whose WalletWall assessment differs from its focal claim is invalid.
  • External assessments (roles ISSUER, UPSTREAM_AUTHORITY, INDEPENDENT_REVIEWER, OTHER) are recorded as stated, with their evidence references. An ISSUER assessment must come from the registry’s authority for that deployment, and no external assessor may use an identity that reads as WalletWall or WallPrint.
  • Disagreement is preserved. Three assessors can disagree, and all three remain. No field anywhere holds an overall or consensus verdict. A record with no external assessment is valid: absence of assessment is not a failed assessment.
WallPrint’s own wording never uses verified, certified, safe, solvent, compliant, audited, approved, trusted or investment-grade: WalletWall’s verdict is a WWEP support state. An external assessor’s statement is recorded verbatim and attributed. Credential-shaped text is refused in every field of a record.

History: corrections, supersessions and withdrawals

Every lifecycle change is an event in an append-only history that is hash-chained per record: an event that is edited, reordered or dropped is detected as long as a later event follows it. Nothing signs or anchors the chain, so the newest event can be removed or rewritten without detection.
  • Correction creates a new record that names its predecessor, binds the predecessor’s digest and gives a reason. The predecessor gains a CORRECTED event; its content, digest and earlier events are untouched. Correction is not mutation.
  • Supersession works the same way and marks the predecessor SUPERSEDED. Supersession is not deletion.
  • Withdrawal adds a WITHDRAWN event with a reason. The record’s identity, bytes, digest and assessments stay addressable. Withdrawal is not deletion.
A record has at most one successor, so a history never branches or cycles.

Integrity: digest, receipt and replay

  • Digest. The record minus its digest field is serialized with RFC 8785 and hashed with SHA-256. The same evidence, policies, rules and assessments always give the same digest. UI state, local paths, process IDs, the current time and credentials have no place in a record, so they can never affect it.
  • Receipt. A receipt carries the record ID, canonicalization, digest algorithm, digest, bundle digest and versions. Verifying it answers one question: do these disclosed bytes match the committed record? It does not establish factual truth, solvency, safety, regulatory compliance, issuer endorsement or investment merit.
  • Replay. Replay re-derives a record from its stored evidence and the engine’s registry, policies and rules, and reports REPRODUCED, MISMATCH (with one reason per differing section) or UNREPLAYABLE (a required historical input is missing or not the committed one). Replay never evaluates historical evidence under present-day policy and never fills in missing evidence. UNREPLAYABLE is not INCORRECT.
A valid WallPrint digest demonstrates that a disclosed canonical record matches its committed record. It does not, by itself, demonstrate that every factual claim in that record is correct.

Portable reference

A portable reference locates one committed record. It answers which record (the record ID), which bytes (the committed digest) and which contract version, and optionally which section to open:
target is one of record, receipt, replay, history, assessments or provenance. The same reference also has a JSON envelope form. Both are deterministic, with exactly one admitted spelling, and a reference carries no record content. A reference is a locator, not authority. It carries no signature, names no signer, and becomes no more authoritative by being printed, shared or scanned as a QR code. A corrected, superseded or withdrawn record is as valid a target as the current one, and nothing redirects an old reference to a newer record.

The public resolver

The public resolver gives a reference a stable HTTPS form on WalletWall’s product domain. The HTTPS form is the same text with walletwall://wallprint/ replaced by https://walletwall.org/wallprint/:
A resolver locates a disclosure. It does not make that disclosure authoritative. Every resolved page carries this statement:
This page resolves a published WallPrint disclosure. Publication and resolution do not establish factual truth, safety, solvency, compliance, or investment merit.

How a page resolves

The resolver is static files and one page script: no server code, no database, no write endpoint and no signing. The page reads its own URL, fetches the record’s standing and one artifact from the same origin (without credentials, refusing redirects), and proves the bytes in your browser before it shows anything. A resolved page states that the URL’s digest covers the record’s canonical bytes and nothing else: the title, registry names and the receipt, replay and diff results carried beside the record are checked for consistency, not covered. A copy served from any origin other than walletwall.org says so. The page loads no analytics and no third-party resources, stores nothing in your browser, reads no clock and never redirects.

The store

Record IDs are intentionally public, and https://walletwall.org/wallprint/index.json lists every published record: enumeration of deliberately published disclosures is not a leak. Record files are revalidated within five minutes, so a newly published record is visible quickly and a not-yet-published one is never cached as missing for long.

Publication

Publication is deliberate, never ambient. Nothing becomes public because it was generated, and nothing you do with WalletWall MCP publishes anything.
  • WalletWall publishes a record from the engine repository, and it reaches walletwall.org through the product site’s ordinary release. There is no public write endpoint, no search endpoint and no assessor import.
  • A record is admitted only if it validates, its canonical bytes digest to its digest, every engine result carried with it agrees with it, and a privacy gate finds nothing credential-, path-, e-mail-, IP-address-, environment- or control-shaped, no URL, and no host name or wallet address outside the record’s own content.
  • Published bytes are immutable: the same disclosure always publishes to the same bytes, and different bytes under the same ID and digest are a conflict, never an overwrite. The record’s standing only extends: events append, a successor is set once, and a rewritten history is refused.
  • A corrected, superseded or withdrawn record stays published at its own URL. Its page shows its standing and links to the successor as a choice; nothing redirects.
On walletwall.org, the resolver page and its store are a pinned build of the open-source resolver in walletwall-copilot. The deployment’s CI rebuilds the pinned source commit and compares the bytes, and synthetic example lineages are test fixtures only: they are never published on the production domain.

What publication does not prove

A WallPrint, its receipt and its resolution are not:
  • a certification of truth, safety, solvency, regulatory compliance or audit status;
  • an endorsement by an issuer, a protocol or WalletWall;
  • investment advice or an opinion on investment merit;
  • a custody event, a transaction, or a transaction signature;
  • a signature or attestation of any kind: a digest match proves bytes, not who published them.
WallPrint records how WalletWall assessed the presented evidence, under named policies, at a stated time. That assessment can be wrong, and WallPrint exists to keep that visible.
Two further limits follow from having no signatures. The standing is the store’s own index: it is checked against its hash-chained ledger, but an authentic but stale ledger, or a well-formed extension appended by whoever controls the store, is printed as recorded. And the public page proves bytes and checks consistency; it does not re-run the engine’s record validation, which is the publisher’s act. Within the engine, WallPrint 0.1 keeps its history and evidence store in memory, and it cannot yet record an evaluation in which a CONFLICTING state propagates to a derived claim.

See WallPrints today

  • In GitHub Copilot: open the WalletWall canvas with a bundled synthetic lineage, for example { "wallprint": "corrected" } or { "wallprint": "conflicting-assessors" }, or with { "reference": "<portable reference>" }. See GitHub Copilot.
  • On the web: follow a published record’s HTTPS reference to walletwall.org/wallprint. Records appear there only after WalletWall publishes them, and the index lists them.

WallPrint among WalletWall’s other artifacts

WallPrint is one of three report-shaped artifacts WalletWall produces, and the only one that belongs to the MCP engine. The application’s Readiness Packet is a signed snapshot of one wallet’s vault readiness derived from WalletWall’s scheduled data; the Wallet Risk Report is an unsigned per-wallet composition of the application’s scorers. Neither is a WallPrint. A WallPrint carries no signature or attestation and certifies nothing; a Readiness Packet is signed, but its issuer signature proves only that WalletWall’s server derived it from its data at the stated time, not that the assessment is correct; the Wallet Risk Report is unsigned.

Evidence Model (WWEP)

The evaluation a WallPrint freezes, state by state.

Privacy & Security

What publication reveals, what the resolver stores, and what WalletWall receives.