AAVE
What Is AAVE?
aaVE is a decentralized non-custodial liquidity market protocol where users can participate as depositors or borrowers. Depositors provide liquidity to the market to earn a passive income, while borrowers are able to borrow in an overcollateralised (perpetually) or undercollateralised (one-block liquidity) fashion.
Why AAVE?
AAVE Protocol has been audited and secured. The protocol is completely open source, which allows anyone to interact with a user interface client, API or directly with the smart contracts on the Ethereum network. Being open source means that you are able to build any third-party service or application to interact with the protocol and enrich your product.
How Do I Interact With AAVE Protocol?
In order to use to interact with AAVE protocol, you simply deposit your preferred asset and amount. After depositing, you will earn passive income based on the market borrowing demand. Additionally, depositing assets allows you to borrow by using your deposited assets as a collateral. Any interest you earn by depositing funds helps offset the interest rate you accumulate by borrowing.
What Is The Cost Of Interacting With AAVE Protocol?
Interacting with the protocol requires transactions and so transaction fees for Ethereum Blockchain usage, which depend on the network status and transaction complexity.
Where Are My Deposited Funds Stored?
Your funds are allocated in a smart contract. The code of the smart contract is public, open source, formally verified and audited by third party auditors. You can withdraw your funds from the pool on-demand or export a tokenised (aTokens) version of your lender position. aTokens can be moved and traded as any other cryptographic asset on Ethereum.
Is There Any Risk?
No platform can be considered entirely risk free. The risks related to the AAVE platform are the smart contract risk (risk of a bug within the protocol code) and liquidation risk (risk on the collateral liquidation process). Every possible step has been taken to minimise the risk as much as possible-- the protocol code is public and open source and it has been audited. Additionally, there is an ongoing bug bounty campaign live and running.
Last updated
Was this helpful?