Representatives of nine blockchain organizations have announced the Quantum Alliance, an initiative to develop common standards for post-quantum readiness. Founding contributor Postquant Labs outlined the initiative on October 15. Its announced program covers networks, wallets and infrastructure, with criteria and benchmarks still to be developed.

The founding organizations listed are Quantus, American Fortress, Intmax, Keystone, Midnight Foundation, Postquant Labs, Abelian, The Vault and Hacken. CoinDesk's October 16 reporting independently confirms the alliance's formation and planned standards work.

Four groups, five areas of evaluation

The first planned output is a public definition of readiness spanning transaction signatures, key management, consensus, zero-knowledge proof systems and peer-to-peer connections. The alliance also plans open test criteria, benchmarks and reference designs for migration.

Its four workstreams divide the engineering questions. A migration group will examine moving existing networks' funds and keys to new schemes. A zero-knowledge group will consider how to evaluate proof systems. A wallet group will address key generation, storage, signing and recovery. Cross-chain work will seek consistent handling of post-quantum keys across wallets, bridges and hardware signers.

Hacken says its contribution will focus on verification: the evidence needed to support a claim, methods for assessing implementations, and what results should communicate. These are announced responsibilities, with no completed verification results presented in that announcement.

An open process, with adoption still separate

Postquant Labs describes a process modeled on the Internet Engineering Task Force, welcoming individual contributors and advancing proposals through public evidence, rough consensus and working implementations. It says an organization's size or token holdings will give it no extra voting weight.

The announcements describe future specifications and evaluation tools. They set no Bitcoin or Ethereum activation date and establish no network-wide deployment. Publication of the criteria and subsequent implementation work remain separate steps.