Quantum Canary · Prepare: experimental research report and website on a DIY, open-source hardware device for generating a cryptocurrency seed offline with verifiable randomness, and a practical path from a standard wallet to a quantum-resistant one. Companion to the Quantum Canary (https://quantum-canary.sites.imd.fun, a public on-chain alarm, contract 0x626517225096671868609c1bbf9c1b416a4efd9a on Ethereum mainnet, that trips the day a quantum computer breaks secp256k1): the Canary says WHEN to move; this work says WHAT to build, HOW to generate keys, HOW to migrate.

Audience: a technically competent hobbyist (can solder, flash firmware, read Python/C/Rust), budget 50-300 EUR. Time frame: the state of the art as of October 2026, with the 2025-2026 developments. English, plain and precise.

Mandatory reference project: EthereumPhone PQ1, https://github.com/EthereumPhone/PQ1 (GPL-3.0, active October 2026). Read README.md, DIY.md, SECURITY.md, FIRMWARE_AUDIT_INTAKE.md and contracts/smart-wallet. Describe it accurately: STM32U585 (Cortex-M33 TrustZone) + Infineon OPTIGA Trust M V3 + NXP SE050E, XOR-split seed entropy across the two secure elements, SPHINCS+C10 hash-based signatures for every transaction, ERC-4337 PQSmartWallet behind an ERC-1967 proxy, trusted display, about $150 of off-the-shelf parts with Mouser links, runs in QEMU too. Report its own caveats where they matter: pre-production bring-up, no devices shipped, no on-chain wallets hold funds, firmware-format authority unresolved, known production-invariant regressions. Assess what a hobbyist can really build and verify today, what is missing for real funds, audit status, and how its choices (dual SE, symmetric-only SE channels, no secp256k1 anywhere) compare with the alternatives.

The report must also cover MIGRATION from a standard wallet to a quantum-resistant one, step by step, for an Ethereum user with a BIP-39 seed in a classic hardware wallet and for a Bitcoin user: what exists today (ERC-4337 accounts with a PQ verifier such as PQ1's PQSmartWallet, Safe modules, deployed verifier contracts with addresses and audit status; Bitcoin options and limits); order of operations (test with dust, generate the PQ account, move ETH, tokens, NFTs, staked positions, ENS, revoke approvals, rotate the old seed); what moving reveals (spending exposes the old pubkey forever); gas costs; chains with no PQ option; how to pre-authorize the migration so it executes the day the Canary trips (isTripped() as trigger, e.g. a Safe module or 4337 account that accepts the PQ owner once the canary balance drops); unaudited contracts vs waiting for protocol changes; a decision table migrate now / prepare / wait. And recommended builds with purchase links: a reference design (BOM table: part, role, buyable link on Mouser, DigiKey, Adafruit, Pimoroni, Waveshare or AliExpress, price; block diagram; firmware to fork; entropy pipeline; what to verify at each stage; residual risks), a variant under 60 EUR, a paranoid variant, the PQ1 BOM as an option, and which suits which user. Close with where the Canary fits: isTripped() as migration trigger, what the device holds ready, and the text of a "Prepare" section for the canary site.

Rules: cite a source for every factual claim (BIPs, EIPs, NIST FIPS 203/204/205 and SP 800-90B, repositories, audits, papers, datasheets for TRNG claims); prefer primary sources; mark observed vs inferred vs open question in 2026; no generic security advice not tied to the design; do not present closed-source hardware as the DIY answer; if a claim cannot be verified in a repository or docs, say so instead of guessing.

Deliverables: step 1 writes artifacts/report.md (5,000-9,000 words: one-page executive summary, comparison table of reference projects, migration decision table, BOM tables with purchase links, the procedure as a numbered checklist, references with links). Step 2 builds the static website that publishes that report, in the style of the canary site, so the canary site can link to it as "the DIY guide". The report title and the site title both begin with "Quantum Canary".