bitcoindevkit / bitcoindevkit/bdk-cli
Add taproot privacy optimisations in policy compiler
- Vorherrschende Sprache
- Rust
- Sterne
- 141
- Forks
- 99
- Ø Merge
- 6 T. 14 Min.
- Gemergte PRs (30 T.)
- 1
Beschreibung
**Describe the enhancement**
`bdk-cli compile --type tr "$POL"` currently only calls `compile` and manually wraps the result into a single taproot leaf, instead of using `compile_tr` from rust-miniscript that splits disjunctions into separate leaves and Huffman-optimises the tree. Using `compile_tr` would be a good compromise, though `compile_tr_private_experimental` exists and goes one step further in privacy optimisation.
**Use case**
When compiling a disjunctive policy to a taproot descriptor, each spending condition should ideally be its own leaf so that only the used path is revealed on-chain. Currently all conditions are bundled into a single leaf, missing the privacy benefits of taproot's script tree.
**Additional context**
The following shows the output of all three rust-miniscript functions for reference:
**Example 1:** `or(pk(A),pk(B))`
```
compile:
or_b(pk(A),s:pk(B))
compile_tr:
internal key : B
tap tree leaves (1 total):
depth=0 script=pk(A)
compile_tr_private_experimental:
internal key : B
tap tree leaves (1 total):
depth=0 script=pk(A)
```
**Example 2:** `thresh(1,pk(A),pk(B),pk(C))`
```
compile:
multi_a(1,A,B,C)
compile_tr:
internal key : C
tap tree leaves (2 total):
depth=1 script=pk(B)
depth=1 script=pk(A)
compile_tr_private_experimental:
internal key : C
tap tree leaves (2 total):
depth=1 script=pk(B)
depth=1 script=pk(A)
```
**Example 3:** `thresh(2,pk(A),pk(B),pk(C))`
```
compile:
multi_a(2,A,B,C)
compile_tr:
internal key : UNSPENDABLE
tap tree leaves (1 total):
depth=0 script=multi_a(2,A,B,C)
compile_tr_private_experimental:
internal key : UNSPENDABLE
tap tree leaves (3 total):
depth=1 script=and_v(v:pk(A),pk(B))
depth=2 script=and_v(v:pk(B),pk(C))
depth=2 script=and_v(v:pk(A),pk(C))
```
Beitragsleitfaden
Rechercherichtung
Verfolge den Einstiegspunkt `bdk-cli compile --type tr` und prüfe den aktuellen `compile`-Aufruf sowie das manuelle Wrapping eines einzelnen Leafs. Vergleiche diesen Pfad mit der Ausgabe von rust-miniscripts `compile_tr` für die disjunktiven und Threshold-Beispiele; als erledigt gilt die Aufgabe, wenn Taproot-Policies separate Leaves verwenden und der resultierende Baum die vorgesehene Huffman-Optimierung erhält.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- rust
- Bereich
- cli
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 55/100