rust-bitcoin / rust-bitcoin/rust-miniscript
No predefined `Satisfier` can be used to sign the keyspend path of a Taproot output
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 426
- Forks
- 200
- Avg merge
- 7d 17h
- Merged PRs (30d)
- 8
Description
Well, the PSBT one does, but that's a lot of infrastructure.
We have an impl for HashMap<(Pk, TapLeafHash>, Signature> that will work for script-spends. But this will silently fail for keyspends, which is confusing and surprising.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the existing HashMap<Pk, TapLeafHash, Signature> Satisfier implementation and the PSBT Satisfier referenced in the issue. Determine how keyspends differ from script-spends; done means a predefined Satisfier can sign the Taproot keyspend path without requiring the full PSBT infrastructure, while retaining script-spend support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, cryptography
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100