Skip to content
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

Deploy 091 - Upgrade OETHVaultCore #2035

Merged
merged 5 commits into from Apr 30, 2024
Merged

Deploy 091 - Upgrade OETHVaultCore #2035

merged 5 commits into from Apr 30, 2024

Conversation

shahthepro
Copy link
Collaborator

@shahthepro shahthepro commented Apr 26, 2024

Contracts

Governance


If you made a contract change, make sure to complete the checklist below before merging it in master.

Refer to our documentation for more details about contract security best practices.

Contract change checklist:

  • Code reviewed by 2 reviewers.
  • Copy & paste code review security checklist below this checklist.
  • Unit tests pass
  • Slither tests pass with no warning
  • Echidna tests pass if PR includes changes to OUSD contract (not automated, run manually on local)

@naddison36
Copy link
Collaborator

I have verified the following

  • The original PR to master only has one approver but I've since review it. Simplify Mint & Redeem #1995
  • The proposal is upgrading the proxy to the correct implementation address.
  • The proposal calls cacheWETHAssetIndex on the Vault
  • The OETH Vault proxy address in the proposal is correct
  • The deployed OETHVaultCore implementation contract matched the source code on this shah/deploy-091 branch.
sol2uml diff 0x8f371d8e65f35914cdb8dd58b997411871dabb37 .,node_modules
Compared the "OETHVaultCore" contract with address 0x8f371d8e65F35914CDb8Dd58B997411871dABb37 on mainnet
to local files under folders ".,node_modules"

match   @openzeppelin/contracts/token/ERC20/IERC20.sol
match   @openzeppelin/contracts/token/ERC20/utils/SafeERC20.sol
match   @openzeppelin/contracts/utils/Address.sol
match   @openzeppelin/contracts/utils/math/SafeMath.sol
match   contracts/governance/Governable.sol
match   contracts/interfaces/IBasicToken.sol
match   contracts/interfaces/IGetExchangeRateToken.sol
match   contracts/interfaces/IOracle.sol
match   contracts/interfaces/IStrategy.sol
match   contracts/token/OUSD.sol
match   contracts/utils/Helpers.sol
match   contracts/utils/Initializable.sol
match   contracts/utils/InitializableERC20Detailed.sol
match   contracts/utils/StableMath.sol
match   contracts/vault/OETHVaultCore.sol
match   contracts/vault/VaultCore.sol
match   contracts/vault/VaultInitializer.sol
match   contracts/vault/VaultStorage.sol

@sparrowDom
Copy link
Member

  • I've verified that the deployed contract address 0x8f371d8e65f35914cdb8dd58b997411871dabb37 matches the sources in git: npx sol2uml diff 0x8f371d8e65f35914cdb8dd58b997411871dabb37 .,node_modules
  • there are 2 proposals created for this deploy, the one with id 78389253671544237322939434422056971914944279457140328550595948923573494383344 should be passed
  • the proposal upgrades the OETHVaultCore of the OETHVaultProxy (addresses correct), and calls cacheWETHAssetIndex on the OETHVaultProxy

Source code verification:

npx sol2uml diff 0x8f371d8e65f35914cdb8dd58b997411871dabb37 .,node_modules
Compared the "OETHVaultCore" contract with address 0x8f371d8e65F35914CDb8Dd58B997411871dABb37 on mainnet
to local files under folders ".,node_modules"

match   @openzeppelin/contracts/token/ERC20/IERC20.sol
match   @openzeppelin/contracts/token/ERC20/utils/SafeERC20.sol
match   @openzeppelin/contracts/utils/Address.sol
match   @openzeppelin/contracts/utils/math/SafeMath.sol
match   contracts/governance/Governable.sol
match   contracts/interfaces/IBasicToken.sol
match   contracts/interfaces/IGetExchangeRateToken.sol
match   contracts/interfaces/IOracle.sol
match   contracts/interfaces/IStrategy.sol
match   contracts/token/OUSD.sol
match   contracts/utils/Helpers.sol
match   contracts/utils/Initializable.sol
match   contracts/utils/InitializableERC20Detailed.sol
match   contracts/utils/StableMath.sol
match   contracts/vault/OETHVaultCore.sol
match   contracts/vault/VaultCore.sol
match   contracts/vault/VaultInitializer.sol
match   contracts/vault/VaultStorage.sol

@shahthepro shahthepro merged commit 3f1afe9 into master Apr 30, 2024
11 of 13 checks passed
@shahthepro shahthepro deleted the shah/deploy-091 branch April 30, 2024 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants