-
Notifications
You must be signed in to change notification settings - Fork 8
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
Emit l2BlockNumber in the Resolved event #226
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## develop #226 +/- ##
========================================
Coverage 41.31% 41.31%
========================================
Files 74 74
Lines 5001 5001
Branches 785 785
========================================
Hits 2066 2066
Misses 2828 2828
Partials 107 107
Flags with carried forward coverage won't be shown. Click here to find out more. |
The new |
I will try to push this to the upstream. |
I have followed their contribution rule and created a Github issue for the discussion. ethereum-optimism#11409 |
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.
LGTM
📋 Add associated issues, tickets, docs URL here.
Overview
Describe what your Pull Request is about in a few sentences.
To reduce the number of RPC calls needed to retrieve the
l2BlockNumber
submitted with the state root in the game, I have added thel2BlockNumber
and rootClaim to the event.This allows us to retrieve all necessary information for the withdrawal from our subgraph rather than making RPC calls to get the
l2BlockNumber
.Here is how the current implementation works: https://github.com/bobanetwork/graphql-utils/pull/9/files Basically, we need to perform a for loop to find the game where its
l2BlockNumber
is larger than the target value, and the previous game’sl2BlockNumber
is smaller than the target value.Changes
Describe your changes and implementation choices. More details make PRs easier to review.
Testing
Describe how to test your new feature/bug fix and if possible, a step by step guide on how to demo this.
The tests are added