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 tagv0.13.31:
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.Stage 0 — Read-only evidence (live)
Stage 0 — Read-only evidence (live)
Stage 1 — Broaden ACVP vector coverage ✓ done in public repo
Stage 1 — Broaden ACVP vector coverage ✓ done in public repo
@0.8.2). Increases confidence in the off-chain verifier; changes nothing about on-chain or production status. No app change required.Stage 2 — Reproducible proof-artifact example ✓ done in public repo
Stage 2 — Reproducible proof-artifact example ✓ done in public repo
@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.Stage 3 — Gated SP1 proving / e2e (research; env-gated path exists, no proof in CI)
Stage 3 — Gated SP1 proving / e2e (research; env-gated path exists, no proof in CI)
@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.Stage 4 — Hosted verifier demo spike ✓ done in public repo (feasibility only)
Stage 4 — Hosted verifier demo spike ✓ done in public repo (feasibility only)
@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.Stage 5 — On-chain verifier feasibility ✓ done in public repo (study, not build)
Stage 5 — On-chain verifier feasibility ✓ done in public repo (study, not build)
@0.8.5). This is a document, not an implementation. On-chain ML-DSA verification does not exist until separately built and audited.Recommended next PR sequence (public vault repo)
ForWallet-Wall/walletwall-vault, sequenced and sober. Stages 1, 2, 4, and 5 are done in the public repo; stage 3 remains unbuilt:
- More ACVP vectors — broaden known-answer coverage for ML-DSA-65. ✓ done (public #64,
@0.8.2) - Reproducible proof-artifact example — publish inputs + expected hashes + a reproduce command. ✓ done (public #65,
@0.8.3) - Hosted verifier demo spike — feasibility spike only; testnet/dev, no custody. ✓ done (public #66,
@0.8.4) - On-chain verifier feasibility doc — a study (gas/calldata/threat model), not an implementation. ✓ done (public #67,
@0.8.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.
- Audit / independent review — before any stage moves toward production.
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.

