1
0
mirror of https://github.com/bitcoin/bips.git synced 2025-05-12 12:03:29 +00:00

better word

Greg Tonoski 2024-10-27 21:10:30 +01:00
parent 90095e3f6e
commit 9a57a86f59

@ -4,4 +4,4 @@ There is the should-type requirement of hardcoded constant "TapTweak" in derivat
1. avoidance/minimisation of a number of hardcoded values (in accordance with commonly accepted best practices); 1. avoidance/minimisation of a number of hardcoded values (in accordance with commonly accepted best practices);
2. keeping requirements specification consice and of high relevance to changes in protocol and consensus rules. 2. keeping requirements specification consice and of high relevance to changes in protocol and consensus rules.
Also it may be worth adding an explanatory/warning note that sometimes the described attack in MSDL-pop scenario is not averted by the proposed "TapTweak" mechanism which is excluded for TapTweaks (t) that exceed SECP256K1_ORDER (regarding the point 23 in Rationale section. i.e. https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki#cite_ref-23-0). Also it may be worth adding an explanatory/warning note that sometimes the described attack in MSDL-pop scenario is not prevented by the proposed "TapTweak" mechanism which is excluded for TapTweaks (t) that exceed SECP256K1_ORDER (regarding the point 23 in Rationale section. i.e. https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki#cite_ref-23-0).