From 4eb501fe5ff533f3d48b4fa85ce57b760bd97988 Mon Sep 17 00:00:00 2001
From: Greg Tonoski <111286121+GregTonoski@users.noreply.github.com>
Date: Wed, 23 Oct 2024 16:19:35 +0200
Subject: [PATCH] Updated Comments:BIP 0341 (markdown)

---
 Comments:BIP-0341.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Comments:BIP-0341.md b/Comments:BIP-0341.md
index b82ddc8..5dfc922 100644
--- a/Comments:BIP-0341.md
+++ b/Comments:BIP-0341.md
@@ -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.
\ No newline at end of file
+2. keeping requirements specification consice and of high relevance to changes in protocol and consensus rules.
\ No newline at end of file