Campaign primitives (Phase 3)
Phase 3 ships six campaigns as preview/model-only. Each is a structured set of readiness actions targeting a specific wallet audience and security goal.Marketing launch themes
Each theme pairs a target audience with what qualifies for the campaign and — just as importantly — what must never be claimed about it. Expand a theme for its full guardrails.Quantum Exposure Reduction
Quantum Exposure Reduction
Core message: High-value wallets with observed signature exposure have more reason to plan and rehearse a future cryptographic migration. In the preview model, documented migration evidence can become an off-chain readiness record for later coordination.Target audience: Whale wallets with signature exposure and estimated value ≥ $100,000.What qualifies: Evidence of an on-chain migration to a previously-inactive address, evaluated from scheduled analytics data rather than self-attestation. This is a preview eligibility rule, not a guarantee that the migration was safe or complete.What to avoid claiming: Any implication that a quantum deadline is known, that WalletWall guarantees migration safety, controls the destination wallet, or distributes value for the migration.
Dormant Whale Readiness
Dormant Whale Readiness
Core message: Long-dormant, high-value wallets can deserve earlier migration review because inactivity may delay a response when cryptographic assumptions or operational requirements change. This campaign models how monitoring and recovery planning could bring those wallets into a readiness workflow.Target audience: Wallets inactive for ≥ 365 days with estimated value ≥ $100,000.What qualifies: Enabling watchlist monitoring, recording a recovery-planning step, or creating a readiness record in the preview model.What to avoid claiming: Any implication that WalletWall contacts wallet owners, knows whether an owner is attentive, manages dormant assets, or provides custodial protection for dormant value.
Vault Readiness
Vault Readiness
Core message: Vault-candidate wallets can rehearse a post-quantum migration path on testnet without moving real funds. The rehearsal is a research exercise, not evidence that the wallet is quantum-safe.Target audience: Programmable wallets that meet the vault-candidate classification threshold.What qualifies: Vault prototype simulation on testnet, guardian/recovery configuration represented by the readiness model, or another documented rehearsal step. No mainnet fund movement is required or implied.What to avoid claiming: Any implication that the vault prototype is production-ready, that funds are being moved or managed, or that vault readiness guarantees post-quantum safety.
Watchlist Monitoring
Watchlist Monitoring
Core message: Monitoring can reduce an observation blind spot by making wallet-state changes easier to notice and review. It is a low-friction readiness action, not a protection mechanism.Target audience: Wallets without active watchlist coverage.What qualifies: Enabling watchlist monitoring with alerting thresholds configured.What to avoid claiming: Any implication that monitoring prevents exposure, guarantees alert timeliness, or provides real-time chain state.
DAO Treasury Migration
DAO Treasury Migration
Core message: DAO and protocol treasuries can require governance-aware coordination before a cryptographic migration. This campaign models governance votes, readiness records, and migration planning without assuming that any one governance process is sufficient.Target audience: DAOs and protocol teams with observable on-chain governance participation.What qualifies: Governance votes on migration standards, treasury readiness records, or configured migration paths in the preview model.What to avoid claiming: Any implication that campaign participation grants financial authority over treasury assets, that a governance vote is binding without the relevant governance mechanism, or that any one migration path is the only viable one.Future sponsor model: DAO sponsors may fund this campaign’s coordination infrastructure. No payout model is defined or implemented.
Proof-of-Readiness Attestation
Proof-of-Readiness Attestation
Core message: Readiness work can be represented as a portable off-chain record. The current attestation schema is a coordination primitive, not cryptographic proof, certification, or a financial claim.Target audience: Any wallet that has completed at least one readiness action represented by the preview model.What qualifies: Creating an off-chain readiness-attestation record (Phase 2 schema) for a modeled readiness action. The current schema is not an on-chain or independently certified attestation.What to avoid claiming: Any implication that attestations are signed on-chain (Phase 2 is schema-only), independently verified, grant financial rights, or represent a payout claim.
Sponsor model progression
1
Now — native preview
walletwall_native_preview (Phase 3, current): WalletWall surfaces campaigns as an informational preview. No sponsor funds are involved.2
Future — sponsor-funded coordination (not implemented)
Three sponsor models are structurally defined but not built, and not ordered relative to one another:
dao_sponsored_future (a DAO funds coordination infrastructure for a targeted campaign), protocol_sponsored_future (a protocol funds readiness coordination for its ecosystem), and ecosystem_sponsored_future (broad ecosystem sponsors — foundations, grants — fund cross-protocol campaigns). All three remain non-custodial.
Sponsor models are structurally defined in the readiness-campaigns module. No sponsor marketplace UI is implemented.
What Protocol Reward Routing is not
Protocol Reward Routing (future optional scope) is non-custodial routing of readiness attestations to a protocol that handles reward distribution. WalletWall would not:- Hold assets
- Determine validator selection
- Control reward payouts
- Define a token or APY
Deferred items
Phase 3.5: Evidence hashes in campaigns
Phase 3.5 ships deterministic evidence-payload helpers. Campaigns can reference an evidence hash so a future verifier can compare a presented, allowlisted evidence object with the digest recorded by the preview model. Evidence hashes are:- Data-minimized — the helper admits only allowlisted, non-sensitive signal fields before hashing; the digest should not be treated as anonymization.
- Deterministic — the same admitted semantic signals produce the same hash regardless of key-insertion order.
- Off-chain — no on-chain write, no custody, no financial entitlement.
evidenceHash on its readiness-attestation record. A match would show that the presented admitted fields reproduce that digest; it would not independently prove that the underlying real-world or on-chain facts were retrieved faithfully.
No campaign currently enforces this verification flow; the helpers are available as building blocks for Phase 4+.
Legal and security review items
Before any campaign is promoted outside of preview:- Legal review of “readiness reward” framing in any jurisdiction where financial product rules apply
- Security review of attestation schema for phishing surface (fake attestations, replay)
- Threat model for evidence hash construction (what can and cannot be in an evidence payload)
- Governance review of
dao_sponsored_futuresponsor model before any DAO is approached
Related
Proof-of-Readiness Rewards
The action categories, eligibility model, reward ledger, attestation schema, and evidence-hash mechanics that these campaigns are built from.
Vault Boundaries & Disclosures
Custody, financial, testnet, and quantum-security boundaries that apply to every campaign and sponsor model on this page.

