-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: nested polkadot fetch #4006
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
49772ec
feat: nested polkadot fetch
dandanlen a6f4c62
fix: nested address generation + tests + fix impl
dandanlen a69a918
fix: clippy
dandanlen 258ccea
test: nesting of equivalent values
dandanlen 03db7c7
Merge branch 'main' into feat/nested-polkadot-fetch
dandanlen 2302c55
Merge branch 'main' into feat/nested-polkadot-fetch
dandanlen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, we should check whether a derivative address can both be used as a valid deposit address AND be used to generate further derivative addresses in a new layer. This is because this implementation would lead to such a case for example the channel ids [0x00,0x00,0x02,0x05] and [0x00,0xAA,0x02,0x05] where AA could be any byte.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Been thinking about this a bit more. I think what it boils down to is whether these are different:
[0x01]
(resulting in a call with offset 0x01).[0x01, 0x00]
(resulting in an offset 0x01 wrapped in an offset 0x00).I think the answer is yes, since when there are two bytes, there are two layers of hashing. So it's the difference between (simplified)
hash(0x00, hash(X, root))
vshash(X, root)
. I'll write short test.