-
Notifications
You must be signed in to change notification settings - Fork 45
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
Carbon Vortex 2.0 #140
Carbon Vortex 2.0 #140
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.
FYI: uint32(block.timestamp)
is an unsafe cast which appears in about 5 different places in the code, but I suppose (know) that it is harmless in the foreseeable future...
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.
You should probably use extend-function-calc-exp-decay-input-range
as the base branch here (and perhaps also pull from it or rebase on top of it), so that the diffs related to that branch don't show up on this PR.
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've left a few semantic comments, and a couple of important ones related to the "uint128 stuff", so I'd like to emphasize once again:
I think that we should have as little as possible "uint128 stuff" in the code, meaning that everything stays as uint256 right up to the point when we need to store it somewhere.
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.
This is a preliminary review, but FYI
…ex-2.0 Carbon Vortex 2.0
Based on this governance proposal:
https://gov.bancor.network/t/carbon-vortex-2-0-dutch-auction/4597