Skip to content

ADR: Revise interest curve utilization rate definition#303

Open
jordanschalm wants to merge 1 commit intomainfrom
jord/adr-interest-curve-utilization
Open

ADR: Revise interest curve utilization rate definition#303
jordanschalm wants to merge 1 commit intomainfrom
jord/adr-interest-curve-utilization

Conversation

@jordanschalm
Copy link
Copy Markdown
Member

No description provided.


### Minimal Example
- User A deposits 100 units of X
- User B withdraws 100 units of X -> totalDebit(X) = 100
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- User B withdraws 100 units of X -> totalDebit(X) = 100
- User B withdraws (borrows) 100 units of X -> totalDebit(X) = 100

Comment on lines +24 to +25
- User B deposits 105 units of X -> totalDebit(X) = 0
- User B still owes 5 units of X, but totalDebit(X) = 0
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why B depositing 105 units would make totalDebit(X) to 0? Could you add more details in the comments.

Prior to this ADR, protocol fees were computed as a percentage of estimated debit income, when extracted. Instead, we will compute protocol fees (insurance fee, stability fee) explicitly as the excess funds available in reserves.

```
protocolFee = reserveBalance + totalTrueDebitBalance - totalTrueCreditBalance
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe more clear:

Suggested change
protocolFee = reserveBalance + totalTrueDebitBalance - totalTrueCreditBalance
IdleAmount = totalTrueCreditBalance - totalTrueDebitBalance
protocolFee = reserveBalance - IdleAmount

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants