Quantum Intelligence

Quantum Intelligence is WalletWall’s cross-cutting framework for estimating future cryptographic migration urgency for Ethereum wallets. It surfaces inside Holder Wall (wallet drawer), Whale Watcher (risk section), and Coinstellation (node detail panel).

Framing

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

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

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.

Signal group	Max points	What it measures
Signature exposure	35	Whether outgoing signature activity has been observed on-chain — the public key becomes recoverable after the first outgoing transaction. A wallet with observed history but no outgoing signature contributes a small baseline (5) instead.
Value at risk	25	Reported balance tier: `≥ $1M` (25), `≥ $100k` (18), `≥ $10k` (10), `> $0` (5). The migration-urgency “bounty.”
Dormancy	20	Observed last-activity bucket: `≥ 730d` (20), `180–730d` (12), `30–180d` (5), active (0).
Key / signature age	15	Age of the exposed key/signature: `≥ 5y` (15), `≥ 3y` (10), `≥ 1y` (5).
Migration-readiness offset	−10	Subtracted when a programmable upgrade path (ERC-4337 AA / multisig) is inferred, reflecting lower migration friction.

These weights are the SCORE_WEIGHTS contract. The composite is bucketed into the labels below. See Scoring Methodology for the plain-English factor walkthrough and worked example. 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.

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

Label	Score band	Meaning
Low exposure	below 25	Minimal priority; public key may not be exposed, or value is low.
Moderate exposure	≥ 25	Standard EOA risk; public key is exposed but migration is not yet urgent.
Elevated exposure	≥ 50	Significant value held in a classical EOA with a revealed public key.
Migration priority	≥ 75	High-value, exposed wallet with no clear path to automated rotation.
Unknown / insufficient data	`null`	Signature info or transaction history is unavailable — no score is emitted.

Prohibited terminology: “Quantum vulnerable”, “Quantum hacked soon”, “Q-Day target”, “Unsafe wallet”. Bands are read from the same score bounds listed in the table above (below 25 / ≥ 25 / ≥ 50 / ≥ 75). Unknown is a distinct, non-numeric outcome — it is never a synonym for a low score.

Source caveats

Every score carries a caveats array built from up to three layers:

Layer	When added
Base caveat (`SCORE_CAVEAT` constant)	Always
Coverage caveat	When key facts (chain profile, tx history, dormancy) are unavailable
Insufficient-data caveat	When `exposureStatus === 'unknown'`
Stale-data caveat	When scheduled Dune data is older than that query’s cadence-scaled staleness threshold
Missing-source caveat	When a required source alias is not configured
Live-only caveat	When a Dune API call failed or was skipped

Staleness is judged per query cadence, not by one flat threshold: queries on a daily refresh cadence flag at roughly 30 hours, while the migration-readiness query — which refreshes weekly by design — uses a weekly-scaled threshold. A weekly snapshot a few days old is on schedule, not late, and is no longer misreported as “Dune auto-run may be delayed.”

Exposure and dormancy facts are stablecoin-scoped: the underlying Dune queries read curated stablecoin tables (stablecoins_multichain.*), so surfaces describe USD-stablecoin balances and flows on Ethereum — the labels state that scope rather than implying all-token coverage.

Chain and signature assumptions

Chain type	Notes
EVM / Ethereum EOAs	Use ECDSA (secp256k1). Public key is recoverable from signature after first outgoing transaction. Accounts that have only received funds have lower immediate exposure.
Smart contract wallets / AA	ERC-4337 or multisig (Gnosis Safe) wallets may support future upgrades to quantum-resistant signatures. If the upgrade path is unknown, confidence is reduced.
Solana	Uses Ed25519. WalletWall does not support Solana holder analytics; Solana quantum risk is documented as a general category only.

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 Dune scheduled data
Source caveats and confidence level

Source provenance is shown via a data-source badge for each contributing data source.

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

Dormancy is measured from the last_active_at timestamp. The Dormancy exposure feed provides source-backed dormancy facts with bucket classification:

Bucket	Duration
`warm_dormant_30_180d`	30–180 days since last outgoing transaction
`cold_dormant_180_730d`	180–730 days (roughly 6 months to 2 years)
`ancient_dormant_730d_plus`	More than 730 days (2+ years)

Migration readiness

Migration readiness indicates whether a wallet has a viable path to adopt post-quantum cryptography (PQC) signatures. 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

is_contract_wallet: true does not mean the wallet is safe — it means it has a programmable upgrade path. The absence of a known-safe upgrade path should still yield low readiness.

How the three concepts relate

WalletWall keeps three distinct ideas separate so users don’t confuse “risk” with “a fix”:

Quantum Exposure
Migration Readiness
Stablecoin Vault

Question it answers: How urgent is the wallet-level risk?The composite 0–100 score (or null) defined above, built from the four signal groups and the migration-readiness offset.

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. The migration-readiness recommender returns level, urgency, difficulty, recommendedPath, blockers, and nextAction.

`recommendedPath`	When it is suggested
`monitor`	Small wallet, low exposure — no action needed yet
`fresh-wallet`	Older exposed wallet with medium value
`split-wallet`	Very high value concentrated in one address
`multisig`	High-value exposed wallet with no upgrade path
`treasury-custody`	DAO / treasury-like (Safe / multisig) wallet needing a signer-led migration path
`vault-prototype`	Long-horizon, high-value, quantum-exposed vault candidate

Stablecoin Vault & Vault Simulator (research prototypes)

When Migration Readiness recommends vault-prototype, Quantum Intelligence surfaces the wallet as a vault candidate and can route to the Stablecoin Vault readiness journey at vault.walletwall.org / /stablecoin-vault. The Stablecoin Vault readiness journey synthesizes Quantum Intelligence exposure signals, Holder Wall holder context, and Stable Seer stablecoin exposure to produce one of four outcomes: Monitor, Prepare, Testnet Rehearsal, or Not Enough Data. The Vault Simulator (/vault) is the Sepolia testnet rehearsal detail — surfaced from the Testnet Rehearsal outcome. 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.

Behavioral exposure signals

Behavioral signals (adversarialSignals) are deterministic heuristics derived from wallet transaction history and 12-week Dune activity data. They are computed by the behavioral-signals engine.

Signal definitions

Key	Approved label	What it observes
`extractionStyleActivityRisk`	extraction-style activity	Single large outgoing movement dominates outgoing volume
`counterpartyConcentrationRisk`	counterparty concentration	Activity concentrated among one or few counterparties
`relayRoutingExposure`	relay routing exposure	Incoming value closely followed by outgoing to different addresses
`activityRampRisk`	activity ramp	Recent activity sharply elevated vs. prior baseline
`assetValueAmbiguityRisk`	asset/value ambiguity	Token or value fields are ambiguous, missing, or unverifiable

Each signal carries score, confidence, reason, and evidence. Signals with score < 0.3 are not rendered. confidence reflects data completeness, not accusatory certainty. These signals are not findings of wrongdoing and do not imply intent, identity, or legal status.

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.

Dune source aliases

Public alias, query name, and cadence

Public alias	Query name	Cadence
Dormancy exposure feed	`walletwall_dormant_quantum_exposure_v1`	Weekly
Signature exposure feed	`walletwall_wallet_signature_exposure_v1`	Daily / on-demand
Value-at-risk feed	`walletwall_quantum_value_at_risk_v1`	Daily
Migration readiness feed	`walletwall_wallet_migration_readiness_v1`	Weekly

See Dune Queries for full field contracts and staleness thresholds.

Migration Readiness

How exposure becomes a recommended path — the shared Monitor / Review / Migrate / Vault Candidate tiers.

Quantum Exposure Clock

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