Skip to main content
WalletWall ships two related but distinct vault surfaces. They do not have the same status, and each leads with its own classification.
Keep availability, interaction mode, and assurance maturity separate. The hosted Stablecoin Vault journey is available today as a read-only research interface. The connected Vault Simulator dashboard is an unaudited Sepolia testnet prototype using mock assets. Neither surface is production custody or production-grade post-quantum verification, and neither should be described as protecting real funds. See Vault Boundaries & Disclosures and what you can use today.
Each surface leads with its own classification. The hosted Stablecoin Vault presents five recommendation states: Monitor, Prepare, Migrate, Vault Candidate, or Unsupported. The Vault Simulator scanner presents four workflow outcomes: Monitor, Prepare, Testnet Rehearsal, or Not Enough Data. A scan result also shows a five-state recommendation lower on the page, and the two can differ. Migration Readiness explains how these relate to the shared risk tiers.

What it does

The Stablecoin Vault is the readiness destination the WalletWall intelligence surfaces point to. It is reachable at /stablecoin-vault and at vault.walletwall.org. You enter a wallet and the facts you have, or arrive with them prefilled from another surface, and the page evaluates them in your browser into one of five recommendation states. The hosted journey is read-only; it does not connect a wallet or request a signature. The page labels itself a prototype, research and testnet only, and shows a Sepolia testnet badge. The Vault Simulator is a research prototype that demonstrates a hybrid classical + post-quantum authorization model for Ethereum wallet migration: a Sepolia testnet rehearsal, with no mainnet and no production custody. It is a technical detail route, not a standalone flagship. Its read-only scanner reads a wallet’s facts and presents one of four workflow outcomes of its own.

What you can learn

  • Which recommendation fits the facts on the page — with a score when there is enough evidence, the risk drivers behind it, and next actions. A recommendation is never an instruction to move funds.
  • Which evidence exists, gate by gate — separate read-only gates for rehearsal metadata, PQ verifier evidence, proof artifacts, candidate SP1 evidence, and the proof evidence chain.
  • How the Vault Simulator scanner reads a wallet — a workflow outcome, plus a recovery readiness score with its bands, findings, and recommendations.
  • What a rehearsal would involve — a conceptual hybrid authorization walkthrough for the scanned wallet, with nothing signed and nothing submitted.

How to read it

Stablecoin Vault recommendations

The hosted page maps what it evaluates to one of five recommendation states. The readiness assessment is read-only: it moves nothing, and it asks for no wallet connection or signature. The strongest signal wins: a score selects its band, and a migration tier on the form can raise the state above that band, or set a state with no score at all. With no usable evidence, the state is Unsupported and no score is shown. The page’s Vault Readiness Workflow rail shows these five states and labels the Vault Candidate step Prove. Four of these states carry a shared Migration Readiness risk tier. Unsupported carries none, and Review is not a state on this page. The same vocabulary appears in the Vault Readiness block of the Migration Path panel on Quantum Intelligence, the wallet activity view, and the Vault Simulator scan result. There it is built from the scan instead of the form.

Readiness evidence gates

Alongside the recommendation, the page shows five read-only evidence gates. Each is evaluated independently: none implies another, none feeds the recommendation, and none is a protection guarantee.

Testnet rehearsal metadata

Whether documented Sepolia/testnet simulator metadata is present and safe to surface — mock assets only. This is a metadata gate, not the scanner outcome called Testnet Rehearsal.

PQ verifier evidence

A hash-only, read-only record that the open ML-DSA-65 verifier accepted a test vector. Not custody, not on-chain verification. Its ZK / SP1 note is research disclosure only: no ZK proof runs behind any readiness state, and this is not production quantum protection.

Proof artifact status

Read-only metadata for a reproducible proof-artifact example generated outside the app. SP1 proving remains gated in this app.

Candidate SP1 evidence

A static execute-mode fixture, display only. No proof is generated here, and it is not production verification.

Proof evidence chain

A read-only step chain of the public vault evidence, in a panel headed Testnet Rehearsal Status. That heading is a status label, not a scanner outcome. Live proof bytes and mainnet launch remain gated.
PQ evidence, proof artifact status, and testnet rehearsal are separate gates — a positive state in one never implies another. The matrix below makes that boundary interactive; the full explanation lives in PQ Evidence, Testnet Rehearsal & ZK/SP1 Status.

How a wallet reaches the journey

Values arrive as a prefill you can review and adjust before evaluating.

Quantum Intelligence → Stablecoin Vault

When a Quantum Intelligence scan has observed at least one vault-relevant signal, it offers a link that carries the wallet, with the balance and dormancy from its scheduled facts when they matched, into the page.

Wallet Profile → Stablecoin Vault

When vault-relevant signals are present, the panel’s vault readiness link carries the wallet address into the page.
Holder Wall and Stable Seer were retired as standalone pages and no longer link here. No Stable Seer signal feeds the hosted recommendation today.

Reaching the Vault Simulator

The hosted page links to the Vault Simulator at /vault from the last of its Migration Path steps and from its vault rehearsal workspace section, and the homepage links to it too. These links are not gated on a recommendation: they appear whatever state the page shows. Opening the simulator does not mean a wallet qualifies for anything.

Vault Simulator scanner

The entry page explains the three concepts (Quantum Exposure, Migration Readiness, WalletWall Vault), shows the research disclosure, and presents a read-only scan form. Users can enter any Ethereum address or ENS name. Scanning does not require a wallet connection, signature, or transaction. The entry page also offers an optional Connect wallet button. Connecting is not part of the scan. On Ethereum mainnet, a connected account sees a read-only assessment built only from reads through the connected wallet’s own RPC provider: the account type (an EIP-7702 delegated account is named as such, and unfamiliar code is reported as unknown rather than as a contract), the signature exposure observed on that chain (a nonce of zero does not show the key has never signed), the native balance, and balances of the approved stablecoin registry shown at assumed par value, not a market price. A read that fails is shown as unknown, never as zero, and no signature, transaction, or write is requested. On any other network, unless the build enables vault actions, which are off by default, a connected user stops at a notice, such as the disabled-actions notice or a wrong-network prompt, and reaches no vault action. Searches may send public wallet or token addresses to third-party data providers to retrieve on-chain analytics. A connected account is assessed from your wallet provider’s RPC and is not sent to WalletWall. After scanning, the result phase renders, top to bottom:
1

Score ring

Displays the vault readiness band (unknown, weak, moderate, strong, resilient) and the scanned address.
2

Research disclosure

Always visible; states the prototype is read-only in the scanner and does not store keys.
3

Vault Readiness panel

One of the four scanner outcomes below, with its next step and persistent testnet disclosures.
4

Simulator deployment status

Read-only Sepolia deployment metadata for the simulator, or a note that none has been recorded. It does not indicate transaction readiness.
5

Wallet security and Proof-of-Readiness panels

Shown when a security profile is available: the wallet security panel, the rewards preview, and a campaign preview listing which readiness campaigns the scanned wallet is eligible for, with an evidence hash derived deterministically from its security profile signals.
6

Quantum Vault Readiness Card

Recovery readiness breakdown, findings, recommendations, controls, and the Migration Path panel. That panel includes a Vault Readiness block with a Stablecoin Vault recommendation for this wallet, and a read-only packet preview.
7

Simulate: Authorization flow panel

Collapsed by default; see below.
8

Research repository link

Links to the WalletWall Vault GitHub repo.

Scanner outcomes

The scanner’s Vault Readiness panel maps a Migration Readiness result to one of four outcomes. The first matching rule wins: The first rule covers many ordinary wallets. A scan supplies no asset count, which the feasibility level needs for its middle rating, so the level stays unknown unless the wallet is programmable, holds $1,000,000 or more, or is a confirmed externally owned account holding $100,000 or more. A wallet whose path or urgency matches a later rule can still read Not Enough Data. Both links jump to the simulator’s deployment status panel on the same page. They are not an entry into the simulator, because the reader is already in it. These outcomes are a presentation layer over the Migration Readiness engine (monitor / plan / prioritize urgency and the vault-prototype recommended path), not new math. They are not the shared Migration Readiness risk tiers (Monitor, Review, Prepare, Migrate, Vault Candidate), and they are not the Stablecoin Vault’s recommendations. A scan result also shows a second classification. The Migration Path panel’s Vault Readiness block shows a Stablecoin Vault recommendation built from the same Migration Readiness result and the card’s exposure level. The block and this panel share a label but apply different rules, so they can disagree: an externally owned account holding $150,000 with an exposed signature can read Prepare here and Migrate in the block. This diagram visualizes the table above; it adds no new inputs. It describes the scan result at /vault only, not the hosted Stablecoin Vault page.

Recovery Readiness Score

When no wallet signals are available the score is null and status is insufficient_data. A heuristic-only baseline is never shown as wallet-specific intelligence.
The score is computed by the recovery-readiness scorer. It starts from a base of 62 and applies deltas for:

Simulate: Authorization flow panel

The Simulate: Authorization flow panel is a collapsible research illustration — not an interactive signing flow. It renders in the result phase below the Quantum Vault Readiness Card, collapsed by default. It shows a static, deterministic narrative of what a hybrid ECDSA + ML-DSA authorization step would look like for this wallet. Steps are neutral-gray (not success/fail colored) and labeled as a conceptual illustration. It represents no real signature request, no key access, and no on-chain submission.

Sepolia stablecoin rehearsal

When a build enables vault actions and the connected wallet is on Ethereum Sepolia, /vault offers a rehearsal against the public StablecoinVaultSimulator stack: the MockUSDC test token (mUSDC, six decimals, no monetary value), the simulator, and MockMLDSAVerifier. Their addresses, deployment commit, source tag and runtime code hashes are pinned in the app from the public repository’s deployment record and reproducibility evidence. The ETH WalletWallVault dashboard described above is a different contract and is unchanged. The journey is Connect → Mint mock USDC → Approve → Deposit → View balance → Withdraw → Verify receipt, as five separate transactions, each approved in the wallet:
1

Deployment identity

On every connection the app reads the runtime code at the three pinned addresses and the simulator’s wiring through the wallet provider and compares them with the public record. Controls are enabled only when the identity is verified; a mismatch disables every write and says so.
2

Mint and approve

The faucet mints 1,000 mUSDC to the connected account. The approval is for the exact amount entered, never an unlimited allowance.
3

Create an EcdsaOnly vault record and deposit

The vault record is created in EcdsaOnly mode: the connected wallet key authorizes withdrawals and no post-quantum key is registered. A deposit moves the approved amount into the vault’s recorded balance.
4

Withdraw under EIP-712 and verify

The wallet signs a Withdrawal typed message under the WalletWallStablecoinVault domain, the app preflights the call, submits it and reports only a status 1 receipt as confirmed, with a link to the transaction on Sepolia Etherscan.
The surface labels itself a Sepolia testnet rehearsal and shows the wallet mUSDC balance, the vault’s recorded balance and the current allowance with distinct unavailable, loading, failed and confirmed states. A read that fails is shown as unknown, never as zero. The simulator’s post-quantum gate is a mock that performs structural length checks only: the rehearsal registers no post-quantum key, synthesizes no mock material, refuses to deposit into or withdraw from an existing Hybrid or PqOnly vault record (a deposit there could never be withdrawn through this surface), and is not post-quantum protection. Reads and writes go through the wallet provider’s RPC, which can observe the address and these queries; WalletWall receives nothing and stores nothing. Mainnet stays blocked by the network gate, by the repo-wide testnet assertion at every control, and by a live chain check before each write. The build flag that enables any connected action (VITE_ENABLE_VAULT_ACTIONS, off by default and absent from production builds) is an operator setting documented in the repository, not a user control; the public boundary is stated in Vault Boundaries & Disclosures.

Data freshness and provenance

The hosted assessment scores the values on the page, so it is only as current as they are. Values prefilled from Quantum Intelligence come from that surface’s data, but no timestamp travels with them and the page shows none. Values you type are self-reported. It adds no separate data source. The Vault Simulator scanner reads the same scheduled and chain-derived facts as Quantum Intelligence. Data Serving Architecture explains how each class is served. The evidence gates are read-only and generated outside the app: WalletWall does not fetch the reference repo at runtime, run SP1, or call any verifier service. See PQ Evidence, Testnet Rehearsal & ZK/SP1 Status for the full statement.

Important boundaries

The Vault Simulator is a research prototype. The readiness scanner is read-only. The connected dashboard is testnet-only and can request EIP-712 signatures and submit testnet transactions. The current verifier is not production-grade post-quantum verification, and no live native PQ precompile support is claimed.
  • A classification is guidance. A recommendation or scanner outcome is never an instruction to move funds, and neither is a security guarantee.
  • No production custody. WalletWall does not store private keys, does not ask for seed phrases, and does not implement recovery flows in this UI. The canonical boundary and guarantees live in the Key Management & Recovery Model — recovery flows are not implemented yet.
  • Testnet only for anything connected. The connected Vault dashboard is separate from the readiness scanner. Ethereum Sepolia is the validated active deployment, and Ethereum Mainnet and Base Mainnet writes remain blocked.
  • The stablecoin rehearsal’s verifier is a mock. MockMLDSAVerifier checks byte lengths only; the rehearsal uses EcdsaOnly vault records and never presents the mock gate as post-quantum protection. Its token is mUSDC, never real USDC.
  • The active testnet deployment is not reproducible from public HEAD yet. See Deployment status for the figures and the remediation path. The Stablecoin Vault page surfaces this state in a read-only Vault Trust Status panel.
  • A rehearsal is not protection. Use careful labels such as “research simulation”, “conceptual flow”, “illustration”, “not a real authorization”, “no keys accessed”, “nothing submitted on-chain”, and “monitor only”. Avoid absolute safety, recovery, or asset-control claims.

Technical reference

Deployment status

Ethereum Sepolia is the validated active deployment:
At the application’s pinned check, the reported source commit is absent from public Vault history, and current public HEAD recompiles to 22,138 runtime bytes, not the active deployment runtime of 20,508 bytes. This deployment is not reproducible from public HEAD yet — in the public repo its reproducibility is remediation-gated and recorded in a machine-checkable manifest (deployments/reproducibility/walletwall-vault-sepolia.json, enforced by npm run validate:reproducibility). The committed remediation path is to redeploy from public HEAD or publish the exact source tag and artifact manifest. Do not claim that current public HEAD reproduces the active Sepolia deployment. The public manifest is the source of truth for the current figures: the public-HEAD byte count moves as the public code changes, and the manifest records when it was last independently re-checked.
The prior Sepolia deployment identified as 0x8c5B…CF24 is deprecated because it has a stale runtime and uses the incompatible legacy 32-byte PQ-key vault format. Do not use it for new vaults or reference it as active. The public Wallet-Wall/walletwall-vault repository owns contracts, security assumptions, verifier design, tests, and deployment records. The private app consumes pinned ABI, custom errors, events, EIP-712 schema, and deployment configuration only. No full public-repository mirror should be added. The read-only Vault Trust Status panel reports the public reference path as remediation-gated, states that the active Sepolia deployment is not reproducible from public HEAD yet, lists the two remediation paths, and links to the public reproducibility manifest at deployments/reproducibility/walletwall-vault-sepolia.json. The panel is presentational only — it performs no runtime fetch, deploy, or transaction, implies no custody, deposits, wallet connection, or signing, and makes no mainnet-readiness claim.

Implementation boundary

The Vault Simulator’s UI is a compatibility/prototype surface. The migration path panel is driven by the shared wallet-security profile when available, with a migration-only fallback. The shared wallet-security orchestration layer supplies the security state, vault eligibility, and recovery readiness rendered in the Wallet Security and Migration Path panels. A deep-link param ?vw=<address> triggers the scan automatically on load. The ← New scan button resets to entry without navigating away.

Authorization flow panel steps

This renders the table above as a sequence, nothing more. Every step is illustration only — the panel is collapsed by default and colored neutral-gray rather than success/fail; it represents no real signature request, no key access, and no on-chain submission.

Cryptographic research context

The vault prototype models hybrid authorization using:
  • ML-DSA (FIPS 204) — formerly CRYSTALS-Dilithium; the primary post-quantum signature scheme.
  • SLH-DSA (FIPS 205) — formerly SPHINCS+; referenced as related signature research.
  • ECDSA / secp256k1 — the current Ethereum signature scheme, retained in the hybrid flow.
The hybrid proof binds both an ECDSA signature and an ML-DSA signature to the migration transaction. The on-chain verifier is an architectural placeholder — it does not perform production-grade cryptographic verification. Connected-dashboard withdrawals use EIP-712 typed-data signing. Before transaction submission, the app runs a staticCall preflight and surfaces decoded custom errors when revert data matches the pinned ABI. Mock PQ key and signature material is prototype/testnet-only. A valid signature is the first of two gates in the prototype’s contracts. The second is policy: spend limits, recipient restrictions, timelocked large withdrawals and composable policy modules decide what an authorized path may do. Policy-Gated Execution explains why that second question matters and what the prototype implements.

Where each classification is defined

  • Stablecoin Vault recommendations: RECOMMENDATION_KEYS (monitor, prepare, migrate, vault_candidate, unsupported), resolved by buildStablecoinVaultReadiness and rendered on the hosted page and by VaultReadinessLayer in the Migration Path panel. Score bands follow VAULT_READINESS_SCORE_THRESHOLDS (25, 50, 75).
  • Vault Simulator scanner outcomes: VAULT_READINESS_OUTCOMES (monitor, prepare, testnet-rehearsal, not-enough-data), mapped by deriveVaultReadinessWorkflow and rendered only in the /vault scan result.
  • Shared risk tiers: TIER_KEYS (monitor, review, prepare, migrate, vaultPrototype). The riskTier field on each recommendation names its shared tier; unsupported has none.

Product registration

The product navigation registry defines the two surfaces. The Stablecoin Vault leads PRODUCT_NAV_ITEMS, the primary homepage journey. The Vault Simulator is a detail route and does not appear in the primary nav.

Approved framing

Open the Stablecoin Vault

The flagship vault readiness journey, at vault.walletwall.org.

Vault Boundaries & Disclosures

Full custody, testnet, and quantum-security boundary statements.

Migration Readiness

The shared risk tiers, and how they relate to the Stablecoin Vault’s recommendations and the Vault Simulator’s scanner outcomes.

Quantum Intelligence

The exposure scoring model, and a scan that can carry a wallet and known values into the Stablecoin Vault page.

Policy-Gated Execution

Why key custody is necessary but not sufficient, and how the prototype bounds what an authorized path may do.

vNext Kernel Prototype

The experimental next-generation kernel: its boundary, evidence, and verifier-admission provenance.

Scanner Evidence & Assurance Model

How scanner output becomes evidence, and why an open-alert count is not a vulnerability count.

WallRoom

A synthetic migration scenario you can change one condition at a time.

WalletWall Vault research repository

Owns contracts, security assumptions, verifier design, tests, and deployment records.