Motivation:
Deploying V3 is pretty complex process and it will also affect existing V2 deployment. To make it smoother, we can start the process from deploying address provider v3 which has backward comparability with V1 and DataCompressor V2.1. which has compatible data structure with DataCompressor V3.
Some apps now depends on DataCompressor V2, which functionality will be broken when a new pool v3 or credit manager v3 will be added to contract registered. To be prepared, it's easier to get time to migrate to DC2.1. which works correct and would not be affected.
As result, services which will be tested to support V2 & V3 could be simplified and some legacy code could be removed.
Suggestion:
- Deploy address provider v3
- Setup all contract address similart to existing v1
- Use address provider v3 as entry point in all docs
- Deploy DataCompressor V2.1. to migrate for unified interface for all existing monitoring and other apps.
Specification
- Deploy AddressProviderV3 with create2 factory
- Set CONTRACTS_REGISTER address in AddressProviderV3
- Set ACCOUNT_FACTORY address in AddressProviderV3
- Set TREASURY address in AddressProviderV3
- Set GEAR_TOKEN address in AddressProviderV3
- Set WETH_TOKEN address in AddressProviderV3
- Set WETH_GATEWAY address in AddressProviderV3
- Set PRICE_ORACLE_V2 address in AddressProviderV3
- Set ROUTER_V2 address in AddressProviderV3
- Deploy DataCompressorV2_10 with create2 factory
- Set DATA_COMPRESSOR_V2_1 address in AddressProviderV3
- Set description in DATA_COMPRESSOR_V2_1 for DAI v2 credit manager
- Set description in DATA_COMPRESSOR_V2_1 for USDC v2 credit manager
- Set description in DATA_COMPRESSOR_V2_1 for WETH v2 credit manager
- Set description in DATA_COMPRESSOR_V2_1 for wstETH v2 credit manager
- Set description in DATA_COMPRESSOR_V2_1 for WBTC v2 credit manager
- Set description in DATA_COMPRESSOR_V2_1 for FRAX v2 credit manager
- Set description in DATA_COMPRESSOR_V2_1 for WETH v2 credit manager
ETA 18 oct 2023 15:00 CET
Voting
Simple Approve / Reject