lightninglabs / lightninglabs/taproot-assets
mssmt: audit SMT leaf/branch hash binding
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 525
- Forks
- 150
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
We should re-examine what we hash into a given branch/leaf to bubble up into the tree.
See section 5 of this paper: https://eprint.iacr.org/2016/683
If we deem that the specified attacks apply, then we may also start to encode information such as the depth or index of the leaf. It may also turn out that our sum usage its enough.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with section 5 of the linked paper, then trace the current leaf and branch hash binding in the mssmt implementation. Determine whether the described attacks apply and whether sum usage is sufficient. Done means reaching a decision on binding depth or index information, or documenting why no additional encoding is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100