highperfocused/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-04-23 06:54:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #126 from MaxHillebrand/patch-1

Browse Source 
fix: script spend, not key spend reveals tree depth
This commit is contained in:
Pieter Wuille 2019-11-06 07:44:00 -08:00 committed by GitHub
commit 73ade2d61b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
bip-taproot.mediawiki
View File

@ -268,7 +268,7 @@ A key path spend could be a "normal" payment from a single- or multi-signature w
A script path spend leaks that there is a script path and that the key path was not applicable - for example because the involved parties failed to reach agreement.
Moreover, the depth of a script in the Merkle root leaks information including the minimum depth of the tree, which suggests specific wallet software that created the output and helps clustering.
Therefore, the privacy of key spends can be improved by deviating from the optimal tree determined by the probability distribution over the leaves.
Therefore, the privacy of script spends can be improved by deviating from the optimal tree determined by the probability distribution over the leaves.
Just like other existing output types, taproot outputs should never reuse keys.
This does not only apply to the particular leaf that was used to spend an output but to all leaves committed to in the output.