-
Notifications
You must be signed in to change notification settings - Fork 147
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
fix: add gns and staking counter part addresses when configuring bridge #889
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #889 +/- ##
=======================================
Coverage 92.69% 92.69%
=======================================
Files 46 46
Lines 2369 2369
Branches 426 426
=======================================
Hits 2196 2196
Misses 173 173
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Going to be THAT guy, can we change this PR to use #sdk as the base branch? |
647d4cd
to
e4317e6
Compare
fix: add gns and staking counter part addresses when configuring bridge
🚨 Report Summary
For more details view the full report in OpenZeppelin Code Inspector |
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, might need to rebase
e4317e6
to
7596581
Compare
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.
I wonder if we should just delete the cli
folder lol
Signed-off-by: Tomás Migone <[email protected]>
Added missing configs on bridge setup, included checks in e2e tests.
counterpartGNSAddress
on L1 and L2counterpartStakingAddress
on L1 and L2L1GNS
andL1Staking
toL1GraphTokenGateway.callhookAllowlist