-
Notifications
You must be signed in to change notification settings - Fork 29
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(client): l1<>l2 messaging crate #220
feat(client): l1<>l2 messaging crate #220
Conversation
Copying back this comment from Mohiit |
and this one from cchudant |
…ate test from eth to launch anvil from code
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.
this is cool! I didn't expect you to handle the niche message cancellation feature
I dont get the nonce part, why are you storing them in the db?
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.
looks good to me 🥳
Pull Request type
What is the current behavior?
Resolves: #204
What is the new behavior?
Does this introduce a breaking change?
No
Usefull information
I reopened this pr because there was an issue with our old fork. This one is from a fresh one.
A few notes on the current design:
Current Progress
Overall Workflow
Specific case to handle
Tests
E2E test 1
E2E test 2
E2E test 3