[AAVE V3 Lending Protocol] Issue 2: Borrowing, Repayment, and Interest Accrual

[polarker]

Parent issue: #23

Objective:

Create mechanisms to allow users to borrow assets, repay loans, and accrue interest over time.

Description:

This issue focuses on enabling borrowing and repayment functionalities and implementing interest accrual mechanisms based on demand and supply.

Tasks:

1. Implement a borrowing function that ensures users can borrow assets against their collateral.
2. Develop a repayment function to allow users to repay their loans.
3. Add interest rate calculations based on demand-supply dynamics and accrue interest over time.
4. Write tests to validate borrowing, repayment, and interest accrual mechanisms.

Acceptance Criteria:

• Users can borrow and repay assets seamlessly.
• Interest rates adjust dynamically based on demand and supply.
• Interest accrues correctly over time and reflects in the system.
• Tests demonstrate the robustness of the borrowing, repayment, and interest accrual mechanisms.

[mimisavage]

Can I work on this, please?

[ShantelPeters]

Can i please be assigned to this issue ?

[Supa-mega]

Could I be assigned to this?

[codebestia]

Can i work on this?
I am a blockchain developer and i have worked with AAVE V3 lending protocol once.
Check it out here

[kfastov]

Hi! Great to see you all here, but I guess we'll wait for the basic implementation of the contract (to be done in #34) before assigning this issue

[abdegenius]

Could I take a shot at this?

[CEOliam]

Can I tackle this one?

[aniruddhaaps]

To address this issue I would implement borrowing with collateral security such that borrowing assets is done efficiently. Then, implement the repayment process and dynamic interest rate calculation with demand-supply mechanics. Accurately calculate interest accrual over time. Test all of these thoroughly to validate the system's reliability and usability for the users.

[kfastov]

@codebestia Hi! I understand 2 days may be too fast for such an issue, but please share your progress and kindly submit a draft PR shortly. If you won't do it, we'll have to reassign it to someone else

[codebestia]

@kfastov GM!. I was under the impression that the parent issue will be completed before this issue is addressed. As that is not the case, give me an estimate of 24 hours to make a PR. I already have my implementation in mind.

[codebestia]

@kfastov Hello!. This PR needs to be merged before i can open my own. So as to prevent major conflicts and unnecessary work.

[raduciobanu22]

@codebestia Are you still interested to submit a PR? If yes, please don't wait for the other PR to be merged. You can branch from it and continue.

[codebestia]

@raduciobanu22 Okay.. On it.