PQC output type discussion

The discussion highlights several key insights into the adoption of taproot, particularly its implementation and reception in different contexts. Taproot's adoption timeframe for fee-driven scenarios, especially for n-of-n multisignature arrangements, has been relatively short, approximately six months, and is still pending for k-of-n configurations. This period coincides with historically low fee levels, which might have influenced the adoption rate. The complexity increases when considering multisig situations as opposed to single-signature setups, which are somewhat simpler.

There appears to be minimal impact from the prisoner's dilemma on the adoption of new Bitcoin address formats such as P2TR. The willingness of senders to use P2WSH, which has a similar cost per output to P2TR, suggests that the issue may lie more with the receivers' hesitation. Receivers may prefer not to switch output types between transactions for change and receipts, possibly due to the perceived insufficient benefits or unappealing potential fee savings offered by P2TR addresses.

Additionally, the conversation touches upon the technical aspects of blockchain management and node anonymity. There is an expressed need for high chances of collision among nodes, as this forms a basis for anonymity. Such collisions imply that changing a node's number post-selection is impractical without storing the entire blockchain, which would be counterproductive. Technical suggestions include the introduction of new peer-to-peer messaging protocols for efficient block chunking and potentially setting a limit on individual transactions to manage the amount of post-quantum signature data, which could be capped at 100kB.

Moreover, the idea of imposing a general transaction limit based on serialized size or abstractly as a weight limit is considered. This could facilitate verifiable chunking of blocks, ensuring that transactions within a specific range, along with their corresponding Merkle paths, can be efficiently processed and confirmed. This approach might not only aid in optimizing block templates but also enhance overall network performance and security.