Skip to content

BIP 448 implementation (0.32.x)#2

Open
darosior wants to merge 4 commits into
bip448:0.32.xfrom
darosior:bip448-0.32.4
Open

BIP 448 implementation (0.32.x)#2
darosior wants to merge 4 commits into
bip448:0.32.xfrom
darosior:bip448-0.32.4

Conversation

@darosior

@darosior darosior commented Jun 29, 2026

Copy link
Copy Markdown

This is #1 ported to rust-bitcoin 0.32.101, which is the version currently used by LDK, with some slight modifications. My understanding is that LDK/BDK will stay on 0.32 for the time being, so it's probably worth maintaining a branch against this version.

w0xlt and others added 4 commits June 29, 2026 15:27
Expose names for the BIP348, BIP349, and BIP446 opcode bytes
used by Bitcoin Inquisition signet. They remain aliases for
the current OP_SUCCESSx bytes so script construction can use
the proposal names without changing TapScript classification.

Add coverage for the alias byte values, builder output, and
current OP_SUCCESSx classification behavior.
Add a TemplateHash tagged-hash type and SighashCache helpers
for computing the BIP446 OP_TEMPLATEHASH message used by Bitcoin
Inquisition signet scripts. The helper commits to version,
lock time, sequences, outputs, input index, and this
input's annex data while intentionally leaving prevouts and
spent amounts out of scope.

Share the BIP341 annex hashing logic, add raw BIP340 signing helpers
for CHECKSIGFROMSTACK use, and cover the behavior with local BIP446 vectors
plus length and input-index error tests.
Add examples that build the common
OP_TEMPLATEHASH OP_INTERNALKEY OP_CHECKSIGFROMSTACK Taproot script
and sign a TemplateHash for a script-spend witness. These examples
demonstrate the local construction and signing API without
implying consensus validation.

Document the intended Bitcoin Inquisition signet scope,
the non-consensus limitations, the TemplateHash commitments, and
the raw CSFS signing convention.
@darosior

Copy link
Copy Markdown
Author

Rebased on top of rust-bitcoin 0.32.101

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants