XLS-0066 Lending Protocol #240

Tapanito · 2024-10-18T17:31:46Z

Discussion thread can be found here: #190
Development branch can be found here: TBD

sappenin · 2024-11-25T16:47:12Z

@Tapanito this PR seems ready to merge -- do you agree?

(Note that per the DRAFTS section of the CONTRIBUTING guidelines, merging does not mean endorsement or even a completed spec, but instead offers a way for spec editors to more easily edit using PRs).

Tapanito · 2024-12-04T14:10:41Z

Before merging, I'd like to have at least one review by an engineer to ensure everything is in order. In addition, similarly to Single Asset Vault, it is simpler/more convenient to edit a PR with various small design changes (e.g. names), rather than open a new PR for each of them. As a result, keeping a PR open allows to have a spec. that is more readily in-alignment with implementation.

sappenin · 2024-12-04T18:00:03Z

Makes sense, especially if it's more convenient. Just didn't want you (or anyone reading along) to think that merging here implies "finished product" (that's why we have a d designator, to indicate draft status).

XLS-0066d-lending-protocol/README.md

- Adds VaultNode to LoanBroker object to track in which owner directory of the Vaults pseudo-account the LoanBroker object is referenced. - Adds LoanBrokerNode to Loan object to track in which owner directory of the LoanBroker object the Loan is references. - Replaces CurrentTime to LastClosedLedger.CloseTime. - Changes the LoanBroker.Delete transaction to automatically return any outstanding Cover to the LoanBroker.Owner. - Adds a balance check to the LoanBrokerCoverDeposit transaction when depositing XRP. - Adds a check to LoanBrokerCoverWithdraw to ensure the CoverAvailable does not drop below Mimimum Cover Required.

Co-authored-by: Ed Hennis <ed@ripple.com>

… when the last Loan is delete

… for the missing flc

Tapanito · 2025-01-28T19:24:07Z

Hmmm, that would make sense, but let me make sure there are no legitimate use cases we would block.

…

On Tue, Jan 28, 2025, 19:18 Ed Hennis ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In XLS-0066d-lending-protocol/README.md <#240 (comment)>: > +$$ +valueChange = (prepaymentPenalty) - (interestOutstanding - accruedInterest) +$$ + +Note that `valueChange <= 0` as an early repayment reduces the total value of the Loan. In theory, yes, it is possible to have valueChange > 0. Remember: prepaymentPenalty = principalOutstanding \times closeInterestRate valueChage > 0 suggests that the borrower would pay MORE to close the Loan early, than repay the loan in scheduled payments. Yeah, those would be pretty cruddy terms to accept on a loan. So do we make valueChange <= 0 a hard requirement to stop loan sharking? 😁 — Reply to this email directly, view it on GitHub <#240 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMDKUYNBBEOX2W5APQBDZ32M7J2BAVCNFSM6AAAAABQGMS3AWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKNZZGIYDQNJVGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Tapanito · 2025-01-28T19:31:34Z

I prefer to measure a year in cups of coffee ☕

…

On Tue, Jan 28, 2025, 19:24 Ed Hennis ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In XLS-0066d-lending-protocol/README.md <#240 (comment)>: > +$$ +periodicRate = \frac{interestRate \times paymentInterval}{365 \times 24 \times 60 \times 60} +$$ If we assume that, by monthly payments you mean every 30 days, then 12% interest rate then the periodic rate would be (12 * 30) / 365 (the hours and seconds cancel out) or ~= 0.986` Ok. Perfect. Thanks! I was imaging a theoretical situation where I make 12 payments equally spaced across the year (i.e. every 365/12 = ~30.417 days or every 24*365/12 = 730 hours. Since the loans are timed in seconds, those terms are possible, and actually kinda interesting.) ...And now I'm humming *Seasons of Love*... — Reply to this email directly, view it on GitHub <#240 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMDKU2W6CZJOD2BQQSNFRL2M7KOLAVCNFSM6AAAAABQGMS3AWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKNZZGIYTSMBRGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

ximinez

Updates look good.

XLS-0066d-lending-protocol/README.md

Co-authored-by: Ed Hennis <ed@ripple.com>

XLS-0066d-lending-protocol/README.md

Tapanito · 2025-03-19T22:08:49Z

No, since we introduced a pseudo-account for the LoanBroker, the deposit will go there

…

On Wed, 19 Mar 2025 at 23:03, Ed Hennis ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In XLS-0066d-lending-protocol/README.md <#240 (comment)>: > + +##### 3.1.3.3 Invariants + +**TBD** + +[**Return to Index**](#index) + +#### 3.1.4 `LoanBrokerCoverWithdraw` + +The `LoanBrokerCoverWithdraw` transaction withdraws the First-Loss Capital from the `LoanBroker`. + +| Field Name | Required? | JSON Type | Internal Type | Default Value | Description | +| ----------------- | :----------------: | :-------: | :-----------: | :-----------: | :------------------------------------------------------------ | +| `TransactionType` | ✔️ | `string` | `UINT16` | **TODO** | Transaction type. | +| `LoanBrokerID` | ✔️ | `string` | `HASH256` | `N/A` | The Loan Broker ID from which to withdraw First-Loss Capital. | +| `Amount` | ✔️ | `object` | `NUMBER` | 0 | The amount of Vault asset to withdraw. | Perhaps it's worth keeping it as amount, and chaking the type to amount too? Just in case, in the future, we want to support depositing different cover assets? But doesn't the deposit go into the Single Asset Vault? That can't hold different types of assets. — Reply to this email directly, view it on GitHub <#240 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMDKUZ7CZWQZZUZKUFZQZD2VHSULAVCNFSM6AAAAABQGMS3AWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDOMBQGM3TONZRGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Sincerely, Vytautas Tumas

ximinez · 2025-03-20T16:30:33Z

No, since we introduced a pseudo-account for the LoanBroker, the deposit will go there

Right, I wasn't thinking about that, but if there is a loan default, and funds have to be paid out of the Cover Amount, wouldn't that go to the SAV?

Tapanito · 2025-03-20T16:58:24Z

No, since we introduced a pseudo-account for the LoanBroker, the deposit will go there

Right, I wasn't thinking about that, but if there is a loan default, and funds have to be paid out of the Cover Amount, wouldn't that go to the SAV?

Yes, 100%, the cover amount liquidation, in essence, will become a transfer of asset from one pseduo-account to another, with some accounting state changes.

ximinez · 2025-03-21T19:11:42Z

No, since we introduced a pseudo-account for the LoanBroker, the deposit will go there

Right, I wasn't thinking about that, but if there is a loan default, and funds have to be paid out of the Cover Amount, wouldn't that go to the SAV?

Yes, 100%, the cover amount liquidation, in essence, will become a transfer of asset from one pseduo-account to another, with some accounting state changes.

Right, so they should be the same currency, no? I'm fine with it being an STAmount as long as we're on the same page that the transaction should fail if it's not the same currency as the SAV.

gregtatcam · 2025-09-23T14:22:10Z

XLS-0066d-lending-protocol/README.md

+
+The following is the pseudo-code for handling a Loan payment transaction.
+
+```


What is value_change? Can as well add description for the arguments in and return.

gregtatcam · 2025-09-23T15:32:05Z

XLS-0066d-lending-protocol/README.md

+    }
+
+    return (total_principal_paid, total_interest_paid, loan_value_change, total_fee_paid)
+```


There are a few functions referred to in the pseudo-code but it's not always obvious what they refer to:

compute_late_payment(): section 3.2.4.1.2 Late Payment

compute_periodic_payment(): section 3.2.4.1.1 Regular Payment

compute_full_payment(): is it section 3.2.4.1.4 Early Full Repayment?

compute_current_value(): is it section 3.2.4.2 Total Loan Value Calculation?
Please describe at the start of the pseudo-code what sections each function refers to.
Also, it's not obvious what these functions return. For instance, when compute_periodic_payment() is called for the first time, it returns a struct with at least one member interest. When it's called a second time, it looks like it returns just one variable periodic_payment amount but then later in the code periodic_payment is used as a struct with {principal, interest}. Please describe the return value of each of the functions and match this value(s) with the calculated values in a relevant section. Also, use the return value consistently. I.e. don't change the type. Lastly, IMO it's better to use hungarian rather than snake notation and use the field names as they are defined in the corresponding ledger objects to make it consistent with the rest of the specs. For instance, pseudo-code refers to loan.payment_interval. Elsewhere in the specs this referred to as Loan.PaymentInterest.

gregtatcam · 2025-09-23T16:27:00Z

XLS-0066d-lending-protocol/README.md

+
+  - Total paid, and what portion goes to the vault:
+
+    - `totalPaid = principal_paid + interest_paid + fee_paid`


Is there any reason to mix hungarian and snake notation throughout the specs? IMHO it should be consistent and use hungarian notation (except for the field names, which should be capitalized).

ximinez · 2025-09-26T17:15:09Z

XLS-0066d-lending-protocol/README.md

+- Initial TotalValueOutstanding = 11 MPT
+- PaymentTotal = 10
+- Amortization produces periodicPayment = 1.1 MPT
+- Asset supports only whole units ⇒ each scheduled payment is truncated to 1 MPT
+  Progress:
+  After 9 payments: Paid = 9 MPT, Remaining TotalValueOutstanding = 2 MPT
+  If we applied the formula again for the 10th payment:
+  periodicPayment (unrounded) = 1.1 MPT → truncated to 1 MPT
+  Remaining after payment = 1 MPT (cannot be repaid; no payments left)
+  Adjustment:
+  Because PaymentRemaining = 1, set periodicPayment = TotalValueOutstanding = 2 MPT
+  Final payment = 2 MPT clears the loan exactly (PrincipalOutstanding = 0, TotalValueOutstanding = 0).


I've been looking at rounding the interest calculations up instead of truncating (down). Nothing is set in stone yet, but let's look at how that would work. I estimated an actual rate to show how the payments change over time.

Initial principal = 10 MPT

PeriodicRate = 0.0178 (Regardless of payment period)

PaymentTotal = 10

PeriodicPayment = 10 * 0.0178 * (1.0178^10) / (1.0178^10 - 1) ~= 1.10048958

Initial TotalValueOutstanding = PeriodicPayment * 10 = 11.0048958, which rounds up to 12 MPT (though we could round down or to nearest. This shouldn't really matter, since 1 MPT should not represent a significant amount)

Asset supports only whole units ⇒ first scheduled payment is rounded up to 2 MPT

After first payment:

TotalValueOutstanding = 10

PrincipalOutstanding = 9

PaymentsRemaining = 9

For the second payment, we recompute the periodic payment

PeriodicPayment = 9 * 0.0178 * (1.0178^9) / (1.0178^9 - 1) ~= 1.0910928, which rounds up to 2 MPT

TotalValueOutstanding = 8

PrincipalOutstanding = 8

PaymentsRemaining = 8

At this point, all of the interest has been paid!

What would the periodic payment be for the third payment?

PeriodicPayment = 8 * 0.0178 * (1.0178^8) / (1.0178^8 - 1) ~= 1.08174822, which would also round up to 2 MPT, and end up over paying.

Instead I propose that we add another rule:

if(PaymentRemaining > 1 && PrincipalOutstanding == TotalValueOutstanding) PeriodicPayment = PrincipalOutstanding / PaymentRemaining;

This is the same as the special case rule where the interest rate is 0, which makes sense, because if the interest rate is 0, the TotalValueOutstanding and PrincipalOutstanding will be identical for the life of the loan!

This would be in addition to the rule you outlined:

if (PaymentRemaining == 1) PeriodicPayment = TotalValueOutstanding;

And an invariant that PrincipalOutstanding <= TotalValueOutstanding. (As an aside, this might let me get rid of the OriginalPrincipal field I added to help with rounding, and simplify a lot of the rounding operations, because any accumulated dust will be wiped out in the last payment. Maybe not, though, because those amounts are taken out of other fields like DebtTotal, and rounding might get weird there.)

I propose we move forward with this scheme for these reasons:

It more realistically maps to the real world (or at least my real world experience) where, for example, my last mortgage payment is scheduled to be less than all the mortgage payments leading up to it.

I think people will complain if they've been making smaller payments all along, and then have it balloon at the end. I also think Vault shareholders would like to get their interest up front.

In a situation like this one where the interest is paid off early, the borrower can continue paying the same amount an potentially pay their loan off early (either through overpayments or extra payments).

It simplifies the math for later payments, because I only have to divide once, instead of taking powers, multiplying, and dividing multiple times, which might be ever so slightly more performant.

…mputation

mvadari · 2025-10-02T14:26:30Z

XLS-0066d-lending-protocol/README.md

+The total fee for the transaction will be increased due to the extra signatures that need to be processed, similar to the additional fees for multisigning. The minimum fee will be $(|signatures| + 1) \times base_fee$ where $|signatures| == max(1, |tx.CounterPartySignature.Signers|)$
+
+The total fee calculation for signatures will now be $(1 + |tx.Signers| + |signatures|) \times base_fee$. In other words, even without a `tx.Signers` list, the minimum fee will be $2 \times base_fee$.


Suggested change

The total fee for the transaction will be increased due to the extra signatures that need to be processed, similar to the additional fees for multisigning. The minimum fee will be $(|signatures| + 1) \times base_fee$ where $|signatures| == max(1, |tx.CounterPartySignature.Signers|)$

The total fee calculation for signatures will now be $(1 + |tx.Signers| + |signatures|) \times base_fee$. In other words, even without a `tx.Signers` list, the minimum fee will be $2 \times base_fee$.

The total fee for the transaction will be increased due to the extra signatures that need to be processed, similar to the additional fees for multisigning. The minimum fee will be $(|signatures| + 1) \times base\_fee$ where $|signatures| == max(1, |tx.CounterPartySignature.Signers|)$

The total fee calculation for signatures will now be $(1 + |tx.Signers| + |signatures|) \times base\_fee$. In other words, even without a `tx.Signers` list, the minimum fee will be $2 \times base\_fee$.

I think this is correct LaTeX to get the underscore to appear right.

ximinez

Just a comment...

ximinez · 2025-10-01T17:26:53Z

XLS-0066d-lending-protocol/README.md

+$$
+latePaymentInterest = principalOutstanding \times \frac{lateInterestRate \times secondsSinceLastPayment}{365 \times 24 \times 60 \times 60}
+$$


I believe the correct calculation is:

secondsSinceLastPayment = lastLedgerCloseTime - Loan.nextPaymentDate ``

I was thinking about this yesterday, when we were looking at this. I agree.

amarantha-k · 2025-10-22T22:01:42Z

@Tapanito Just a quick note to drop the "d" from the directory name before merging. (XLS-0066d-lending-protocol/README.md -> XLS-0066-lending-protocol/README.md).

gregtatcam · 2025-10-28T16:40:15Z

XLS-0066d-lending-protocol/README.md

+
+##### 2.2.2.5 PeriodicPayment
+
+The periodic payment amount represents the precise sum the Borrower must pay during each payment cycle. For practical implementation, this value should be rounded UP when processing payments. The system automatically recalculates the PeriodicPayment following any overpayment by the borrower. For instance, when dealing with MPT loans, the calculated `PeriodicPayment` may be `10.251`. However, since MPTs only support whole number representations, the borrower would need to pay `12` units. The system maintains the precise periodic payment value at maximum accuracy since it is frequently referenced throughout loan payment computations.


11 units, not 12.

gregtatcam · 2025-10-28T16:48:13Z

XLS-0066d-lending-protocol/README.md

+
+##### 2.2.2.2 TotalValueOutstanding
+
+The total outstanding value of the Loan, including all fees. To calculate the outstanding interest portion, use this formula: `TotalInterestOutstanding = TotalValueOutstanding - PrincipalOutstanding - ManagementFeeOutstanding`.


If it includes all fees then why only ManagementFeeOutstanding is subtracted?

gregtatcam · 2025-10-28T16:48:33Z

XLS-0066d-lending-protocol/README.md

+The loan's financial state is tracked through three key components:
+
+- **PrincipalOutstanding**: Represents the remaining principal balance that the borrower must repay to satisfy the original loan amount.
+- **TotalValueOutstanding**: Encompasses the complete remaining loan obligation, comprising both the outstanding principal and all scheduled interest payments based on the original amortization schedule. This value excludes any additional interest charges resulting from late payments.


Should mention the fees. Per section 2.2.2.2 TotalValueOutstanding also includes the fees.

gregtatcam · 2025-10-28T16:50:36Z

XLS-0066d-lending-protocol/README.md

+
+- **PrincipalOutstanding**: Represents the remaining principal balance that the borrower must repay to satisfy the original loan amount.
+- **TotalValueOutstanding**: Encompasses the complete remaining loan obligation, comprising both the outstanding principal and all scheduled interest payments based on the original amortization schedule. This value excludes any additional interest charges resulting from late payments.
+- **InterestOutstanding**: The total scheduled interest remaining on the loan, derived as `TotalValueOutstanding - PrincipalOutstanding`.


Why is the fee not subtracted? This is different from section 2.2.2.2.

gregtatcam · 2025-10-28T17:05:51Z

XLS-0066d-lending-protocol/README.md

+- **TotalValueOutstanding**: Encompasses the complete remaining loan obligation, comprising both the outstanding principal and all scheduled interest payments based on the original amortization schedule. This value excludes any additional interest charges resulting from late payments.
+- **InterestOutstanding**: The total scheduled interest remaining on the loan, derived as `TotalValueOutstanding - PrincipalOutstanding`.
+
+**Asset-Specific Precision Handling**: For discrete asset types (MPTs and XRP denominated in drops), both `TotalValueOutstanding` and `PrincipalOutstanding` values are truncated to whole numbers to ensure compatibility with the underlying asset precision requirements.


Are the values always truncated or rounded up or down?

gregtatcam · 2025-10-28T17:20:21Z

XLS-0066d-lending-protocol/README.md

+| ----------------- | :----------------: | :-------: | :-----------: | :-----------: | :---------------------------------------------------------------------- |
+| `TransactionType` | :heavy_check_mark: | `string`  |   `UINT16`    |     `77`      | Transaction type.                                                       |
+| `LoanBrokerID`    | :heavy_check_mark: | `string`  |   `HASH256`   |     `N/A`     | The Loan Broker ID from which to withdraw First-Loss Capital.           |
+| `Amount`          | :heavy_check_mark: | `object`  |   `AMOUNT`    |       0       | The Fist-Loss Capital amount to withdraw.                               |


Should this be NUMBER type? We are going to access Vault anyways so will now specific Asset type. NUMBER is going to make the tx size smaller by 40 bytes(IOU/XRP) or 24 bytes (MPT). It's also fewer checks in preclaim. This also applies to LoanBrokerCoverDeposit, LoanBrokerCoverWithdraw, and LoanPay. By the way, PrincipalRequested in LoanSet is NUMBER. I think it makes sense to make all the Amount fields to have NUMBER type.

Should this be NUMBER type? We are going to access Vault anyways so will now specific Asset type. NUMBER is going to make the tx size smaller by 40 bytes(IOU/XRP) or 24 bytes (MPT). It's also fewer checks in preclaim. This also applies to LoanBrokerCoverDeposit, LoanBrokerCoverWithdraw, and LoanPay. By the way, PrincipalRequested in LoanSet is NUMBER. I think it makes sense to make all the Amount fields to have NUMBER type.

There was an earlier discussion on this topic. #240 (comment)

tl;dr Because of how SFields are defined, any field name Amount must be AMOUNT. It was decided to keep the familiar name rather than create a new field.

Tapanito added 2 commits October 18, 2024 18:28

adds lending protocol spec

ba3a750

improves the description of the management fee

d3e6115

renames field names from plural to singular

b297e6e

ximinez requested changes Jan 24, 2025

View reviewed changes

Tapanito and others added 7 commits January 27, 2025 16:40

removes CoverAvailable check from LoanBrokerDelete transaction

f18e8f1

Apply suggestions from code review

44e1b57

Co-authored-by: Ed Hennis <ed@ripple.com>

cleans up latex code

1a437ee

updates LoanDelete transaction to delete the LoanBroker DirectoryNode…

9f47ea2

… when the last Loan is delete

in case insufficient first loss capital add loan broker fees to cover…

60a311e

… for the missing flc

fixes loan object ownership

9090bd3

adds pseudo-account to the LoanBroker

8851620

ximinez approved these changes Jan 29, 2025

View reviewed changes

Tapanito added 2 commits January 31, 2025 12:51

adds counterparty to LoanSet transaction

0f6644c

updates failure conditions of LoanSet transaction

14a634f

ximinez requested changes Mar 12, 2025

View reviewed changes

XLS-0066d-lending-protocol/README.md Outdated Show resolved Hide resolved

ximinez requested changes Mar 12, 2025

View reviewed changes

XLS-0066d-lending-protocol/README.md Outdated Show resolved Hide resolved

Update XLS-0066d-lending-protocol/README.md

b77401b

Co-authored-by: Ed Hennis <ed@ripple.com>

ximinez requested changes Mar 19, 2025

View reviewed changes

Tapanito added 2 commits March 19, 2025 11:30

addresses PR comments

aa50126

fixes signature field name

9acddc1

improves variable name consistency

2c2524e

gregtatcam suggested changes Sep 23, 2025

View reviewed changes

Tapanito added 4 commits September 26, 2025 13:23

Merge branch 'master' into xls-66-lending-protocol

6b04e50

adds DebtTotal > 0 condition to LoanBrokerDelete

4ba07c6

adds Loan.TotalValueOutstanding

4b02ae4

adds Loan.PrincipalRequested

a43426e

ximinez reviewed Sep 26, 2025

View reviewed changes

Tapanito added 5 commits September 29, 2025 20:04

adds authentication requirements to the loanset transaction

7022130

fixes debt maximum calculation

2ef8f5a

improves the handling of fees when loanbroker account is frozen

0a05584

Merge branch 'master' into xls-66-lending-protocol

2977f04

improves the pseudo-code accuracy and removes bugs in late payment co…

63730e5

…mputation

mvadari reviewed Oct 2, 2025

View reviewed changes

ximinez reviewed Oct 2, 2025

View reviewed changes

Tapanito added 3 commits October 21, 2025 14:27

adds loan overpayment flag to LoanPay transaction

ead6cec

adds description of rounding error handling

1607e70

adds balance checks to loan pay

5dda351

mvadari changed the title ~~XLS-0066d Lending Protocol~~ XLS-0066 Lending Protocol Oct 22, 2025

Tapanito added 7 commits October 23, 2025 10:43

adds loan scale field

1933a4a

completely rewrites they loanPay transaction

b855be2

adds extra guards to loanset transaction

789ee88

adds missing fullpayment flag in pseudo-code

b976847

adds missing fee

d644b04

adds missing fee

77d789c

adds exclusivit check for overpayment and earrly payment flags

853563d

gregtatcam reviewed Oct 28, 2025

View reviewed changes

renames PreviousPaymentDate to PreviousPaymentDueDate

732b33e


		The following is the pseudo-code for handling a Loan payment transaction.

		```


		- Total paid, and what portion goes to the vault:

		- `totalPaid = principal_paid + interest_paid + fee_paid`

		The total fee for the transaction will be increased due to the extra signatures that need to be processed, similar to the additional fees for multisigning. The minimum fee will be $(\|signatures\| + 1) \times base_fee$ where $\|signatures\| == max(1, \|tx.CounterPartySignature.Signers\|)$

		The total fee calculation for signatures will now be $(1 + \|tx.Signers\| + \|signatures\|) \times base_fee$. In other words, even without a `tx.Signers` list, the minimum fee will be $2 \times base_fee$.


		##### 2.2.2.5 PeriodicPayment

		The periodic payment amount represents the precise sum the Borrower must pay during each payment cycle. For practical implementation, this value should be rounded UP when processing payments. The system automatically recalculates the PeriodicPayment following any overpayment by the borrower. For instance, when dealing with MPT loans, the calculated `PeriodicPayment` may be `10.251`. However, since MPTs only support whole number representations, the borrower would need to pay `12` units. The system maintains the precise periodic payment value at maximum accuracy since it is frequently referenced throughout loan payment computations.


		##### 2.2.2.2 TotalValueOutstanding

		The total outstanding value of the Loan, including all fees. To calculate the outstanding interest portion, use this formula: `TotalInterestOutstanding = TotalValueOutstanding - PrincipalOutstanding - ManagementFeeOutstanding`.

XLS-0066 Lending Protocol #240

Are you sure you want to change the base?

XLS-0066 Lending Protocol #240

Conversation

Tapanito commented Oct 18, 2024

Uh oh!

sappenin commented Nov 25, 2024

Uh oh!

Tapanito commented Dec 4, 2024

Uh oh!

sappenin commented Dec 4, 2024

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Tapanito commented Jan 28, 2025 via email

Uh oh!

Tapanito commented Jan 28, 2025 via email

Uh oh!

ximinez left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Tapanito commented Mar 19, 2025 via email

Uh oh!

ximinez commented Mar 20, 2025

Uh oh!

Tapanito commented Mar 20, 2025

Uh oh!

ximinez commented Mar 21, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ximinez Sep 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ximinez left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

amarantha-k commented Oct 22, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

ximinez Sep 26, 2025 •

edited

Loading