Roadmap

A ten-year plan with no finish line

Attacks improve and quantum hardware scales. We plan in 1, 2, 5 and 10-year horizons, and each one ends with a gate we have to pass before moving on.

1year

Foundation

Through the end of 2027. Publish the threat model, ship the first open-source library and get it independently audited.

Software

  • Threat model and layer specification v1 published
  • Open-source hybrid signing library: Ed25519 + ML-DSA-65, written in Rust
  • Known-answer tests, fuzzing and constant-time checks running in CI
  • Hybrid X25519 + ML-KEM-768 on all project services

Hardware

  • Signing device prototype on off-the-shelf secure elements
  • Entropy source characterized against SP 800-90B
  • Side-channel lab equipped and first leakage measurements taken

Community

  • Research notes published on a monthly cadence
  • Public bug bounty for the signing library
  • Quarterly transparency reports to $QSEC holders

Exit gate: library v1.0 completes an external audit with no open high or critical findings.

2years

Hardening

Through 2028. Put threshold signing in users' hands and push the hardware through its first full attack battery.

Software

  • 2-of-3 threshold wallet in public beta on Solana
  • Formal proofs for key parsers and signing state machine
  • Tamper-evident audit log live for all key operations
  • Second independent audit covering the wallet

Hardware

  • Engineering and design validation units of the signing device
  • Full in-house power, EM and fault-injection testing
  • Measured boot and open firmware with reproducible builds

Ecosystem

  • SDK so Solana apps can verify hybrid signatures
  • Hash-based vault prototype on devnet
  • Bug bounty extended to wallet and firmware

Exit gate: the device survives the full lab attack battery and the wallet beta passes its security review.

5years

Scale

Through 2031. Post-quantum protection by default across every product, certified hardware and institutional-grade tooling.

Software

  • Post-quantum signatures on by default in every product
  • Crypto-agility framework: swap algorithms without moving funds
  • Custody tooling for teams, DAOs and institutions
  • Formal verification extended to all critical modules

Hardware

  • Signing device in production
  • Pursuit of FIPS 140-3 and Common Criteria certification
  • Per-device attestation and tracked supply chain

Ecosystem

  • Contributions to post-quantum standards for blockchains
  • Standing external red-team program
  • Tested migration playbook for Ed25519 account holders

Exit gate: hardware certification achieved and the account migration playbook proven in a live, audited exercise.

10years

Permanence

Through 2036. Security that renews itself on a schedule, governed independently and funded to keep going.

Software

  • Automated, audited algorithm and parameter rotation
  • Every legacy classical-only path retired
  • Research into next-generation schemes as cryptanalysis evolves

Hardware

  • Third-generation device with an in-field upgrade path
  • Evaluation of custom secure silicon
  • Interfaces ready for quantum key distribution networks

Governance

  • Independent foundation stewarding the open-source stack
  • Long-term research fund for continued maintenance
  • Community voice in research priorities

Standing goal: no user funds ever lost to a cryptographic failure in our systems, measured and reported every year.

How we keep pace

The review cycle never stops

A roadmap is only useful if it keeps up with reality. Every quarter, independent of where we are in the plan, the team runs the same five-step cycle. If a new attack or a quantum hardware milestone shifts our timelines, the roadmap moves forward to meet it.

  • Every algorithm we use has a written replacement plan before it ships
  • Security margins are re-checked against the latest published attacks
  • Results of each cycle go into the quarterly transparency report
Quarterly cycle: monitor, research, harden, verify, deploy, then repeat Monitor Threats and new standards Research Evaluate new attacks Harden Raise parameters Verify Test and audit Deploy Roll out upgrades Every quarter then again

Track every milestone as it lands

Research notes and quarterly reports show progress against each gate.