-
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
Arbitrum bridge + rewards distribution #552
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #552 +/- ##
==========================================
+ Coverage 90.35% 91.96% +1.61%
==========================================
Files 35 44 +9
Lines 1762 2092 +330
Branches 296 361 +65
==========================================
+ Hits 1592 1924 +332
+ Misses 170 168 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
69626a9
to
6ef918b
Compare
e68ebf9
to
f91c67d
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.
Some notes and open questions.
// For some reason the call count doesn't work properly, | ||
// and each function call is counted 12 times. | ||
// Possibly related to https://github.com/defi-wonderland/smock/issues/85 ? | ||
//expect(arbSysMock.sendTxToL1).to.have.been.calledOnce |
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 was trying to investigate why this doesn't work, as it would be nice to explicitly check we only call this once...
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.
The error looks very similar to what they reported, and the number being 12 looks really fixed. I haven't used that feature from waffle yet.
e66acaf
to
0287949
Compare
I've deployed this to a new deployment on Rinkeby and I'm working on some CLI commands to configure the new contracts and interact with them, but doing this in a separate PR, see #556 |
95ba090
to
37cc956
Compare
822e1da
to
bcee887
Compare
e60da74
to
f80cad3
Compare
Deployment commands in the CLI are also updated to include an L2 deployment. Configuration and address book entries for Arbitrum are added as well.
f80cad3
to
0495b9c
Compare
We also add Goerli and Arbitrum Nitro Devnet configurations (though the CLI commands don't support Nitro yet).
Socket Security Report👍 No new dependency issues detected in pull request Socket.dev scan summary
Powered by socket.dev |
…o call drip (needs tests)
… L2 [H-03] [L-03]
Superseded by #699 so closing |
Motivation
Based on discussions that have been going on in the past few months (see this Forum discussion), it seems that there is interest in the community for scaling through a Layer 2 network. Conversations between core dev teams point towards an Arbitrum Graph devnet as the most viable first step in this direction.
This devnet would require, among other things, a way to bridge GRT from L1 into L2 and back. This bridge should be the canonical way to send GRT into Arbitrum, but it should be extensible to support any protocol-specific behavior that may be necessary, both for the initial devnet deployment and the eventual "mainnet” release. This GIP covers the specification of such bridge.
GIPs for discussions in the forum:
Changes
(Edited to add the changes from #556 and #571 as these were merged on top of this PR)