Blockstream names Falcon-1024 its leading lattice signature option

Blockstream’s research names Falcon-1024 as its leading lattice-based Bitcoin (BTC) signature option among three schemes: Dilithium, Falcon and Hawk. The company says it offers the strongest balance of signature size, verification speed and maturity of security assumptions.

That is a research conclusion, not a Bitcoin rollout announcement. Blockstream is evaluating lattice-based signatures as part of its assessment of defenses against future quantum computing threats.

Blockstream’s preferred candidate

The comparison weighs three operational measures: signature size, verification speed and maturity of security assumptions. On those measures, Blockstream identifies Falcon-1024 as the strongest candidate if a lattice-based scheme had to be selected now.

That ranking is conditional. Blockstream’s assessment leaves open how Falcon-1024 would work across the wider Bitcoin wallet ecosystem. The listed implementation work qualifies the comparison’s result. The research gives developers a reference candidate without declaring the signature transition ready for deployment.

Three hurdles remain

Blockstream lists three specific obstacles:

• Standards: Falcon-1024’s standards are not final.
• Hardware-wallet memory: Hardware wallets may face memory demands if they adopt the scheme.
• Public-key derivation: A viable method for deriving public keys is lacking.

Each obstacle affects a different part of adoption. Unfinished standards leave implementers without a settled target. Memory requirements can determine whether a scheme fits constrained wallet hardware. The missing public-key derivation method leaves a gap in the process needed to use the signature system.

The research provides no memory benchmark or deployment timetable. The operational case therefore remains incomplete, with device capacity and key handling requiring resolution before a Bitcoin implementation can move beyond evaluation.

Why hashes lead near term

Blockstream describes hash-based signatures as the more conservative near-term choice. The distinction matters because the lattice candidate’s potential advantages come with unresolved implementation constraints. In Blockstream’s assessment, hash-based signatures offer the more conservative path while those constraints remain unsettled.

The company does not present the two families as permanent rivals. Its research raises a possible future combination of hash-based and lattice-based signatures. The assessment does not set a readiness date for that combination or say whether Bitcoin would adopt it.

Algorand already has a path

Falcon-1024 also supports Algorand accounts. Existing Algorand users have a way to switch transaction authorization to the scheme. That gives the proposal a practical account-level use case beyond theoretical evaluation.

Bitcoin presents a harder path in Blockstream’s research. Its lattice work still carries the standards, hardware-wallet memory and public-key derivation hurdles. Algorand support does not erase those Bitcoin constraints, but it shows how the same signature scheme can fit an existing account framework.

What does this change for Bitcoin wallets?

For wallet operators, the change is a clearer candidate and a more explicit list of unresolved work. Falcon-1024 provides Blockstream’s preferred reference point for further design work. Teams still face the same underlying constraints: an unfinished standard, possible memory demands and no viable public-key derivation method identified in the research.

For Bitcoin users, the assessment does not announce an immediate signing requirement, wallet upgrade or network activation. The practical distinction is between a research preference and a deployed migration. Blockstream has selected a leading candidate for evaluation, while hash-based signatures retain the more conservative near-term position.

Any future Bitcoin market-structure change would still depend on final Falcon-1024 standards, a workable hardware-wallet memory profile and a viable public-key derivation path. Until those conditions are met, the choice remains a research preference rather than an operational migration.