Skip to main content

​
PQ Evidence, Testnet Rehearsal & ZK/SP1 Status

Everything on this page is read-only research and testnet status. It is not custody, not a wallet transaction, not signing, not a mainnet deposit, not yield, and not production quantum protection. PQ evidence, proof artifact status, and testnet rehearsal are separate gates — none implies the others.
This page documents the post-quantum (PQ) verifier-evidence, proof artifact status, testnet-rehearsal, and ZK/SP1 status surfaces that the Stablecoin Vault renders. It aligns the app’s public-facing language with the reference repo Wallet-Wall/walletwall-vault. The evidence surfaces described here are pinned to the walletwall-vault@0.8.5 baseline (SHA 6462c10; initial baseline @0.8.1); the public repo’s main has since advanced past this tag, so treat the specific version references below as an as-of snapshot rather than the repo’s latest release. The app consumes only local, read-only shapes derived from that repo. It does not fetch the repo at runtime and does not import its contracts, ABIs, verifier code, prover code, or deployment artifacts. See Vault Boundaries & Disclosures for the full custody / testnet / quantum-resistance statement.

​
Three separate gates

WalletWall keeps three independent questions separate and never collapses them into a single “ready / protected / secured” claim: The flagship page may show all three together, but each is labelled as its own gate, and any may be unavailable without affecting the others.

​
Try it — proof gate matrix

Toggle the gates below to see exactly which claims each state does and does not support. The point of the exercise is what cannot happen: no combination moves a red-line claim into the supported column, and requesting SP1 proving, on-chain ML-DSA verification, a mainnet chain, or a non-mock token fails closed rather than unlocking anything. This is a claim-boundary explainer, not a verifier or a deployment-status checker. It runs no cryptography, calls no prover or contract, and fetches nothing.

​
PQ Evidence (read-only, hash-only)

The Stablecoin Vault renders a read-only Post-Quantum Verifier Evidence card. It displays the deterministic, hash-only result shape produced by the open ML-DSA-65 verifier in the reference repo (schema id walletwall.pq-verifier.v1).
  • Hash-only by design. The card shows keccak256 hashes of the message, public key, and signature — never raw key, signature, message, or secret material. The adapter fails closed: any payload carrying raw material renders the placeholder instead.
  • Display only. No verification runs in the app. A verified: true result is evidence that the open verifier accepted a test vector — it is not a claim of custody, mainnet support, a ZK proof, or on-chain verification.
  • Sample vs live. The flagship page shows a clearly-marked sample result; live PQ evidence is not observed there.
  • Reference: verifier boundary guards and evidence artifact/schema correspond to public repo PRs #60 and #61 (baseline walletwall-vault@0.8.1).
The PQ evidence card never reaches a signer, provider, ABI, or network call. It is a self-contained, read-only presentation of an evidence shape.

​
Proof Artifact Status (read-only)

The Stablecoin Vault renders a read-only Proof Artifact Status card. It displays metadata derived from the reproducible proof-artifact example published in public repo PR #65 (walletwall-vault@0.8.5).
  • Static, app-local fixture. The card shows a demo fixture based on the example shape from the public repo. It is not fetched at runtime — no network request is made.
  • Generated outside the app. The proof artifact example was produced by the public vault repo reference tooling. This app does not run SP1, does not invoke a prover, and does not call any hosted verifier service.
  • Proof block is gated. The proofBlockStatus is gated — SP1 proving is not active in this app. No proof has been generated by or for this surface.
  • Hash display only. The card shows truncated keccak256 hashes for context only (evidence hash, output hash). No raw proving key, private key, witness, or mnemonic is ever displayed. The adapter fails closed: any artifact carrying forbidden raw-material fields renders the placeholder.
  • Schema walletwall.proof-artifact.v1. Only this schema version is understood; others render as unsupported.
  • Not on-chain verification. Displaying a proof artifact status is not on-chain ML-DSA verification and is not a production protection guarantee.
  • Reference: reproducible proof-artifact example from public repo PR #65 (walletwall-vault@0.8.5).
The proof artifact card never reaches a signer, prover, hosted-verifier endpoint, or contract. It is a self-contained, read-only presentation of a static example artifact.

​
Testnet Rehearsal status

The rehearsal status model answers whether a Sepolia/testnet simulator and operator path are documented and the metadata is safe to surface. It mirrors the app-consumable status example published in public repo PR #58 as a static, app-local fixture — nothing is fetched at runtime. The model is deterministic and fails closed. It surfaces one of: A mainnet chain ID, a non-mock token mode, or any disabled safety gate forces unavailable. Mainnet chain IDs can never resolve to a ready state.

​
ZK / SP1 status — disclosure only

The reference repo includes an SP1 smoke lane and a ZK/PQ status matrix (public repo PRs #62 and #63). In the app these are research / disclosure status only:
  • The SP1 smoke lane is a research signal, not production proving.
  • No on-chain verification runs in the app.
  • There is no ZK proof behind any user-facing readiness state, and none is implied.
  • This is not production quantum protection.
A reproducible proof-artifact example was published in public PR #65 (walletwall-vault@0.8.5). The app displays this as read-only Proof Artifact Status (see above). The artifact is not a live SP1 proof and not on-chain verification. See the ZK proof-artifact roadmap for the staged, non-production next steps.

​
Safety boundaries

This surface inherits the full vault boundary statement: no custody, no wallet transaction, no signing, no contract writes, no mainnet deposits, no yield, and not production quantum protection. In full, no WalletWall surface here involves:
  • custody of funds or private-key handling,
  • wallet transactions, signing, or contract writes,
  • mainnet deposits or withdrawals,
  • yield, interest, or returns,
  • production quantum protection.
The complete statement — custody, financial, testnet, quantum-resistance, mainnet gates, and the app/vault repo boundary — lives in Vault Boundaries & Disclosures.

​
Approved framing

Vault Boundaries & Disclosures

Full custody, testnet, and quantum-resistance boundary statement.

Stablecoin Vault & Vault Simulator

The flagship readiness journey and the Sepolia rehearsal detail route.

ZK proof-artifact roadmap

Staged, non-production next steps for the ZK/SP1 proof-artifact lane.

walletwall-vault@0.8.5

The public reference repo that owns contracts, the verifier, and deployment records (current: @0.8.5).