Introduce BIN-2026-0001 for BIP-446 OP_TEMPLATEHASH#18
Open
darosior wants to merge 1 commit intobitcoin-inquisition:masterfrom
Open
Introduce BIN-2026-0001 for BIP-446 OP_TEMPLATEHASH#18darosior wants to merge 1 commit intobitcoin-inquisition:masterfrom
OP_TEMPLATEHASH#18darosior wants to merge 1 commit intobitcoin-inquisition:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This introduces a BIN for the
OP_TEMPLATEHASHproposal as drafted in bitcoin/bips#1974 and implemented in bitcoin-inquisition/bitcoin#100.The proposal dates from late 2025 but BIN-26-1 was chosen in place of BIN-25-4 since the BIP number 446 was assigned on February 6, 2026. Since the revision date should match the referenced document, i went with 26.
Since the BIP is not merged yet, we link to the PR instead of a commit hash on the author's branch, which would be much more volatile due to force pushes in addressing review comments. Once the BIP is merged, the revision will be updated to a commit hash.