aboutsummaryrefslogtreecommitdiff
path: root/src/consensus/merkle.cpp
diff options
context:
space:
mode:
author4d55397500 <[email protected]>2020-03-18 10:34:53 -0700
committerGitHub <[email protected]>2020-03-18 10:34:53 -0700
commit5b59a19731827398aa32754d1f327178247d3199 (patch)
tree90cc0c5135c14c13372143fd058f6a2fe109977d /src/consensus/merkle.cpp
parentMerge #18371: test: use fs namespace in dbwrapper unicodepath test (diff)
downloaddiscoin-5b59a19731827398aa32754d1f327178247d3199.tar.xz
discoin-5b59a19731827398aa32754d1f327178247d3199.zip
Update merkle.cpp
Change comment from `The reason is that if the number of hashes in the list at a given time is odd`, to ` The reason is that if the number of hashes in the list at a given level is odd` (to be a bit more precise)
Diffstat (limited to 'src/consensus/merkle.cpp')
-rw-r--r--src/consensus/merkle.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/consensus/merkle.cpp b/src/consensus/merkle.cpp
index 843985e54..241cc316a 100644
--- a/src/consensus/merkle.cpp
+++ b/src/consensus/merkle.cpp
@@ -10,7 +10,7 @@
that the following merkle tree algorithm has a serious flaw related to
duplicate txids, resulting in a vulnerability (CVE-2012-2459).
- The reason is that if the number of hashes in the list at a given time
+ The reason is that if the number of hashes in the list at a given level
is odd, the last one is duplicated before computing the next level (which
is unusual in Merkle trees). This results in certain sequences of
transactions leading to the same merkle root. For example, these two