PREVIEW · READ-ONLY · NO REWARD DISTRIBUTEDStatus (1 November 2026): pre-release preview. The eligibility rules, the local reward
ledger, the attestation schema and the campaign definitions on this page exist in the application
as a read-only preview. No reward has been distributed, no payout or sponsor mechanism is
implemented, and no on-chain token exists. See What you can use today.
What this is
The model is designed to recognize wallets that take concrete steps to reduce quantum exposure risk, configure recovery, enable monitoring, and participate in migration governance. The incentive structure is aligned with security outcomes, not with the size of a deposit or the duration of a lock-up.What this is not
Why quantum migration is a governance coordination problem
Post-quantum migration is not a solo action. The Ethereum ecosystem cannot migrate atomically — it requires:- Shared standards for what counts as a post-quantum migration path
- Coordination across wallet providers, protocol teams, and key holders
- Reference implementations and inspectable migration records
Reward action categories
Each category is evaluated independently against a wallet’s observable signals. Expand a category for its eligibility signal, verification source, and custody posture — every category requires no custody.Exposure reduction
Exposure reduction
Wallets that migrate away from a public-key-exposed address, as observed in scheduled analytics, reduce the concentration of value behind that exposed key. This is the most direct, measurable readiness action.Eligibility signal: signature exposure observed AND estimated value ≥ $100,000
Verification: on-chain migration transaction observed in scheduled analytics
Custody required: no
Verification: on-chain migration transaction observed in scheduled analytics
Custody required: no
Vault readiness
Vault readiness
Wallets can rehearse a post-quantum vault migration path — through programmable wallet structure, guardian configuration, or recovery policy simulation — without moving real funds. A rehearsal is research, not evidence that the wallet is quantum-safe.Eligibility signal: vault-candidate classification (programmable wallet with meaningful value)
Verification: WalletWall Vault prototype (testnet) and scheduled wallet classification
Custody required: no
Verification: WalletWall Vault prototype (testnet) and scheduled wallet classification
Custody required: no
Recovery setup
Recovery setup
Wallets with no configured recovery path represent the highest concentration risk for unrecoverable value loss. Configuring a recovery path — multisig threshold, guardian designation, or emergency withdrawal policy — is an observable readiness action.Eligibility signal: recovery classification of
Verification: WalletWall recovery readiness classifier
Custody required: no
should-configure-recovery or needs-urgent-migrationVerification: WalletWall recovery readiness classifier
Custody required: no
Monitoring
Monitoring
Enabling active monitoring on a wallet generates richer signal data for the whole ecosystem. It is a low-effort, high-impact readiness action.Eligibility signal: watchlist not enabled
Verification: WalletWall watchlist configuration
Custody required: no
Verification: WalletWall watchlist configuration
Custody required: no
Governance participation
Governance participation
Voting on quantum migration readiness standards, flagging exposure patterns for community review, and contributing to governance proposals creates shared coordination for migration at scale.Eligibility signal: active governance context detected
Verification: on-chain or off-chain snapshot records
Custody required: no
Verification: on-chain or off-chain snapshot records
Custody required: no
Readiness attestation
Readiness attestation
Non-custodial attestations — EIP-712 typed signatures or off-chain records — create portable records of completed readiness actions without moving funds or revealing keys. A record is a coordination primitive, not cryptographic proof that an action was safe or complete.Eligibility signal: any completed readiness review
Verification: attestation signature and source action
Custody required: no
Verification: attestation signature and source action
Custody required: no
Eligibility model
The eligibility helper (getProofOfReadinessRewardActions) accepts a plain object of wallet signals and returns the subset of actions that are relevant for that wallet. Rules are deterministic and conservative:
Future scope: Protocol Reward Routing
Protocol-native reward routing — non-custodial staking routing, validator selection, or on-chain attestation anchoring — is future optional scope only. If implemented, it will be non-custodial routing only: WalletWall would route readiness attestations to a protocol that handles reward distribution. WalletWall would not hold assets, determine validator selection, or control reward payouts. Not yet implemented: routing, staking integration, APY display, validator selection, wallet connection for rewards, transaction flows, or any on-chain reward token.Non-custodial guarantees
The Proof-of-Readiness Rewards model is constrained by the same guardrails as the rest of WalletWall:- WalletWall never stores private keys
- WalletWall never asks for seed phrases
- WalletWall never moves funds on your behalf
- Eligibility is determined from publicly observable on-chain facts only
- No action requires a deposit or a lock-up
Phase 2: Local reward ledger and attestation schema
Phase 2 adds a local, off-chain reward ledger model and a Proof-of-Readiness attestation schema. Neither introduces custody, payouts, database persistence, or any on-chain writes.1
Eligibility determined
Wallet signals are evaluated against the reward action rules described above (
getProofOfReadinessRewardActions).2
Reward event tracked locally
A reward event moves through the local ledger statuses below:
eligible → suggested → completed_local → attestation_ready.3
Evidence hash computed (Phase 3.5)
A deterministic hash of redacted, allowlisted signals is computed — described later in Phase 3.5.
4
Attestation issued (schema only)
An off-chain attestation references the evidence hash. It is not signed on-chain, not a payout, and not a reward claim.
Local reward ledger
The local reward ledger tracks readiness reward events in memory only — no database, no chain interaction, no server persistence.Readiness statuses
This is a local, in-memory reward-event record, not a payout and not a blockchain transaction status — it mirrors the status table above.
Reward event shape
A reward event is a plain object with no financial fields:rewardUnits is a non-monetary counter that may inform future non-custodial governance weight. It is not a token balance, not a payout, and not a financial entitlement of any kind.
Proof-of-Readiness attestation schema
The attestation schema defines the structure of an off-chain readiness attestation. Phase 2 is schema-only: no cryptographic signing, no wallet connection, no on-chain write.Evidence hash concept
TheevidenceHash field is an opaque string representing a hash of the evidence that supports a readiness action. For example:
- For an on-chain migration: a hash of the transaction hash and target address
- For a vault readiness check: a hash of the readiness score snapshot
- For watchlist monitoring: a hash of the wallet address and configuration timestamp
Replay prevention and nonce
Thenonce field prevents replay of an attestation across different contexts. It must be a unique string per attestation issuance — typically a UUID, a random hex string, or a timestamped value. WalletWall does not enforce a specific nonce format.
Attestation shape
Attestations are not payouts
Phase 3: Readiness campaigns
Phase 3 introduces readiness campaigns — structured sets of security-positive actions that help wallets, DAOs, and protocols coordinate quantum migration readiness. Campaigns are informational scaffolding only: no custody, no payouts, no staking, no protocol reward routing, and no on-chain writes.What a readiness campaign is
A readiness campaign bundles:- A targeted wallet audience (individual wallet, whale wallet, DAO treasury, protocol team)
- A clear security goal (migrate, monitor, attest, configure recovery)
- A set of eligible Phase 1 readiness action IDs
- A sponsor model (native preview or future sponsor)
- Structural invariants:
custodyRequired: false,payoutImplemented: false,protocolRoutingImplemented: false
Campaign table
All campaigns are in preview/model-only status. No sponsor marketplace is implemented. Protocol Reward Routing remains future optional scope.
Campaign eligibility
getReadinessCampaignsForWallet(walletSignals) maps existing wallet signals to recommended campaigns:
Why campaigns do not require custody or deposits
Each campaign targets an observable on-chain or local-state signal (signature exposure, dormancy, vault candidate classification, watchlist state, governance participation, completed action). There is no deposit gate, no lock-up, no APY, and no staking requirement. The campaign model is aligned with security outcomes, not with capital flows.Future sponsor model
Future sponsor models (dao_sponsored_future, protocol_sponsored_future, ecosystem_sponsored_future) are defined structurally but not implemented. When sponsor campaigns are introduced, they will remain non-custodial: a sponsor funds the coordination infrastructure, not the wallets participating in it.
See proof-of-readiness-campaign-roadmap for the product-strategy view.
Phase 3.5: Deterministic evidence hashes
Phase 3.5 adds a set of evidence helpers that build data-minimized evidence payloads and compute deterministic evidence hashes. These hashes are what attestations reference in theirevidenceHash field.
How evidence hashes work
What evidence hashes are
What evidence hashes are
An evidence hash is a stable
0x-prefixed SHA-256 digest of a redacted evidence payload. The payload names the wallet address and captures the allowlisted signals (dormancy, exposure tier, vault eligibility) that motivated a readiness action, without raw transaction or balance history. The digest identifies those bytes; it should not be treated as anonymization.Why payloads are redacted
Why payloads are redacted
Every evidence payload is normalized before hashing: only an explicit allowlist of signal fields (such as
hasSignatureExposure, dormantDays, migrationReadinessTier, vaultEligible) is preserved. All other signal fields — including any identity-revealing, financial, or sensitive data — are stripped before the payload is constructed. The payload’s privacy field is always "redacted" and custody is always "none".Sensitive fields that are always stripped:
privateKey, seed, seedPhrase, mnemonic, secret, email, ipAddress, sessionToken, accessToken, rawTransactionHistory, fullBalanceHistory, amount, payout, rewardToken, apy, yield, stake, deposit.Why hashes are deterministic
Why hashes are deterministic
Before hashing, the payload is serialized with keys sorted alphabetically at every level. This means the same semantic payload always produces the same hash regardless of the JavaScript key-insertion order. Any party that holds the original payload can recompute the hash that attestations and reward events reference. A match shows that the payload reproduces the digest, nothing more.
Why evidence hashes are not payouts, custody, or guarantees
A matching evidence hash shows that a presented payload reproduces the digest. It does not independently prove that the underlying signals were observed faithfully. It is also:- Not a financial instrument. Hashing signals creates no financial entitlement.
- Not custody. WalletWall does not hold assets, keys, or any value as a result of creating evidence.
- Not a guarantee. A hash does not guarantee that any reward, payout, or distribution will follow.
- Not on-chain. Evidence payloads and their hashes are off-chain only.
Evidence payload shape
campaignId is optional and only present when the evidence is tied to a specific readiness campaign.
Creating an evidence hash
Attestation referencing an evidence hash
An attestation can be created from an evidence object directly; theevidenceHash is derived automatically:
evidenceHash string can still be passed and takes precedence over evidence.hash, preserving the existing Phase 2 API.
Allowed evidence types
Allowed signal fields (allowlist)
Copy guardrails
The following phrases are prohibited throughout all Proof-of-Readiness Rewards copy, enforced by the test suite:earn interestguaranteed yielddeposit to earnWalletWall pays APYpassive incomerisk-freeinsuredbank-like
Related
Proof-of-Readiness Campaign Roadmap
The product-strategy view: marketing themes, sponsor model progression, and deferred items for these reward categories.
Key Management & Recovery Model
The full non-custodial boundary — no stored keys, no seed phrases, no fund movement — that constrains this entire rewards model.

