-
Notifications
You must be signed in to change notification settings - Fork 85
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
Curve Pool Booster for L2 #2389
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2389 +/- ##
==========================================
- Coverage 50.96% 50.60% -0.36%
==========================================
Files 92 93 +1
Lines 4529 4592 +63
Branches 1203 1223 +20
==========================================
+ Hits 2308 2324 +16
- Misses 2217 2264 +47
Partials 4 4 ☔ View full report in Codecov by Sentry. |
/// @title CurvePoolBooster | ||
/// @author Origin Protocol | ||
/// @notice Contract to manage interactions with VotemarketV2 for a dedicated Curve pool/gauge. | ||
contract CurvePoolBoosterDirect is Initializable, Strategizable { |
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.
nit: we should probably move these contracts into their own directories. They're not Vault strategies, so don't really belong here
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.
Any suggestion for the the directory name?
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 ain't sure. But since we are naming the contracts "PoolBooster", we can probably use the same as the name of the directory as well
Description
The current
CurvePoolBooster
(CPB) has been deployed and works for gauge that are on Ethereum mainnet. AsVotemarket
is only deployed on L2s, CPB used theCampaignRemoteManager
contract to interact withVotemarket
on L2 and create/manage bribes.But for gauge that are already on L2, it will be more efficient to directly use the Votemarket on L2, no need to bridge message!
So this implementation of CPB is a simplified version that directly interact with Votemarket.
Code Change Checklist
To be completed before internal review begins:
Internal review: