Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Update Sparse Merkle Tree leaf value to be hashed #6900

Closed
Tracked by #6554
ishantiw opened this issue Nov 12, 2021 · 0 comments · Fixed by #6954
Closed
Tracked by #6554

Update Sparse Merkle Tree leaf value to be hashed #6900

ishantiw opened this issue Nov 12, 2021 · 0 comments · Fixed by #6954
Assignees
@shuse2
Labels
elements/tree type: bug unplanned
Milestone
Sprint 58

Comments

@ishantiw
Copy link
Contributor

ishantiw commented Nov 12, 2021 •
edited by shuse2
Loading

Description

Stored value should be hashed as https://github.com/LiskHQ/lips/blob/main/proposals/lip-0040.md#specification specifies.

When updating the value

value is not hashed before setting to the smt

Acceptance Criteria

  • Ensure stored value is hashed
@ishantiw ishantiw mentioned this issue Nov 12, 2021
Closed
@sridharmeganathan sridharmeganathan mentioned this issue Nov 19, 2021
Closed
36 tasks
@shuse2 shuse2 changed the title Update Sparse Merkle Tree leaf value to only contain leaf prefix Update Sparse Merkle Tree leaf value should be hashed Dec 1, 2021
@shuse2 shuse2 self-assigned this Dec 1, 2021
@shuse2 shuse2 changed the title Update Sparse Merkle Tree leaf value should be hashed Update Sparse Merkle Tree leaf value to be hashed Dec 1, 2021
@shuse2 shuse2 added this to the Sprint 58 milestone Dec 1, 2021
@shuse2 shuse2 mentioned this issue Dec 2, 2021
Merged
@shuse2 shuse2 closed this as completed Dec 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@shuse2 shuse2

Labels
elements/tree type: bug unplanned
Projects
None yet
Milestone
Sprint 58
Development

Successfully merging a pull request may close this issue.

Fix SMT leaf value to be hashed before update - Closes 6900 LiskArchive/lisk-sdk
2 participants
@shuse2 @ishantiw