Skip to content

Commit 35fbc54

Browse files
committed
chore: address comment
1 parent 908fa6b commit 35fbc54

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

docs/SMT.md

+9-8
Original file line numberDiff line numberDiff line change
@@ -384,14 +384,15 @@ of the trie.
384384

385385
NB: If the hash provided to the `ClosestProof` function is known prior to the
386386
tree being filled and closed there is the possibility of placing a leaf where
387-
the hash will lead. If used **as intended** the hash provided should **not** be
388-
known prior to calling the method and the tree should not be updateable after
389-
the fact. If the hash were known prior to closing the tree and not inserting
390-
into it anymore a leaf could be inserted into the tree in such a way that it
391-
would always be produced from the `ClosestProof` method (as it is deterministic).
392-
When used as a pseudo-random challenge this is a vulnerability and if used in
393-
this manner care should be taken when and how the hash used in the proof is
394-
decided upon and when it is provided to the caller of the method.
387+
the hash will lead. If used **as intended**, the hash provided should **not** be
388+
known prior to calling the method; therefore, the tree should not be updateable
389+
after the fact. If the hash were known by the caller of the method, after the
390+
last update but prior to closing the trie a leaf could be inserted into the tree
391+
in such a way that it would always be produced from the `ClosestProof` method
392+
(as it is deterministic). When used as a pseudo-random challenge this is a
393+
vulnerability and, if used in this manner, care should be taken around how the
394+
hash used in the proof is decided upon and when it is provided to the caller of
395+
the method.
395396

396397
### Compression
397398

0 commit comments

Comments
 (0)