1. PixelPlaygroundHome
  2. Metaverse Insights

Aave community discusses deployment of Aave V3 MVP version

• Metaverse Insights • 119 views

On March 3, the Aave community launched a discussion on the temperature check and governance of the deployment of the Aave V3 MVP version on the main Polygon z…

Aave community discusses deployment of Aave V3 MVP version

On March 3, the Aave community launched a discussion on the temperature check and governance of the deployment of the Aave V3 MVP version on the main Polygon zkEVM network. At present, the community hopes that through the proposal discussion, the deployment of Aave V3.0.1 (MVP V3) on zkEVML2 will enable Aave Governance to establish a strategic position on the network as soon as possible. The deployment of AaveV3 has a small development workload, but in order to reduce risks, the proposal proposes to limit the inflow of assets and set conservative risk parameters so that the development and risk service providers can conduct a more in-depth analysis of the zkEVM network. The proposal proposes to add only three collateral (WETH, WMATIC and USDC) and one lendable asset (USDC) to reduce risk.

The Aave community initiated a discussion on the temperature check of deploying the Aave V3 MVP version on the main network of Polygon zkEVM

Interpretation of the news:


The Aave community has initiated a discussion on the temperature check of the deployment of the Aave V3 MVP version on the main Polygon zkEVM network. The community aims to establish a strategic position on the network as soon as possible through the proposal discussion. The deployment of AaveV3 has a small development workload, but in order to reduce risks, the proposal suggests limiting the inflow of assets and setting conservative risk parameters.

The deployment of Aave V3 MVP version on the main Polygon zkEVM network would provide Aave Governance with a strategic position on the network, bringing the community one step closer to achieving its goal. Aave Governance would be able to leverage the opportunities available on the Polygon zkEVM network and enhance its services, offering users more efficient and cost-effective solutions.

However, the community understands the risks that come with deploying on a new network, and so the proposal suggests limiting the inflow of assets and taking a conservative approach to risk parameters. Adding only three collateral (WETH, WMATIC, and USDC) and one lendable asset (USDC) would reduce the risk of loss, ensuring a safe deployment process.

The proposal stresses the importance of conducting a thorough analysis of the zkEVM network’s development and risk services providers, ensuring a deep understanding of the network’s capabilities and limitations. By doing so, the Aave community can optimize the deployment process and mitigate risks effectively, while offering its services to an expanding network of users.

In summary, the Aave community’s discussion on the deployment of the Aave V3 MVP version on the main Polygon zkEVM network highlights the importance of taking a risk-averse approach to new network deployment. By deploying conservatively and limiting the inflow of assets, Aave Governance can establish a strategic position on the network and offer cost-effective solutions to its expanding user base. The proposal emphasizes the importance of conducting a thorough analysis of the network’s capabilities and limitations to ensure optimal deployment and risk management.

This article and pictures are from the Internet and do not represent Fpips's position. If you infringe, please contact us to delete:https://www.fpips.com/4827/

It is strongly recommended that you study, review, analyze and verify the content independently, use the relevant data and content carefully, and bear all risks arising therefrom.

Like (0)
Previous 03/03/2023 09:19
Next 03/03/2023 09:49

Recommended articles