Public key recovery for EC leaves in P2MR (BIP-360)

The discussion revolves around the complexities and technical challenges in cryptocurrency technology, particularly addressing the implementation of a new BIP340 variant. This variant is noteworthy for its inclusion of a keyhash-commitment with recovery features, which, despite adding complexity, is considered valuable for the protection and efficiency it brings to the system. The abandonment of batch validation highlights a shift in priority, focusing more on security enhancements rather than features that have not been integrated, such as batch verification which remains unmerged in the core even seven years after the deployment of P2TR.

The conversation also touches on the implications of not solving certain cryptographic problems before potential critical events, referred to as Q-day. If unresolved, these issues could lead to nowhere safe to send money, underscoring the urgency and necessity of these developments. In contrast, existing implementations prior to Q-day would see an increase in the size of EC witnesses, approximately 35 bytes larger, indicating a trade-off between current inefficiencies and future security needs.

Moreover, there’s a critique regarding the slow progress on merging significant updates like batch verification into the core codebase, as evidenced by a stagnant pull request (The PR) that has not seen activity for six months. This stagnation raises questions about the prioritization of features versus security within the community, especially since there doesn't seem to be a rush to operationalize these features. Lastly, the email queries the practical use cases of posting bare public keys in the ScriptPubKey (SPK), suggesting a gap in common practical applications or examples within the current frameworks.