The hardest part of PoUW is making real-world optimization compatible with consensus.
Bitcoin solves this with hashes that are cheap to verify.
QMS replaces arbitrary hashing with commercially valuable optimization problems while keeping computational work at the heart of consensus.
Original Tweet
X | LinkedIn | Medium | Docs
Bitcoin solves this with hashes that are cheap to verify.
QMS replaces arbitrary hashing with commercially valuable optimization problems while keeping computational work at the heart of consensus.
Original Tweet
X | LinkedIn | Medium | Docs
❤2
We received some really good questions from you, and here’s our CTO Christopher Portmann’s reply, ICYMI:
1️⃣ Q: I haven't quite figured out yet whether the testnet network prioritizes GPU or CPU?
Chris: The first version will be CPUs. Once we can better gauge demand and the computational power needed to meet it, we can optimise the code for GPUs.
Note that our first version will also allow for hybrid quantum-classical miners, where part of the computation is done on a QPU. Admittedly, at the moment these still cost more and produce less, but the design is ready for the next frontier in computing.
2️⃣ Q: As quantum solvers join the network, what’s your current thinking on proof-of-work verification for quantum outputs since they don’t produce a replayable classical path? Are you exploring ZK-based approaches here?
Chris: That’s a brilliant question. The short answer is no, we are exploring the use of hash-based (ZK-)SNARKs for improving verification in the classical case. But for the quantum case, something else is needed.
ZK-proofs are often designed to be short and efficient to verify, so they can be used to shift the burden from the verifiers to the prover (that is what zk-rollups do). They also provide the ZK-property, which in the context of computation verification, could allow a miner to prove that they have done the correct computation without revealing what computation that is (e.g., to preserve confidentiality of the client’s data). So they can be used to improve proofs, but they can’t be used to come up with proofs in a setting where we don’t already know how to generate (large, non-zk) proofs.
In the quantum case, we can verify that the output is correct, but what we don’t yet know how to do, is for a quantum miner to prove that they haven’t pre-computed the output (e.g., they learned about the input before other miners, and get an advantage which doesn’t correspond to their computational power). Classical replayable paths solve the problem, because in the classical case the miners are forced to follow a path that depends on the hash of the last block, so we just need to verify that they did take that path. We are working with academic partners on solving the quantum case.
3️⃣ Q: Will QMS network allow users to migrate from current wallet addresses to quantum-safe ones?
Chris: As soon as Ethereum pushes the account abstraction feature that we need, we will be able to implement this.
Since Ethereum’s roadmap for a post-quantum (PQ) consensus will take years, we are implementing PQ-consensus ourselves. But the account abstraction features needed to migrate current addresses to quantum safe ones should be released with the Ethereum Hegotá update at the end of the year (hopefully). And since we do not want to reinvent the wheel, we will wait for that and base our PQ-addresses on it.
Original Tweet
X | LinkedIn | Medium | Docs
1️⃣ Q: I haven't quite figured out yet whether the testnet network prioritizes GPU or CPU?
Chris: The first version will be CPUs. Once we can better gauge demand and the computational power needed to meet it, we can optimise the code for GPUs.
Note that our first version will also allow for hybrid quantum-classical miners, where part of the computation is done on a QPU. Admittedly, at the moment these still cost more and produce less, but the design is ready for the next frontier in computing.
2️⃣ Q: As quantum solvers join the network, what’s your current thinking on proof-of-work verification for quantum outputs since they don’t produce a replayable classical path? Are you exploring ZK-based approaches here?
Chris: That’s a brilliant question. The short answer is no, we are exploring the use of hash-based (ZK-)SNARKs for improving verification in the classical case. But for the quantum case, something else is needed.
ZK-proofs are often designed to be short and efficient to verify, so they can be used to shift the burden from the verifiers to the prover (that is what zk-rollups do). They also provide the ZK-property, which in the context of computation verification, could allow a miner to prove that they have done the correct computation without revealing what computation that is (e.g., to preserve confidentiality of the client’s data). So they can be used to improve proofs, but they can’t be used to come up with proofs in a setting where we don’t already know how to generate (large, non-zk) proofs.
In the quantum case, we can verify that the output is correct, but what we don’t yet know how to do, is for a quantum miner to prove that they haven’t pre-computed the output (e.g., they learned about the input before other miners, and get an advantage which doesn’t correspond to their computational power). Classical replayable paths solve the problem, because in the classical case the miners are forced to follow a path that depends on the hash of the last block, so we just need to verify that they did take that path. We are working with academic partners on solving the quantum case.
3️⃣ Q: Will QMS network allow users to migrate from current wallet addresses to quantum-safe ones?
Chris: As soon as Ethereum pushes the account abstraction feature that we need, we will be able to implement this.
Since Ethereum’s roadmap for a post-quantum (PQ) consensus will take years, we are implementing PQ-consensus ourselves. But the account abstraction features needed to migrate current addresses to quantum safe ones should be released with the Ethereum Hegotá update at the end of the year (hopefully). And since we do not want to reinvent the wheel, we will wait for that and base our PQ-addresses on it.
Original Tweet
X | LinkedIn | Medium | Docs
❤4👍2
As always, share your technical questions with us, and we’ll provide thoughtful and truthful replies.
X: https://x.com/QMSNetwork
Website: https://qms.finance
LinkedIn: https://linkedin.com/company/qms-network
Medium: https://medium.com/@QMSNetwork
X: https://x.com/QMSNetwork
Website: https://qms.finance
LinkedIn: https://linkedin.com/company/qms-network
Medium: https://medium.com/@QMSNetwork
👍3❤2
"What if mining had two “customers” instead of one?
Today, miners are paid by the network. QMS adds another source of demand: commercial optimization problems.
The same computation helps secure the chain while producing something businesses already pay for.
One computation. Two revenue streams.
Original Tweet
X | LinkedIn | Medium | Docs
Today, miners are paid by the network. QMS adds another source of demand: commercial optimization problems.
The same computation helps secure the chain while producing something businesses already pay for.
One computation. Two revenue streams.
Original Tweet
X | LinkedIn | Medium | Docs
❤5
Most blockchains fund their security from inside the network.
QMS explores a different model.
Commercial demand → stronger miner incentives → a stronger network → more commercial demand.
That’s the flywheel QMS is designed to build.
Original Tweet
X | LinkedIn | Medium | Docs
QMS explores a different model.
Commercial demand → stronger miner incentives → a stronger network → more commercial demand.
That’s the flywheel QMS is designed to build.
Original Tweet
X | LinkedIn | Medium | Docs
❤4
Traditional mining:
spend energy → secure the network → earn block rewards.
QMS mining:
spend energy → secure the network while solving a commercial optimization problem → earn block rewards + client payments.
Original Tweet
X | LinkedIn | Medium | Docs
spend energy → secure the network → earn block rewards.
QMS mining:
spend energy → secure the network while solving a commercial optimization problem → earn block rewards + client payments.
Original Tweet
X | LinkedIn | Medium | Docs
❤3👍3
Many people don’t realize this, banks are further along in post-quantum migration than much of crypto.
Regulators have already pushed financial institutions into multi-year transition plans.
Crypto has a different challenge:
- Wallets
- Exchanges
- Custodians
- Bridges
- Smart contracts
- Users
That’s why post-quantum readiness is easier to design in than retrofit.
Original Tweet
X | LinkedIn | Medium | Docs
Regulators have already pushed financial institutions into multi-year transition plans.
Crypto has a different challenge:
- Wallets
- Exchanges
- Custodians
- Bridges
- Smart contracts
- Users
That’s why post-quantum readiness is easier to design in than retrofit.
Original Tweet
X | LinkedIn | Medium | Docs
❤5
The best CTOs in deep tech can move fluently between theory and production.
Meet Christopher Portmann, CTO of QMS Network.
Christopher brings more than 20 years of experience across advanced cryptography, decentralized systems, and blockchain protocol design.
After 15 years in academia, a Ph.D. in quantum cryptography, and more than a dozen peer-reviewed publications, he joined Concordium, where he led the design of core blockchain protocols, including novel consensus mechanisms and zero-knowledge-based identity systems.
Working closely with engineering teams, he helped carry those designs from formal security proofs through to production.
At QMS, Christopher leads the protocol’s overall architecture and engineering execution. His work spans cryptographic research, protocol design, the post-quantum transition, and QMS’s long-term research programme on quantum hardware integration.
Few people combine that level of research depth, protocol design, and production experience. For a blockchain preparing for the quantum era, that range matters.
QMS was built around an ambitious technical vision. We’re proud to have Christopher leading the team bringing it to life!
Original Tweet
X | LinkedIn | Medium | Docs
Meet Christopher Portmann, CTO of QMS Network.
Christopher brings more than 20 years of experience across advanced cryptography, decentralized systems, and blockchain protocol design.
After 15 years in academia, a Ph.D. in quantum cryptography, and more than a dozen peer-reviewed publications, he joined Concordium, where he led the design of core blockchain protocols, including novel consensus mechanisms and zero-knowledge-based identity systems.
Working closely with engineering teams, he helped carry those designs from formal security proofs through to production.
At QMS, Christopher leads the protocol’s overall architecture and engineering execution. His work spans cryptographic research, protocol design, the post-quantum transition, and QMS’s long-term research programme on quantum hardware integration.
Few people combine that level of research depth, protocol design, and production experience. For a blockchain preparing for the quantum era, that range matters.
QMS was built around an ambitious technical vision. We’re proud to have Christopher leading the team bringing it to life!
Original Tweet
X | LinkedIn | Medium | Docs
❤7🔥5
This media is not supported in your browser
VIEW IN TELEGRAM
This week, 3 developments showed the post-quantum retrofit challenge moving down the stack: from legacy wallet recovery, to transaction validation agility, to core key-management infrastructure.
1️⃣ A practical post-quantum Bitcoin recovery path is now working.
On July 15, Project Eleven unveiled a post-quantum zero-knowledge proof, developed with Binius lead, Jim Posen. It lets users prove that key material higher in a BIP-32 derivation tree produced a given address without revealing the key material itself.
The prototype generates the proof in 243 ms and verifies it in 40 ms on a laptop (M5 MacBook Air, CPU only), with no trusted setup. It remains an unaudited early prototype and would still require explicit protocol support to recover live assets.
This moves one of the hardest parts of post-Q-Day wallet recovery from theory to a concrete engineering path.
2️⃣ Ethereum is gaining signature agility at the transaction layer.
On July 14, Nethermind opened a WIP PR implementing EIP-8141 Frame Transactions (tx type 0x06). The proposal makes the sender explicit in the payload and separates validation from execution, allowing accounts to define their own validation logic instead of being permanently tied to envelope-level ECDSA.
It creates a clean on-ramp for future post-quantum authentication schemes. The implementation is still incomplete and off-by-default.
Changing a core cryptographic assumption embedded in every transaction is expensive, and this is exactly the kind of plumbing work required.
3️⃣ Post-quantum cryptography is entering the key-management standard stack.
On July 15, OASIS Open announced that PKCS #11 Specification v3.2 and Profiles v3.2 have been approved as OASIS Standards. Version 3.2 adds support for post-quantum mechanisms to Cryptoki, the interface used by HSMs, smart cards, and certificate authorities, while the Profiles document defines conformance requirements for interoperability.
Selecting post-quantum algorithms is only the first step. The infrastructure that actually stores keys and authorizes operations now has a path to support them consistently across vendors.
Original Tweet
X | LinkedIn | Medium | Docs
1️⃣ A practical post-quantum Bitcoin recovery path is now working.
On July 15, Project Eleven unveiled a post-quantum zero-knowledge proof, developed with Binius lead, Jim Posen. It lets users prove that key material higher in a BIP-32 derivation tree produced a given address without revealing the key material itself.
The prototype generates the proof in 243 ms and verifies it in 40 ms on a laptop (M5 MacBook Air, CPU only), with no trusted setup. It remains an unaudited early prototype and would still require explicit protocol support to recover live assets.
This moves one of the hardest parts of post-Q-Day wallet recovery from theory to a concrete engineering path.
2️⃣ Ethereum is gaining signature agility at the transaction layer.
On July 14, Nethermind opened a WIP PR implementing EIP-8141 Frame Transactions (tx type 0x06). The proposal makes the sender explicit in the payload and separates validation from execution, allowing accounts to define their own validation logic instead of being permanently tied to envelope-level ECDSA.
It creates a clean on-ramp for future post-quantum authentication schemes. The implementation is still incomplete and off-by-default.
Changing a core cryptographic assumption embedded in every transaction is expensive, and this is exactly the kind of plumbing work required.
3️⃣ Post-quantum cryptography is entering the key-management standard stack.
On July 15, OASIS Open announced that PKCS #11 Specification v3.2 and Profiles v3.2 have been approved as OASIS Standards. Version 3.2 adds support for post-quantum mechanisms to Cryptoki, the interface used by HSMs, smart cards, and certificate authorities, while the Profiles document defines conformance requirements for interoperability.
Selecting post-quantum algorithms is only the first step. The infrastructure that actually stores keys and authorizes operations now has a path to support them consistently across vendors.
Original Tweet
X | LinkedIn | Medium | Docs
❤3
Many people don’t realize this, banks are further along in post-quantum migration than much of crypto.
Regulators have already pushed financial institutions into multi-year transition plans.
Crypto has a different challenge:
- Wallets
- Exchanges
- Custodians
- Bridges
- Smart contracts
- Users
That’s why post-quantum readiness is easier to design in than retrofit.
Original Tweet
X | LinkedIn | Medium | Docs
Regulators have already pushed financial institutions into multi-year transition plans.
Crypto has a different challenge:
- Wallets
- Exchanges
- Custodians
- Bridges
- Smart contracts
- Users
That’s why post-quantum readiness is easier to design in than retrofit.
Original Tweet
X | LinkedIn | Medium | Docs
❤2
Quantum computing is a geopolitical race now.
The US is putting ~$2B in CHIPS incentives into nine quantum companies and taking minority equity stakes. DOE is targeting a fault-tolerant system by 2028.
Japan invested heavily in quantum alongside a ~$7B chips-and-quantum package.
The UK added up to £2B in March.
Estimates put China's cumulative public spend as high as $15B, and Beijing put quantum first among its "future industries."
And Google's March paper dropped the qubit estimate for breaking secp256k1 below 500,000, roughly 20x lower than the prior best.
Governments are buying the sword and mandating the shield.
Original Tweet
X | LinkedIn | Medium | Docs
The US is putting ~$2B in CHIPS incentives into nine quantum companies and taking minority equity stakes. DOE is targeting a fault-tolerant system by 2028.
Japan invested heavily in quantum alongside a ~$7B chips-and-quantum package.
The UK added up to £2B in March.
Estimates put China's cumulative public spend as high as $15B, and Beijing put quantum first among its "future industries."
And Google's March paper dropped the qubit estimate for breaking secp256k1 below 500,000, roughly 20x lower than the prior best.
Governments are buying the sword and mandating the shield.
Original Tweet
X | LinkedIn | Medium | Docs
👍4❤2
Our CTO, Christopher Portmann, has been elected by the community to the 2026 Concordium Governance Committee.
Reflecting on the appointment, Christopher shared that his time with Concordium has shaped how he approaches L1 architecture - lessons he now applies while building QMS Network’s post-quantum-secure PoUW chain. He also said he’s excited to continue contributing as both ecosystems tackle overlapping challenges.
Original Tweet
X | LinkedIn | Medium | Docs
Reflecting on the appointment, Christopher shared that his time with Concordium has shaped how he approaches L1 architecture - lessons he now applies while building QMS Network’s post-quantum-secure PoUW chain. He also said he’s excited to continue contributing as both ecosystems tackle overlapping challenges.
Original Tweet
X | LinkedIn | Medium | Docs
❤6🔥3
The post-quantum transition cannot wait for a perfect signature algorithm. That is the central message of Cloudflare's latest analysis.
ML-DSA-44 is available today, but it carries real costs. Its signatures are 2,420 bytes, compared with 64 bytes for Ed25519, while its public keys are 1,312 bytes versus 32. NIST advanced nine additional candidates to a third round in June, yet Cloudflare estimates that several promising alternatives may not be widely available until 2033–35.
The deployment timeline matters just as much. Dilithium, the scheme that became ML-DSA, entered the NIST competition in November 2017 and was finalized as a standard in August 2024. The first CMVP certificates for an ML-DSA module followed in March 2026, while Cloudflare does not expect the first ML-DSA certificates in the WebPKI until early 2027.
Standardization is only the beginning. Protocol integration, software support, validation and ecosystem-wide migration take years.
Cloudflare is targeting 2029 to become fully post-quantum secure. The June 2026 US executive order adds further urgency: it directs OMB to require federal agencies to transition high-value assets and high-impact systems to post-quantum key establishment by December 31, 2030, and digital signatures by December 31, 2031.
The deeper lesson is architectural. No single post-quantum signature optimizes size, speed, security and implementation simplicity. Systems must be built around those trade-offs while preparing for a lengthy transition.
During that transition, continued support for classical-only authentication can enable downgrade attacks unless the protocol prevents or detects them. Cloudflare notes that simply switching classical cryptography off is not even an option for many sufficiently distributed systems, including the WebPKI.
This closely aligns with the design QMS is working on: block production requires no digital signatures, post-quantum finality runs asynchronously outside the block-production critical path, and PQ signatures for EVM accounts are introduced gradually.
Original Tweet
X | LinkedIn | Medium | Docs
ML-DSA-44 is available today, but it carries real costs. Its signatures are 2,420 bytes, compared with 64 bytes for Ed25519, while its public keys are 1,312 bytes versus 32. NIST advanced nine additional candidates to a third round in June, yet Cloudflare estimates that several promising alternatives may not be widely available until 2033–35.
The deployment timeline matters just as much. Dilithium, the scheme that became ML-DSA, entered the NIST competition in November 2017 and was finalized as a standard in August 2024. The first CMVP certificates for an ML-DSA module followed in March 2026, while Cloudflare does not expect the first ML-DSA certificates in the WebPKI until early 2027.
Standardization is only the beginning. Protocol integration, software support, validation and ecosystem-wide migration take years.
Cloudflare is targeting 2029 to become fully post-quantum secure. The June 2026 US executive order adds further urgency: it directs OMB to require federal agencies to transition high-value assets and high-impact systems to post-quantum key establishment by December 31, 2030, and digital signatures by December 31, 2031.
The deeper lesson is architectural. No single post-quantum signature optimizes size, speed, security and implementation simplicity. Systems must be built around those trade-offs while preparing for a lengthy transition.
During that transition, continued support for classical-only authentication can enable downgrade attacks unless the protocol prevents or detects them. Cloudflare notes that simply switching classical cryptography off is not even an option for many sufficiently distributed systems, including the WebPKI.
This closely aligns with the design QMS is working on: block production requires no digital signatures, post-quantum finality runs asynchronously outside the block-production critical path, and PQ signatures for EVM accounts are introduced gradually.
Original Tweet
X | LinkedIn | Medium | Docs
❤2👍2
QMS Network Official
The post-quantum transition cannot wait for a perfect signature algorithm. That is the central message of Cloudflare's latest analysis. ML-DSA-44 is available today, but it carries real costs. Its signatures are 2,420 bytes, compared with 64 bytes for Ed25519…
Valuable and timely analysis from the Cloudflare team:
https://blog.cloudflare.com/ml-dsa-will-have-to-do/
https://blog.cloudflare.com/ml-dsa-will-have-to-do/
Cloudflare Blog
Why we cannot wait for better post-quantum signature algorithms
NIST is advancing nine new post-quantum signature algorithms as potential candidates for future standardization. We take a closer look at all of them, and argue that while they are in the works and show great potential, we should use ML-DSA for now — the…
❤2
Meet Egeyar Özlen Saiu, our Lead Protocol Engineer.
Fun fact: the world's most widely used compiler and linker include code she wrote.
Egeyar has spent more than 9yrs building the lower layers of distributed systems, with a focus on consensus protocols and applied cryptography.
Her path to QMS:
→ Core consensus engineering at DFINITY during the design and launch of the Internet Computer
→ Led the development of a distributed secret-management and disaster-recovery system at Lit Protocol
→ Now implementing and hardening QMS’s novel consensus and finality layers
Egeyar joined us in March, and we're truly happy to have her on the team!
Original Tweet
X | LinkedIn | Medium | Docs
Fun fact: the world's most widely used compiler and linker include code she wrote.
Egeyar has spent more than 9yrs building the lower layers of distributed systems, with a focus on consensus protocols and applied cryptography.
Her path to QMS:
→ Core consensus engineering at DFINITY during the design and launch of the Internet Computer
→ Led the development of a distributed secret-management and disaster-recovery system at Lit Protocol
→ Now implementing and hardening QMS’s novel consensus and finality layers
Egeyar joined us in March, and we're truly happy to have her on the team!
Original Tweet
X | LinkedIn | Medium | Docs
❤4
QMS Network Official
Meet Egeyar Özlen Saiu, our Lead Protocol Engineer. Fun fact: the world's most widely used compiler and linker include code she wrote. Egeyar has spent more than 9yrs building the lower layers of distributed systems, with a focus on consensus protocols and…
If you'd like to learn more, here’s Egeyar's LinkedIn profile: https://www.linkedin.com/in/egeyar/
❤2🔥2
Qubits needed to break RSA-2048:
2019: ~20M
2025: under 1M
2026: research claims under 100k
What happens by 2027?
Original Tweet
X | LinkedIn | Medium | Docs
2019: ~20M
2025: under 1M
2026: research claims under 100k
What happens by 2027?
Original Tweet
X | LinkedIn | Medium | Docs
👀3❤2
Think of a quantum computer as a very sensitive musical instrument that constantly slips out of tune.
Until now, engineers often had to stop the computation, retune the machine, and restart it.
Google’s latest research, published July 22, introduces an AI “technician” that listens to a machine’s error signals and adjusts it while it keeps operating.
The breakthrough: the system can detect its own hardware drift and continuously recalibrate itself during computation. This matters because useful quantum computations will eventually need to run uninterrupted for long periods.
Google demonstrated this on Willow in quantum-memory experiments. While not yet with a long, commercially useful algorithm, they’re making quantum hardware more capable of operating like reliable infrastructure.
Original Tweet
X | LinkedIn | Medium | Docs
Until now, engineers often had to stop the computation, retune the machine, and restart it.
Google’s latest research, published July 22, introduces an AI “technician” that listens to a machine’s error signals and adjusts it while it keeps operating.
The breakthrough: the system can detect its own hardware drift and continuously recalibrate itself during computation. This matters because useful quantum computations will eventually need to run uninterrupted for long periods.
Google demonstrated this on Willow in quantum-memory experiments. While not yet with a long, commercially useful algorithm, they’re making quantum hardware more capable of operating like reliable infrastructure.
Original Tweet
X | LinkedIn | Medium | Docs
❤5
"Quantum doesn’t matter yet. The machines aren’t here."
That misses how the threat works.
For encrypted data, the risk is Harvest Now, Decrypt Later: capture ciphertext today, decrypt it when the hardware arrives.
On blockchains, transaction histories, signatures, and exposed public keys remain in a permanent public archive. The harvesting is already done on the ledger.
Replacing vulnerable software with quantum-resistant versions is complicated and takes time. That's another reason we need to act before quantum computers are here.
Original Tweet
X | LinkedIn | Medium | Docs
That misses how the threat works.
For encrypted data, the risk is Harvest Now, Decrypt Later: capture ciphertext today, decrypt it when the hardware arrives.
On blockchains, transaction histories, signatures, and exposed public keys remain in a permanent public archive. The harvesting is already done on the ledger.
Replacing vulnerable software with quantum-resistant versions is complicated and takes time. That's another reason we need to act before quantum computers are here.
Original Tweet
X | LinkedIn | Medium | Docs
❤2👍2
This media is not supported in your browser
VIEW IN TELEGRAM
1️⃣ BlackRock, Fidelity, and Coinbase are now paying for Bitcoin's quantum migration.
On 23 July, nine firms launched the Bitcoin Security Consortium: BlackRock, Fidelity Digital Assets, Coinbase, Strategy, Block, Blockstream, Anchorage Digital, ARK Invest, and Galaxy.
$15M over three years for Bitcoin security researchers and open-source developers. Post-quantum preparation is a named focus. Each member funds independently, and the group takes no position on protocol changes.
Migration on a live chain is a collective-action problem. It moves when the biggest holders start writing checks. Even then, the money funds research, nobody can buy a protocol change.
2️⃣ The same day, Coinbase published its post-quantum custody plan: a PQ successor to the key management system securing roughly 99.9% of the assets it custodies, plus a quantum-safe signing pipeline (secure enclaves + threshold cryptography) due within a year.
Custody can re-engineer itself in a year. The settlement layer underneath needs consensus and years. That asymmetry is the retrofit problem in one picture.
QMS is built around this assumption: the next generation of blockchain infrastructure should be quantum-resistant by design and capable of turning network compute into useful work.
Original Tweet
X | LinkedIn | Medium | Docs
On 23 July, nine firms launched the Bitcoin Security Consortium: BlackRock, Fidelity Digital Assets, Coinbase, Strategy, Block, Blockstream, Anchorage Digital, ARK Invest, and Galaxy.
$15M over three years for Bitcoin security researchers and open-source developers. Post-quantum preparation is a named focus. Each member funds independently, and the group takes no position on protocol changes.
Migration on a live chain is a collective-action problem. It moves when the biggest holders start writing checks. Even then, the money funds research, nobody can buy a protocol change.
2️⃣ The same day, Coinbase published its post-quantum custody plan: a PQ successor to the key management system securing roughly 99.9% of the assets it custodies, plus a quantum-safe signing pipeline (secure enclaves + threshold cryptography) due within a year.
Custody can re-engineer itself in a year. The settlement layer underneath needs consensus and years. That asymmetry is the retrofit problem in one picture.
QMS is built around this assumption: the next generation of blockchain infrastructure should be quantum-resistant by design and capable of turning network compute into useful work.
Original Tweet
X | LinkedIn | Medium | Docs
🔥3❤2