rust-bitcoin / rust-bitcoin/rust-bitcoin
[33.0-beta0] | ScriptBuf Tag Types + Rust Miniscript Integration
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 88
Description
Problem
Currently I am attempting a refactor of rust-miniscript library to enable BIP-0390 musig descriptor support.
Schnorr Pk agg is not a part of rust-bitcoin 31.x FFI bindings in libsecp256k1 this leads to a problem. Updating to version 33.0-beta0 which supports these bindings uses a new tagged version of ScriptBuf which is hard to refactor into locations like this ... RustMsiniscript Bare
Where the above function does not fit the model of any of the available tags this is because the above function should return a script buffer that can be used either as a ScriptSig element or a WitnessScript which each have their own tags but not a mixed tag that represent multiple locations for use.
Thanks in advance,
PortlandHODL
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 with rust-miniscript's src/descriptor/bare.rs and compare its ScriptBuf use with rust-bitcoin's primitives/src/script/mod.rs and primitives/src/script/tag.rs. Read the linked MuSig FFI context to understand the 33.0-beta0 constraint and determine how the bare descriptor output should represent both ScriptSig and WitnessScript uses. Done means an agreed ScriptBuf tagging approach that supports this integration without misrepresenting the script's valid contexts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100