Updated Comments:BIP 0341 (markdown)

Greg Tonoski committed 2024-10-23 16:19:35 +02:00
1 parent ce271e7b28
commit 4eb501fe5f
1 file changed
+1 -1
+1 -1
@@ -2,4 +2,4 @@
There is the should-type requirement of hardcoded constant "TapTweak" in derivation of a private-public key pair used in a spending path that excludes scripts in the BIP-0341 specification. I think that the requirement is unnecessary or too restrictive. I would suggest replacing the requirement with a cautionary description and leaving an option to tweak a key to an owner's discretion instead. Reasons:
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.
2. keeping requirements specification consice and of high relevance to changes in protocol and consensus rules.