-
Notifications
You must be signed in to change notification settings - Fork 12
Charm Vault manager update #217
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
Conversation
Charm Vault manager update
🚨 Report Summary
For more details view the full report in OpenZeppelin Code Inspector |
d27a583 to
9e39bda
Compare
|
|
||
| VAULT = vault_; | ||
| POOL = vault_.pool(); | ||
| USDC = vault_.token0(); |
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.
Probably better style to hardcode the expected token addresses, then do a require check on the vault properties on init.
Nothing inherently incorrect with this approach, provided we do a manual spot check on deployment.
9e39bda to
4cf35e9
Compare
53a8c10 to
39bee7f
Compare
brandoniles
left a comment
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.
LGTM, just the comment update and looks good
Co-authored-by: Brandon Iles <brandon@fragments.org>
Uh oh!
There was an error while loading. Please reload this page.