-
Notifications
You must be signed in to change notification settings - Fork 212
feat: bump AO version and report consensus version and remove legacy oracle #1034
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
base: feat/vaults
Are you sure you want to change the base?
Conversation
Hardhat Unit Tests Coverage Summary
Diff against master
Results for commit: 669c094 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
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.
👀
|
||
_updateContractVersion(2); | ||
/// @dev BaseOracle.initialize() mistakenly sets the contract version to 1, so it's impossible to |
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 let's update BaseOracle then?
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.
3808666
It was an initial update, but this adds VEBO into the scope and makes it un-sync with the deployed contracts.
This PR bumps the AO contract version and consensus version for the AO report. Also, remove Legacy Oracle from the repo, as it is not needed elsewhere.
Context
For vaults, we need to update AO version and it's consensus version
Problem
Some issues arise while bumping the version:
Solution
The solution is in this PR