-
Notifications
You must be signed in to change notification settings - Fork 59
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
Rollback ve changes #696
Rollback ve changes #696
Conversation
Thanks. Could you show a diff of our code, and the original ve code? Perhaps right before doing the diff, replace CRV with OCEAN. |
I've updated the We made modifications in |
That's the diff between our code before the PR, and our code after the PR. (Or did I miss something?) I'm interested to see the diff between our code after the PR, and Curve's code. |
Oh I see. In this PR, for each contract, I copy pasted the code from the Curve repo and replaced CRV with OCEAN in the code comments. Here are the original contracts from Curve repos: The contracts should be identical, excluding the comments. |
Looks like we are using different vyper versions for contracts: -0.3.1 in https://github.com/oceanprotocol/contracts/blob/rollback-ve-changes/contracts/ve/veDelegation.vy#L1 Although, technically, is not an issue (we can download all those compilers), I do wonder if we can stick with one version for all contracts |
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
@alexcos20 in the previous version I upgraded the contract versions. In the PR, I set them as in original contracts in case there could be a security issue. Maybe I'm being too paranoid. |
Changes proposed in this PR:
Rollback changes to ve contracts.