mirrors/bitcoin-bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-03-13 11:09:16 +01:00
Code Issues Projects Releases Wiki Activity

fix: script spend, not key spend

Browse source 
For the key spend the script tree depth is not revealed, it is only done for script spends. This sentence makes sense only for the script spend.
This commit is contained in:
Max Hillebrand 2019-11-06 05:58:11 +01:00 • committed by Pieter Wuille
parent fe74ab65db
commit 3d97967b97
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.