UPDATE ON AAVE
I tried to analyze in depth the new update "AAVEPro" proposed by
$AAVE and here are some major problems that arise from this update:
• Conflict between the team that designed the V3 protocol and the team that designed the new V4 protocol
In reality, what happened?
AAVE tasked
#AaveLabs with the design of the new V4 protocol, which angered the team that built V3 because AaveLabs requested a huge budget for the implementation of the update (almost $15M of GHO per year over 3 years) and last month they withdrew, saying that AaveLabs is taking control over everything and making AAVE too centralized.
Now you might be wondering where the problem lies in all this?
What you need to know is that the security of AAVE, at least of the V4 protocol 😂 (I love provocations) is divided by 2 since the first team, which consisted of
#BGDLabs and
#ACI , was working together with
#AaveLabs to secure the V3 protocol; their withdrawal simply halves the security of V3.
So AAVE divides its security by 2 to satisfy the needs of its community, well done 👏 👏 👏
Give me your opinion in the comments 💬