Feat/gauge registry #21
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Using a maxsize of MAX_UINT256 raises an error, setting MAX_INT128 (2 ** 127 -1), seems like a decent upper limit regardless
Updates the factory address in storage
skellet0r
force-pushed
the
feat/gauge-registry
branch
from
d1b5592 to
54de8c5
Compare
|
Need to add |
Useful for cacheing data off-chain
assert last_updated time updates
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Gauge registry for tracking gauges deployed via the new curve factory.
Allows for gauges to auto-register themselves on initialization, given that they are minimal proxies for the gauge implementation which the Factory has in storage.
Features: