Segwit commitment to post-quantum witness data?

The concept of enhancing blockchain technology to accommodate post-quantum cryptography involves several innovative adjustments to the current system. One proposed method is to increase the block size to include an extension block area specifically for post-quantum signature data. This area could also house the additional overhead associated with ECC spends, such as those used in P2MR or P2MR+PKR transactions. By structuring it so that the initial bytes (32B or 64B per input) are free, this could potentially align the economic viability of these ECC paths with more commonly used paths like p2wpkh and p2tr. The integration of another witness area seems technically feasible and might become necessary as the usage of post-quantum cryptographic (PQC) schemes expands.

However, implementing such changes introduces complexities. For instance, creating a new transaction identifier (pqwtxid) that includes both the pqdata and the traditional segwit data would require significant updates to mining and network infrastructure. This includes the need for a new block commitment in the coinbase to these pqwtxids and potentially a pqwtxid relay feature, similar to the BIP339 wtxid relay. Moreover, adding these elements necessitates modifications within the Peer-to-Peer (P2P) logic to handle three types of identifiers instead of two, complicating backward compatibility with older network nodes and protocols.

An alternative solution to mitigate some of these challenges involves placing a commitment to the pqdata within the segwit area of an input, maintaining the wtxid as the sole transaction identifier. This approach could avoid altering existing transaction identification mechanisms significantly while still integrating the necessary post-quantum data. Although this method would increase storage and bandwidth requirements due to the additional 32 bytes required for pqdata commitment, it's possible to manage this through node-specific optimizations or P2P protocol negotiations without broadly impacting the deployment of the pqdata feature itself. Additionally, reallocating all witness data to the pqdata area for certain output types could allow for more flexible costing, potentially starting with a negative cost to offset the added pqdata commitment burden.

These considerations highlight the delicate balance between advancing blockchain technology to support emerging cryptographic standards and maintaining a seamless and efficient network operation. Each proposed change carries potential benefits and drawbacks, requiring careful evaluation and possibly innovative problem-solving to implement effectively.