-
Notifications
You must be signed in to change notification settings - Fork 103
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
GSM L2 #449
base: main
Are you sure you want to change the base?
GSM L2 #449
Conversation
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 d switch back to normal string errors, to minimize diff between GsmL2 and Gsm.
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.
in my ideal world, we'd use a newer solidity with custom errors to save on deployment size and gas on reverts. thought this would save on some deployment size and prepare this for the future but not a deal breaker it can be strings.
* @dev Updates Liquidity Provider | ||
* @param liquidityProvider The address of the liquidty provider for the GSM | ||
*/ | ||
function _updateLiquidityProvider(address liquidityProvider) internal { |
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.
does it make sense to use a role for this instead?
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 thinking only one facilitator can provide liquidity to the GSM so that's why I went with one address but don't have a strong opinion on it
Changelog
Add GSML2 implementation where GHO is provided to the GSM and then transfered in/out instead of mint/burn.
Update tests for GSML2.