Skip to main content
AVAILABLE · READ-ONLY · FORWARD-LOOKING HEURISTICA high Quantum Exposure Score does not mean a wallet is currently vulnerable to theft or exploitation by any existing technology. The score is a forward-looking heuristic for long-term cryptographic migration planning, not a statement of current risk. See what you can use today for every surface side by side.

What it does

Quantum Intelligence is WalletWall’s cross-cutting framework for estimating future cryptographic migration urgency for Ethereum wallets. It is the Intelligence area of WalletWall and also surfaces inside the wallet activity view (risk section) and the relationship graph (node detail panel).

What you can learn

WalletWall keeps three distinct ideas separate so “risk” is not confused with “a fix”:
Question it answers: How urgent is the wallet-level risk?The composite 0–100 score (or null) defined below, built from four signal groups and the migration-readiness offset.
You can also see how dormant a wallet is, which behavioral patterns its activity resembles, and how much confidence each reading deserves.

How to read it

Quantum Exposure Score

The score is a normalized value from 0 to 100 — or null when there is not enough evidence to score. It is built from four additive signal groups plus one subtractive migration-readiness offset. Each group contributes at most the points shown; missing data never adds points — an unavailable signal is recorded as unknown (0 points) and lowers confidence instead of inflating the score. See Scoring Methodology for the plain-English factor walkthrough and worked example.

Try it — exposure calculator

The table gives each group’s maximum. Between the anchor values, the value-at-risk, dormancy, and key-age axes interpolate continuously rather than stepping, so a wallet between two tiers scores between two tiers. This calculator applies the same SCORE_WEIGHTS and the same calibration curves as production — the weights and anchors are pinned to the canonical modules by test, so it cannot drift from the app. Set an axis to not observed to see the rule that matters most: missing evidence contributes 0 points and lowers confidence — it never makes a wallet look safer.

Score labels

Dormancy signal

Wallets that have not sent any outgoing transaction are classified as dormant. Dormancy increases migration urgency because:
  • The wallet may not be actively monitored
  • The holder may not respond to future migration requirements
  • Long-dormant wallets represent “cold” exposure that is hard to remediate
Migration readiness indicates whether a wallet has a viable path to adopt post-quantum cryptography (PQC) signatures. Migration Readiness can recommend a single migration path from existing wallet signals (value at risk, signature exposure, dormancy, wallet structure). It does not add a separate score.

Vault Readiness Card

The Vault Readiness Card renders the full score breakdown:
  • Composite score and risk band
  • Per-component breakdown with values
  • Behavioral exposure signals (adversarial signals)
  • Migration-readiness hints from scheduled data
  • Source caveats and confidence level
Source provenance is shown via a data-source badge for each contributing data source. The card’s Migration Path panel also includes a Vault Readiness block showing a Stablecoin Vault recommendation for this wallet.

Behavioral exposure signals

Behavioral signals are deterministic heuristics derived from wallet transaction history and the scheduled 12-week activity baseline. Confidence reflects data completeness, not accusatory certainty.

Policy simulator

The policy simulator allows exploring how score components would change under different wallet configuration assumptions (e.g., migrating to a Safe multisig, rotating keys). It operates on the current score breakdown and produces a hypothetical output — no on-chain action is taken.

Data freshness and provenance

The facts behind the score come from scheduled feeds, with chain-derived readings when a feed cannot be read for a request. A scheduled feed is never a live reading. See Data Serving Architecture for how each class of data is served and labelled.
Exposure and dormancy facts are stablecoin-scoped: the underlying scheduled feeds are built over curated stablecoin tables, so surfaces describe USD-stablecoin balances and flows on Ethereum — the labels state that scope rather than implying all-token coverage.
The signature-exposure snapshot holds one row per signer observed signing on a covered EVM chain in the last 90 complete UTC days. A wallet with no row is reported as not observed signing in the window, never as safe.
Every score carries caveats, built from these layers: Staleness is judged per feed cadence, not by one flat threshold: feeds on a daily refresh cadence flag at roughly 30 hours, while the migration-readiness feed — which refreshes weekly by design — uses a weekly-scaled threshold. A weekly snapshot a few days old is on schedule, not late.

Important boundaries

  • Future-looking: measures potential risk posed by future quantum computing advances to current cryptographic standards (ECDSA/secp256k1)
  • Not currently exploitable: no practical quantum attack exists against these standards today
  • Informational only: provided for cryptographic awareness and security planning
  • Not investment advice: must not be used as a basis for financial decisions
  • Missing is not safe: Unknown is a distinct, non-numeric outcome — it is never a synonym for a low score
  • A contract wallet is not automatically safe: it has a programmable upgrade path, and the absence of a known-safe upgrade path should still yield low readiness
  • Behavioral signals are not findings: they are not findings of wrongdoing and do not imply intent, identity, or legal status
Prohibited terminology: “Quantum vulnerable”, “Quantum hacked soon”, “Q-Day target”, “Unsafe wallet”.

Stablecoin Vault & Vault Simulator (research prototypes)

When Migration Readiness recommends vault-prototype, Quantum Intelligence surfaces the wallet as a vault candidate. Any scan with at least one vault-relevant signal can carry the wallet, with the balance and dormancy from its scheduled facts when they matched, into the Stablecoin Vault readiness journey at vault.walletwall.org / /stablecoin-vault. The Stablecoin Vault readiness journey evaluates those values, or the ones you enter, into one of five recommendation states: Monitor, Prepare, Migrate, Vault Candidate, or Unsupported. The Vault Simulator (/vault) is the separate Sepolia testnet rehearsal detail, with its own scanner outcomes. It demonstrates a hybrid classical + post-quantum authorization model: an Ethereum ECDSA signature plus an ML-DSA (FIPS 204, formerly CRYSTALS-Dilithium) signature. Related signature research includes SLH-DSA (FIPS 205, formerly SPHINCS+).
Both vault surfaces are research prototypes. The app does not store keys, does not ask for seed phrases, and does not implement recovery flows. The on-chain verifier is an architectural placeholder, not production-grade cryptographic verification. vault.walletwall.org is Stablecoin Vault (the readiness journey); /vault is the Vault Simulator (the Sepolia testnet detail route).
Approved framing: post-quantum migration research, hybrid authorization prototype, experimental migration path, vault candidate, Stablecoin Vault readiness, Vault Simulator (for /vault). Avoid absolute safety, recovery, or asset-control claims. See Stablecoin Vault & Vault Simulator for full product documentation.

Technical reference

How the score combines

These weights are the SCORE_WEIGHTS contract. The composite is bucketed into the score labels. Each signal group contributes independently, up to its own maximum; the migration-readiness offset is the only subtractive term. The same five weights from the table above — no others — drive the composite. Bands are read from the same score bounds listed in the score labels table (below 25 / ≥ 25 / ≥ 50 / ≥ 75). Unknown is a distinct, non-numeric outcome — it is never a synonym for a low score.

Chain and signature assumptions

Field and source reference

Dormancy is measured from the last_active_at timestamp. The Dormancy exposure feed provides source-backed dormancy facts with bucket classification:
The Migration readiness feed provides:
  • is_contract_wallet: true if the address is a contract-based wallet (Safe, multisig, ERC-4337 AA)
  • contract_wallet_type: safe, gnosis_multisig, erc4337_aa, or other_contract
  • recent_migration_signal: true if a token migration or key-rotation event was observed
  • risky_approval_count: count of active ERC-20 approvals with unlimited or large allowances
The migration-readiness recommender returns level, urgency, difficulty, recommendedPath, blockers, and nextAction.
Behavioral signals (adversarialSignals) are computed by the behavioral-signals engine. Each signal carries score, confidence, reason, and evidence. Signals with score < 0.3 are not rendered.
Every score carries a caveats array. The base caveat is the SCORE_CAVEAT constant, and the insufficient-data caveat applies when exposureStatus === 'unknown'.
The signature snapshot is read by wallet through a parameterised, byte-bounded query. A response says which source answered in metadata.signatureSource.See Dune Queries for the Dune field contracts and staleness thresholds.

Migration Readiness

How an exposure score becomes a recommended migration path, and how the shared tiers relate to it.

Quantum Exposure Clock

Why exposure is wallet-specific — key/signature age and value at risk, without a universal Q-Day countdown.

Policy-Gated Execution

Why a vault candidate’s migration path needs execution policy as well as key custody.

PQ Evidence, Rehearsal & ZK/SP1 Status

The read-only post-quantum evidence gates behind the readiness journey.