This changelog records the milestones that shaped WalletWall’s public surface — documentation,
security hardening and application behavior — newest first, each entry naming its category. An
entry is dated by the merge of the change it describes or by the dated repository record it names.
The milestone entries added on 1 November 2026 were backfilled from merge records, release tags and
runbooks; none of them is dated by the day it was written. The one exception is the entry for the
refresh that added them, dated by the day it was prepared because it describes the change that
carries it. This is a record of what shipped where, not a product-release log or a statement of
production readiness.
BigQuery data-foundation migration completed.The planned five-slice migration closed after the wallet-activity slice moved from shadow serving to
WalletWall’s owned BigQuery snapshot and passed its post-cutover checks plus the first natural
scheduled refresh. Legacy provider paths remain where they are still intentionally used as fallbacks
or by separate surfaces. See Data Serving Architecture,
Data Foundation Refresh Model, and
BigQuery Serving & Canary.
Public documentation refreshed site-wide: product status, BigQuery serving, policy-gated execution (prepared 1 November 2026).The site gained a dated map of what you can use today, three pages on how
WalletWall-owned BigQuery snapshots are served,
refreshed and
promoted, and a Vault page on
policy-gated execution. Dune references were reclassified as
live, scheduled or legacy, the MCP & Integrations area was cross-linked from the rest of the site,
and this changelog was backfilled with the milestone entries below.
MCP & Integrations documentation area published.Eleven pages document the local, read-only WalletWall MCP server: its six tools and eleven resources,
the WWEP 0.1 evidence model, WallPrint 0.1, the GitHub Copilot and Claude Code plugins, the privacy
boundary and troubleshooting. Start at the MCP Overview.
WallPrint public resolver hosted at walletwall.org/wallprint.A published WallPrint record can now be resolved by its digest-identified reference on walletwall.org
through same-origin static reads with no analytics. The index starts empty: records appear only when
WalletWall deliberately publishes them, and a resolved record proves bytes, not truth. See
WallPrint.
Claude Code plugin distribution synced to the canonical engine, with its origin proven in CI.The public
walletwall-claude repository now carries a generated distribution pinned to the
canonical WalletWall MCP source, and its CI rebuilds the distribution from that pin to prove the two
match. Installation is described on Install & Connect.WalletWall MCP server and GitHub Copilot plugin published; listed in the official MCP Registry.The public
walletwall-copilot repository released the first GitHub Copilot plugin and MCPB
package, and the server was listed as io.github.Wallet-Wall/walletwall in the official MCP Registry
the same day; the 0.2.1 package followed on 26 October with eleven resources. The server is local,
read-only evidence infrastructure — it fetches, signs and publishes nothing. See
Install & Connect.BigQuery serving reads fail closed on incomplete results.A serving read whose single result page does not hold every row the query matched is now refused,
and the route answers from its unchanged legacy source instead of a silently truncated snapshot.
Page completeness joins the byte ceiling as a condition every owned read must satisfy; see
Data Serving Architecture.
Owned snapshot publication is atomic.The signature-exposure refresh now publishes each snapshot range with a single atomic statement, so a
reader sees either the previous complete snapshot or the new one and never a half-written range. The
guarantee is described in the Data Foundation Refresh Model.
Production serving from an owned BigQuery snapshot begins.The wallet holdings strip’s portfolio cohort was switched from its legacy scheduled source to the
owned stablecoin balance ledger after a shadow comparison and the read-only cutover gate, and kept
after a 48-hour canary. Responses label their source, and a single setting returns the surface to
its legacy path. See BigQuery Serving & Canary.
Slice 5: wallet signature exposure on an owned multi-chain signer snapshot.The per-wallet signature-exposure fact behind the Quantum Exposure Score gained an owned BigQuery
source — one row per signer seen on a covered EVM chain in the last 90 complete UTC days, read by
wallet through a parameterised, byte-bounded query — with the legacy Dune signature feed, which had
not refreshed since August 2026, as the nominal fallback. Each response says which source answered.
Slice 4: wallet portfolio on an owned stablecoin balance ledger.The wallet holdings strip gained an owned BigQuery source: a daily cohort of the top Ethereum wallets
by par stablecoin balance, built from an owned balance ledger, with the Dune portfolio query retained
as the fallback.
Slice 3: Stable Seer daily volume trend on an owned BigQuery table.The daily stablecoin volume series moved onto an owned, incrementally refreshed daily volume table,
read through a fixed, byte-bounded query, with the Dune query retained as the fallback.
Scheduled refresh workflow for the owned BigQuery tables.A scheduled workflow now refreshes the owned tables on fixed cadences instead of by hand. The refresh
model it runs — a single-runner lease, verified watermarks advanced one complete window at a time,
and byte budgets that refuse before overspending — is documented in the
Data Foundation Refresh Model.
Cutover gate: a read-only readiness check before any surface is promoted.Before a surface’s selector may move from shadow to its owned source, a read-only readiness gate must
pass. The gate’s current checks and the promotion method around it are described in
BigQuery Serving & Canary.
Slice 2: Stable Seer large flows on an owned BigQuery table.Stable Seer’s large stablecoin flows gained an owned BigQuery source refreshed every six hours,
designed to run in shadow beside the Dune query before promotion; shadow was switched on for the
route on 14 October.
BigQuery migration begins: slice 1, wallet activity.The wallet-activity series was the first surface given an owned BigQuery source behind a per-route
selector (
legacy, shadow, bigquery), with bounded serving reads and the legacy path kept
unchanged as the fallback. The migration’s design had been specified in August; see
Data Serving Architecture.Vault assurance docs reconciled to walletwall-vault v0.13.15.The Vault & Proof Readiness pages were brought in line with the public vault repository at v0.13.15:
the ZK/PQ status matrix, the policy-control authority design and the SP1 proof-exercise status, each
stated at the maturity the repository supports.
A code-owned hard byte ceiling on every BigQuery execution.Every BigQuery statement WalletWall sends must declare a maximum bytes billed, and a code-owned
absolute ceiling refuses — never clamps — any request above it. Serving reads sit far below that
ceiling.
walletwall-vault v0.13.0: policy-control authority.The public vault research prototype gained its policy-control authority design: changes that weaken
policy are delayed behind a timelock, changes that strengthen it apply immediately, and an emergency
path can freeze but never relax. The prototype remains testnet research, not production custody; see
Policy-Gated Execution.
Assurance v2: a frozen, bounded shadow prototype with its evidence.An eight-probe runtime-evidence prototype was frozen with its evidence package and documented as
exactly that — a bounded prototype, not a production assurance framework. See
Assurance v2 Runtime Evidence.
WallRoom: an interactive reasoning lab in the docs.A synthetic scenario room lets a reader change one condition in a controlled world and watch which
dependency moves and why the migration-readiness conclusion follows. It assesses no real vault. Open
WallRoom.
BigQuery-first data foundation specified.The migration from Dune-only analytics to WalletWall-owned BigQuery tables was specified before any
slice shipped; the October slices implemented it.
Knowledge Explorer proof of concept, now WallAtlas.An interactive map of the documentation’s concepts and their dependencies was added, and renamed
WallAtlas on 13 August. Explore it at WallAtlas.
Documentation migrated to docs.json with tabs; this changelog created.The site moved from mint.json to docs.json and gained tab navigation, the contextual AI menu, an
issue-reporting link and this changelog page.
Navigation icons completed; emoji removed from published pages.30 of the 36 pages in the sidebar had no icon, and 7 had no frontmatter at all —
rendering a path-derived label instead of their real title. Every navigation page now
declares a verified Font Awesome icon name. Along the way, a pre-existing broken icon
(
git-fork, a Lucide name absent from this deployment’s Font Awesome set) was fixed to
code-fork.The one emoji on a published page was replaced with plain text. Internal,
unpublished audit records that use check-mark and cross-mark emoji as
load-bearing table values were left untouched — that is data, not decoration.Added a static guard (test/docs-navigation-icons-and-emoji.test.mjs) so a future
page can never ship without a verified icon, and no published page can reintroduce
emoji.Published
.mdx pages brought into the static security scan.The repository’s static-analysis lint walked every .md file under docs/ for
injection sinks (dangerouslySetInnerHTML, eval, raw HTML injection) and committed
secrets — but silently skipped every .mdx file, even though Mintlify publishes
.mdx pages as live pages that can contain executable JSX.The scan now covers .mdx too, with a rule split that keeps it accurate: sink rules
scan only the executable body (fenced code samples and inline code spans are
display-only and never run), while credential rules always scan the full raw text —
a committed secret is a leak whether or not it happens to sit inside a code fence.This is a documentation-tooling change. No application code, provider, or scoring
behavior changed.Three interactive explainer components added to the docs.The Wallet Evidence Model, Quantum Intelligence, and PQ Evidence & Rehearsal pages
each gained a small, deterministic, client-only React component readers can use to
explore the underlying contract directly:
- Evidence State Explorer — shows why an unavailable reading is never rendered as
a confident
$0. - Quantum Exposure Calculator — mirrors the production
SCORE_WEIGHTSscoring curve, pinned by test against the canonical scoring modules so it cannot silently drift from what the application actually computes. - Proof Gate Matrix — demonstrates that PQ evidence, proof-artifact status, testnet rehearsal, and production readiness are independent gates, and that no combination of states can produce a “quantum-secure” claim or imply the platform is ready for production.
Rust/SP1 proof foundation for the vault-candidate threshold.A first SP1 program and trust-boundary definition for a
vault_candidate_threshold_v1 statement
entered the repository as research. It proves nothing on-chain and no circuit is deployed; see the
ZK Proof Artifact Roadmap.Post-quantum terminology aligned with the NIST standards; evidence ingestion hardened.Following an alignment audit against the NIST post-quantum standards, the Vault and Quantum
Intelligence pages and runtime metadata use the standards’ own names, and the ingestion path for
post-quantum verifier evidence was hardened.
Portfolio Assessment: a controlled-pilot workspace.An operator-invited workspace batch-assesses 10 to 100 wallets at once. Access stays controlled, and
the cost model is documented in the
Portfolio Assessment Cost Model.
Wallet Risk Report v1: schema, composition layer and read-only API.A per-wallet report composes existing scorers into one read-only object with client-side
content-hash integrity and no signing; the report page and its entry points shipped the same day.
See the Wallet Risk Report Model.
Internal docs unpublished; scoring and API claims corrected.A documentation audit moved internal records out of the published site, corrected scoring and API
claims, and added the public and private repositories page.
Dune reads become scheduled and cached: a daily warmer with a 24-hour cache.A scheduled warmer copies the Dune results WalletWall needs into a cache once a day (a lifetime since
lengthened to 25 hours), and routes read that cache; result reads outside the warmer had been made
fail-closed behind operator flags two days earlier. See Dune Queries.
Wallet Evidence Model v1: source-aware claims where unknown is never zero.Every wallet fact now carries its source, state and freshness, and an unavailable reading is rendered
as unknown rather than as a confident zero. The model was extended to movements, activity and
protocol affinity the same day, with public docs and a Mermaid diagram system. See the
Wallet Evidence Model.
Exposure Report route with a print one-pager.A route renders a wallet’s exposure report, including a printable one-page summary, from the same
scheduled data as the rest of the application. See Exposure Report.
Readiness Packet: canonical serialization, content hash and issuer signing.A wallet’s readiness assessment can be issued as a dated, signed, read-only packet that travels as a
URL fragment. Issuance is server-side and fail-closed without a signing key. See
Readiness Packet.
Proof-readiness stack documented, and where SP1 fits.The layers between a readiness verdict and a verifiable proof were written down, with the SP1
candidate decision documented the same day. See the
Proof Readiness Stack.
Read-only PQ verifier evidence on the Stablecoin Vault page.The Vault page surfaces the public vault repository’s post-quantum verifier evidence read-only, with
the public docs aligned the same day. The vault repository tagged its own ZK/PQ status matrix, which
bounds what it claims, as v0.8.1 that day. See
PQ Evidence & Rehearsal.
Stablecoin Vault readiness engine.A readiness engine scores a wallet’s stablecoin vault readiness into tiers from scheduled data; the
readiness workflow landed the same day, and the Holder Wall handoff and the Stable Seer / Stablecoin
Vault taxonomy followed on 19 June. See Stablecoin Vault.
The /vault route: a post-quantum migration research page.WalletWall’s Vault surface began as a research page on post-quantum migration. Everything built on
it since remains testnet research, not production custody.
Coinstellation entry page and homepage card.The 3D wallet-relationship view, named Coinstellation since mid-May, gained its own entry page and a
homepage card. See Coinstellation.
Quantum Intelligence page and the wallet holdings strip.The Quantum Intelligence page presents the Quantum Exposure Score, whose API had landed on 29 May,
and wallet pages gained a holdings strip. See Quantum Intelligence.
Market Radar becomes Stable Seer.The stablecoin market surface was renamed Stable Seer throughout the codebase, following the
interface rename of 28 May. See Stable Seer.
Dune scheduled 12-week activity feed.Whale Watcher’s 12-week heatmap began reading a scheduled Dune query, establishing the rule that Dune
data is scheduled and cached, never live. See Dune Queries.
Whale Watcher begins as an analytics tab.The first Whale Watcher surface was an analytics tab over live wallet reads. See
Whale Watcher.

