The problemBitcoin and nearly every coin after it secure ownership with ECDSA/Schnorr signatures. Those rely on the hardness of the elliptic-curve discrete-log problem — which a sufficiently large quantum computer breaks (Shor's algorithm). The hashing (SHA-256d) is fine; the
signatures are the exposure. When a signed transaction is broadcast, its public key is revealed, and a capable quantum adversary could in principle forge a spend before it confirms.
Friotaíoch is a straightforward experiment: keep the well-understood SHA-256d proof-of-work base, and add signature schemes that are believed to resist quantum attack — usable today.
The dual-scheme approachFRIO ships two NIST post-quantum signature schemes as native address types:
- ML-DSA-65 (FIPS 204, lattice-based) — witness v2, addresses begin frio1z…. Public key 1952 B, signature ~3309 B.
- SPHINCS+-128s (SLH-DSA, FIPS 205, hash-based) — witness v3, addresses begin frio1r…. Public key 32 B, signature 7856 B.
Two families with different security assumptions (lattice vs. hash) means if one is weakened, the other remains. Both are implemented from the reference sources and verified against the chain's own consensus verifier.
What's actually live- Mainnet running from genesis. Magic F710C0DE; P2P 51775, RPC 51777; native bech32 HRP frio.
- Six address types, all validated by the node:
– Legacy F…
– P2SH 7…
– SegWit v0 frio1q…
– bech32m frio1p…
– P2QR ML-DSA-65 frio1z…
– P2QR SPHINCS+-128s frio1r… - Block explorer, DNS seeder, ElectrumX server.
- Desktop wallets (Windows + Linux) built via CI.
- FRIO's address namespace is isolated — Bitcoin addresses are rejected by the node, so no cross-chain mis-send.
NEW: non-custodial browser quantum walletThe headline addition since launch: a
web wallet where post-quantum signing happens entirely in your browser.
- The ML-DSA-65 signer is compiled to WebAssembly and runs client-side. Your seed phrase never leaves the page — the server only relays the finished, signed transaction.
- We reimplemented FRIO's P2QR signature hash in JavaScript and verified it is byte-identical to the node's consensus code, then confirmed end-to-end that a browser-produced quantum signature is accepted and confirmed on-chain.
- Full flow works: derive a quantum address from your seed, receive to a real frio1z… address, send with automatic coin-selection and change, all signed in-browser.
- Live at wallet.friotaioch.com.
⚠️ Experimental — read this: The browser quantum-signing path works and is demonstrated on our test network, but it has
not undergone a security audit, and the main chain is in its earliest phase. This is software to explore and test,
not to store meaningful value in yet. Use throwaway amounts, expect rough edges, and report what breaks.
Chain parameters- Algorithm: SHA-256d proof-of-work
- Base: Bitcoin Core v29 fork
- Difficulty: ASERT (aserti3-2d), per-block retarget, anchored at genesis
- Target block time: 10 minutes
- Block reward: 50 FRIO, halving every 210,000 blocks · 21,000,000 cap
- Address HRP: frio · Magic: F710C0DE
- P2P port 51775 · RPC port 51777
- Genesis hash: 00000000908e647ce8296582a2d24023ef96a5e7d2320a5815b603463993676d
- No premine. Launched clean from its own genesis block.
Roadmap- Mainnet mining launch (public)
- SPHINCS+ (v3) signing in the browser wallet (ML-DSA is wired now; SPHINCS+ support is built and pending UI)
- Security review of the browser signing path before it's recommended for real value
- Wallet hardening: fee estimation, address rotation, multi-scheme UX
Honest positioningFRIO is not claiming to be the first or only post-quantum chain — combinations of ML-DSA and SLH-DSA exist elsewhere. What FRIO offers is this specific pairing on a SHA-256d PoW base, with a browser-native non-custodial quantum wallet, built and verified in the open by a solo developer. It's an experiment, presented as one.
LinksOpen source · solo-built · post-quantum from day one
