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 and testnet rehearsal are separate gates — neither implies the other.
This page documents the post-quantum (PQ) verifier-evidence, 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@0.8.1. 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.

​
Two separate gates

WalletWall keeps two independent questions separate and never merges them into a single “ready / protected / secured” claim:
GateQuestion it answersWhat a positive state means
PQ EvidenceWas read-only verifier evidence observed?A hash-only verifier result is available to display. It is not custody, mainnet support, a ZK proof, or on-chain ML-DSA verification.
Testnet RehearsalIs a testnet simulator / operator path documented and metadata-safe?Documented Sepolia/testnet simulator metadata, mock assets only. It is not PQ evidence and not production protection.
The flagship page may show both together, but each is labelled as its own gate, and either may be unavailable without affecting the other.

​
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.
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.

​
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:
StateMeaning
not_configuredNo rehearsal metadata configured — read-only readiness only
rehearsal_metadata_missingMetadata present but required fields absent
unsupported_schemaMetadata schema version not understood
unavailableMalformed, non-testnet/forbidden chain, or a disabled safety gate — never shown as ready
rehearsal_readyDocumented Sepolia/testnet metadata, mock token, all safety gates true
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.
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

UseDo not use
Read-only PQ verifier evidenceQuantum-proof / quantum-secure
Hash-only result shapeFunds are protected / secured
Testnet rehearsal metadataMainnet-ready / production-ready
Separate PQ and rehearsal gatesA single “vault is ready” claim
SP1 smoke is research statusSP1 proves your wallet
Not production quantum protectionOn-chain ML-DSA verification (none exists)

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.1

The public reference repo that owns contracts, the verifier, and deployment records.