rust-bitcoin / rust-bitcoin/rust-miniscript
Think about how MiniscriptKey interacts with Musig keys
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 426
- Forks
- 200
- Avg merge
- 7d 17h
- Merged PRs (30d)
- 8
Description
Integrating musig2 keys with the existing API introduces a couple of new challenges:
- We currently support
Terminal::Pk(Pk)in our miniscript decoding. This means we should parsemusig(A,B,C)as a single Pk. - At the same time, we want the translation API to allow to translation of native
A,BandC.
Seems like we might to re-design some parts of the codebase to support it. cc @apoelstra
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 tracing the existing Terminal::Pk(Pk) miniscript decoding path and the translation API. Work out how musig(A,B,C) should be represented as one Pk while still allowing translation of A, B, and C; the issue is complete when this interaction has an agreed design and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100