fixups

Author: instagibbs

bip-templatehash-csfs-ik.md

@@ -1,7 +1,7 @@
 ```
   BIP: ?
   Layer: Consensus (soft fork)
-  Title: OP_TEMPLATEHASH + OP_CHECKSIGFROMSTACK + OP_INTERNALKEY
+  Title: Next-transaction and Rebindable Signatures
   Author: Gregory Sanders <[email protected]>
           Antoine Poinsot <[email protected]>
           Steven Roose <[email protected]>
@@ -16,7 +16,7 @@
 ## Abstract
 
 This document proposes bundling three new operations for [Tapscript][tapscript-bip]:
-[`OP_TEMPLATEHASH`][templatehash-bip], [`OP_CHECKSIGFROMSTACK`][csfs-bip], and [`OP_INTERNALKEY`][internalkey-bip].
+[`OP_TEMPLATEHASH`][templatehash-bip], [`BIP348 OP_CHECKSIGFROMSTACK`][csfs-bip], and [`BIP349 OP_INTERNALKEY`][internalkey-bip].
 
 These minimal operations introduce modular functionalities which improve existing second layer protocols and make new
 ones possible through plausible interactivity requirements.
@@ -25,9 +25,9 @@ ones possible through plausible interactivity requirements.
 
 The three proposed operations are simple, well-understood, and enable powerful new capabilities while minimizing the
 risk of surprising behavior or unintended applications. They improve existing, well-studied protocols and make promising
-new ones possible, while minimizing the risk of surprising behavior or unintended or undesirable applications.
+new ones possible.
 
-`OP_TEMPLATEHASH` enables commitment to the transaction spending an output. `OP_CHECKSIGFROMSTACK` enables
+`OP_TEMPLATEHASH` enables committing to the transaction spending an output. `OP_CHECKSIGFROMSTACK` enables
 [BIP340][schnorr-bip] signature verification of arbitrary messages. `OP_INTERNALKEY` allows to push the
 [Taproot][taproot-bip] internal key on the stack.
 
@@ -52,7 +52,7 @@ signatures.
 ## Rationale
 
 This proposal seeks to extend Bitcoin's scripting capabilities in areas that are useful to proven approaches to scaling
-Bitcoin payments, while minimizing the risk of enabling surprising or unwanted usage. The operations proposed to achieve
+Bitcoin payments. The operations proposed to achieve
 these capabilities are contained within the more modern and well-studied Tapscript context. They are simple, composable
 and unlikely to be made obsolete by future extensions to Bitcoin Script. They build upon existing operations and
 therefore present a minimal cost to validation and implementation complexity.
@@ -70,6 +70,10 @@ substantially improve existing ones, this proposal favours the minimal approach.
   signatures usage more efficient;
 - it prevents surprising interactions with programs in a transaction input's `scriptSig`.
 
+## Implementation
+
+[`OP_TEMPLATEHASH`][templatehash-bip], [`BIP348 OP_CHECKSIGFROMSTACK`][csfs-bip], and [`BIP349 OP_INTERNALKEY`][internalkey-bip] implemented as specified in their corresponding documents.
+
 ## Backward compatibility
 
 This document proposes to give meaning to three Tapscript `OP_SUCCESS` operations. The presence of an `OP_SUCCESS` in a

bip-templatehash.md

@@ -117,6 +117,10 @@ rules: there is no block that is valid under the rules proposed in this BIP but
 rules. As a consequence these changes are backward-compatible with non-upgraded node software. That said, the authors
 strongly encourage node operators to upgrade in order to fully validate all consensus rules.
 
+## Implementation
+
+* https://github.com/instagibbs/bitcoin/tree/2025-07-op_templatehash
+
 ## Test Vectors
 
 For development and testing purposes, we provide a [collection of test vectors](bip-templatehash/test_vectors). The test