diff options
| author | Max Hillebrand <30683012+MaxHillebrand@users.noreply.github.com> | 2019-11-06 05:58:11 +0100 |
|---|---|---|
| committer | Pieter Wuille <pieter.wuille@gmail.com> | 2020-01-19 14:47:33 -0800 |
| commit | 3d97967b97831dc268b39bc8b667d6aace0dc56a (patch) | |
| tree | afad53e547ba2f6ddc3e02dd193eac8c2d16a3b5 /bip-taproot.mediawiki | |
| parent | fe74ab65dbc119e75eac2c9e25812410e32c4cb0 (diff) | |
fix: script spend, not key spend
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.
Diffstat (limited to 'bip-taproot.mediawiki')
| -rw-r--r-- | bip-taproot.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-taproot.mediawiki b/bip-taproot.mediawiki index 0e27724..d408357 100644 --- a/bip-taproot.mediawiki +++ b/bip-taproot.mediawiki @@ -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. |