-
Notifications
You must be signed in to change notification settings - Fork 71
feat(v1.0.0): merkle #393
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
Open
legion2002
wants to merge
6
commits into
v1.0.0
Choose a base branch
from
tanishk/v1.0.0-merkle
base: v1.0.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
feat(v1.0.0): merkle #393
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
6dd67d0
feat: fix and simplify multichain design (#327)
howydev 4cde57e
feat: remove intent struct (#365)
howydev 9b5b848
feat: native merkle sig verification in Account
legion2002 40e6a08
chore: fmt
legion2002 61b3720
chore: unify merkle sig flow for orchestrator multi chain intents
legion2002 52c4d32
chore: bump contract versions due to bytecode changes - Contracts upd…
actions-user 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 hidden or 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 hidden or 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
Oops, something went wrong.
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.
continuing convo from this: https://github.com/ithacaxyz/account/pull/388/files#r2387828490
I think the outer one is entirely ignored, so theres no security issue
return _verifyMerkleSig(digest, signature)-> this overrides thekeyHash = ...parsed in the top level call frameOn prehash - IIUC there should only be 1
prehashthat's set, in either the outer or inner wrapper. There's a difference between the 2 since the digest has to be in the merkle tree, so which one we want to set depends whether the merkle leaf issha-ed or not. I don't know which one would beshaed in practice, but the other one would probably be redundantThere 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.
Something that I just thought to check was whether we'll run into issues around second preimage attacks
I don't see anything thats obvious so far, bringing it up just in case im missing something