DeFi protocols have been upping their risk parameters to fend off attacks from bad actors.
On Nov. 28, the Aave community voted in favor of a proposal to freeze 17 tokens with low liquidity on v2 of the protocol. The proposal was passed with 536,870 AAVE tokens in favor, which was well past the required quorum of 320,000 tokens.
The proposal to freeze the illiquid markets was first put forth by risk management firm Gauntlet as a way to de-risk Aave v2, Unchained reported last week. The essence of the move will be in aid of freezing activity in these volatile and relatively illiquid markets while encouraging users to migrate to v3 – a newer version of the protocol with more stringent risk measures in place.
The liquidity pools that will cease to operate are YFI, CRV, ZRX, MANA, 1INCH, BAT, sUSD, ENJ, GUSD, AMPL, RAI, USDP, LUSD, xSUSHI, DPI, renFIL and MKR.
Aave has also been increasingly encouraging users to move assets to v3 of the protocol. Another proposal enacted on Nov. 28 called for 26 assets to be deployed on Aave v3 Ethereum.
“Aave V2 lacks many of the risk controls that Aave V3 solves for (supply caps, borrow caps, isolation mode, e-mode, etc),” said Gauntlet’s Pauljlei in a governance forum discussion last week.
On Friday, Aave founder Stani Kulechov shared a proposal from Bored Ghosts Developing (BGD Labs) — a team of Aave technical developers — to set up risk council for Aave v3. The proposed risk council would ideally consist of five members without any conflict of interest, who would authorize a limited set of actions as fast as possible in the event that the protocol is under threat.
“As an example, having ‘faster’ mechanism on Aave v2 Ethereum would have allowed disabling borrowing on CRV, which almost surely would have reduced the bad debt to 0,” said BGD Labs, referring to the Mango Market’s exploiter’s attempted CRV exploit on Aave last week.