-
Notifications
You must be signed in to change notification settings - Fork 617
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(contracts): lido gateway #988
Conversation
LCOV of commit
|
Storage layouts (for reference):
|
could you benchmark the gas cost of lido bridge? |
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.
Hello, thank you for all of the efforts, team 👍
Awesome work!
I want to add some input from the NEW tech wing side 🙏
Will get back to you by late Wednesday with more details; just decided to put forward major suggestions and proposals on the go to make things more agile
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.
Left the follow-up review 🙏
Please consider addressing the provided concerns if possible 👀
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #988 +/- ##
===========================================
+ Coverage 56.15% 56.45% +0.29%
===========================================
Files 145 149 +4
Lines 11014 11087 +73
===========================================
+ Hits 6185 6259 +74
+ Misses 4407 4406 -1
Partials 422 422
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
will do after rebasing with #1011 |
|
Purpose or design rationale of this PR
This PR implements the Lido L1 and L2 Gateways.
PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
Deployment tag versioning
Has
tag
incommon/version.go
been updated or have you addedbump-version
label to this PR?Breaking change label
Does this PR have the
breaking-change
label?