Skip to main content
RESEARCH · NOT PRODUCTION PROVINGThis roadmap is research and testnet only. Nothing here describes a live or imminent production capability. There is no production custody, no mainnet deposits, no yield, and no quantum-proof guarantee. The SP1 smoke lane is not production proving, and no on-chain verification exists unless and until it is actually implemented and independently reviewed. See what you can use today for every surface side by side.
A staged plan for evolving the post-quantum (PQ) verifier and ZK/SP1 proof-artifact work, based on the public reference repo Wallet-Wall/walletwall-vault as of the walletwall-vault@0.8.5 baseline (SHA 6462c10, June 2026). The public repo’s main has since advanced past this tag (v0.13.31 on 22 October 2026); the version references in the current-state table are that baseline, and the status update below records what has changed since. This plan exists to keep the next steps sober and sequenced — not to assert readiness. The WalletWall app consumes only local, read-only evidence shapes from this work. It does not run proving, does not verify on-chain, and does not import prover/verifier code at runtime. See PQ Evidence, Testnet Rehearsal & ZK/SP1 Status and Vault Boundaries & Disclosures. The candidate SP1 program (readiness_score_v1) is a dev-only research scaffold. To build and run it locally in a controlled environment — execute-mode only, not production verification — follow the SP1 dev environment runbook. See also the Proof-Readiness Architecture and Proof Claim Schema for how candidate SP1 evidence attaches to the Readiness Packet proofExtension.

Current state (as of walletwall-vault@0.8.5, baseline walletwall-vault@0.8.1)


Status update, 22 October 2026

The repository’s own capability matrix is the single source of truth for what exists, and it is written so that this site cannot overclaim. Recorded from that matrix at tag v0.13.31: The app has not changed what it renders in response to any of these: it shows read-only evidence shapes, runs no prover or verifier, and fetches nothing from the repository at runtime.

Timeline

“Today” is what ships and runs live. “Research spike” and “Future research” are staged, non-production work — they do not imply a scheduled release, live custody, or a production ZK/PQ guarantee.

Stages

Each stage is independent and gated. None implies the next is funded, scheduled, or safe to ship.
The app shows hash-only PQ verifier evidence and testnet rehearsal metadata as separate gates. This is the only live app capability. No proving, no on-chain verification, no custody.
Broader known-answer / ACVP test-vector coverage for the ML-DSA-65 verifier was added in public PR #64 (@0.8.2). Increases confidence in the off-chain verifier; changes nothing about on-chain or production status. No app change required.
A reproducible, independently re-verifiable proof-artifact example (inputs, expected hashes, and a reproduce command) was published in public PR #65 (@0.8.3). This is a research artifact, not a production proof and not a custody signal. The app may display a reference link and expected hash (read-only) — no prover, verifier import, or raw proof blob.
Wire end-to-end SP1 proving behind an explicit research gate, clearly labelled as not production proving. Output remains a research artifact; the app continues to display read-only evidence only. At the @0.8.5 baseline this stage was not built. By v0.13.31 the repository carries an env-gated prove path and a verifier-binding registry, with no proof produced in CI, nothing deployed or registered, and no WalletWall proof admitted as evidence; it remains research, not production proving.
A hosted verifier spike was completed in public PR #66 (@0.8.4): feasibility/dev service that accepts a test vector and returns a hash-only result. The app does not call this service at runtime. This is docs/spike only — no custody, no mainnet, no user funds.
An on-chain verifier feasibility study (gas, calldata, precompile assumptions, threat model) was authored in public PR #67 (@0.8.5). This is a document, not an implementation. On-chain ML-DSA verification does not exist until separately built and audited.

For Wallet-Wall/walletwall-vault, sequenced and sober. Stages 1, 2, 4, and 5 are done in the public repo; stage 3 remains unbuilt:
  1. More ACVP vectors — broaden known-answer coverage for ML-DSA-65. ✓ done (public #64, @0.8.2)
  2. Reproducible proof-artifact example — publish inputs + expected hashes + a reproduce command. ✓ done (public #65, @0.8.3)
  3. Hosted verifier demo spike — feasibility spike only; testnet/dev, no custody. ✓ done (public #66, @0.8.4)
  4. On-chain verifier feasibility doc — a study (gas/calldata/threat model), not an implementation. ✓ done (public #67, @0.8.5)
  5. Stage 3 — Gated SP1 proving / e2e — wire end-to-end proving behind an explicit research gate, clearly labelled as not production proving. An env-gated prove path now exists in the repository (v0.13.31); it runs no proof in CI and has no production binding, and admitting any proof as evidence requires its own design review.
  6. Audit / independent review — before any stage moves toward production.
None of the above introduces custody, signing, mainnet deposits, yield, or a production protection claim.

Explicit non-goals

This roadmap does not plan, promise, or imply:
  • production custody of funds,
  • mainnet deposits or withdrawals,
  • yield, interest, or returns,
  • a quantum-proof or quantum-secure guarantee,
  • on-chain ML-DSA verification (none exists today),
  • production SP1 proving (the smoke lane is research only),
  • any runtime dependency of the app on the public vault repo.

PQ Evidence, Rehearsal & ZK/SP1 Status

How the app surfaces these as separate, read-only gates today.

Vault Boundaries & Disclosures

What no roadmap stage changes: custody stays with the owner, deployments stay on testnet, and no quantum-resistance claim is made.

walletwall-vault (public repo)

The public reference repo for contracts, the verifier, and proof artifacts (pinned baseline @0.8.5; repository at v0.13.31 on 22 October 2026).

Proof-Readiness Architecture

Where a proof would attach to the Readiness Packet, and why WalletWall is proof-ready, not SP1-dependent.