banner.jpg

Aave Launches Its Permissioned Lending And Liquidity Service



Aave (AAVE), the decentralized lending platform, has launched its permissioned lending and liquidity service Aave Arc to help institutions participate in regulation-compliant decentralized finance.


It has been reported that as opposed to its permissionless cross-chain counterparts on the platform, Aave Arc is a permissioned liquidity pool specifically designed for institutions to maintain regulatory compliance in the decentralized finance (DeFi) space.


However, the first of 30 entities lined up for the whitelist for Aave Arc was Fireblocks, the institutional digital asset custodian. It explained in an announcement that the pool “enables whitelisted institutions to securely participate in DeFi as liquidity suppliers and borrowers.”


The report said that users of Aave Arc must perform due diligence procedures such as Know Your Customer/Anti-Money Laundering (KYC/AML) in order to gain access. Fireblocks also serves as a whitelisting agent for Aave Arc, ensuring other institutions that wish to join the permission pool perform KYC/AML requirements.


Likewise, Aave cannot perform this task, itself, because it is not a regulated entity such as a bank or other traditional financial institution. As the whitelisting agent, Fireblocks has already approved “30 licensed financial institutions to participate on Aave Arc as suppliers, borrowers, and liquidators.”


Among some of the whitelisted entities are Anubi Digital, Canvas Digital, CoinShares, GSR, and crypto yield aggregator Celsius.

According to DappRadar, Aave’s new permissioned liquidity pool aims to onboard more institutions to the burgeoning DeFi space that has $133 billion in total value locked (TVL) as of January 6. That TVL has grown 4.5 times since January 10 of 2021.


Thus, most remained skittish about dabbling in DeFi due to compliance hurdles and regulatory uncertainty while institutions began purchasing cryptocurrency in increasingly sizable portions in 2021.


Source: Cointelegraph


 

0 comments