Bitcoin's plan to survive #QuantumComputers has reached one of the oldest disagreements in the protocol: how big a block is allowed to get.
The problem they're hitting (repeatedly) is that post-quantum signatures are REALLY big.
On the Delving Bitcoin forum, developers spent late July and August comparing four ways to build a quantum-resistant output type, under names that admittedly mean nothing outside the protocol:
P2MR, P2TRv2, P2TRH and P2QR
On a Bitcoin Core regtest run, developer jeanpablojp clocked a P2MR two-leaf spend at 513 weight units against 545 for the equivalent Taproot script path, with the design needing only about 96 lines on top of the existing Taproot code.
Developer conduition points out that hash-based schemes would need an 8x jump in block size. Each year, the blockchain would grow by TERABYTES - rather than the hundreds of gigabytes it currently grows by.
That is a lot of disk space to ask of anyone running a full node.
Pieter Wuille, one of #Bitcoin's most senior developers, is less worried about the storage footprint. His point is that storage has always grown faster than the chain, and the real limit is validation bandwidth at the tip - where every node has to validate new blocks as fast as they arrive.
On the positive side, the conversation has at least moved on to costing the #Quantum migration and choosing an approach. It's a WAY more concrete conversation than the usual ⌛quantum-will-break-Bitcoin ⌛ coverage.