The XRP Ledger's proposed lending protocol could punish depositors far more when one big borrower defaults than when the same total debt fails across many smaller loans, according to a modeled example built from the protocol's documented rules. A single 100,000-token default leaves depositors with a 90,000-token loss, while ten 10,000-token defaults produce only a 4,500-token loss — a 20-fold gap despite identical total debt and reserve.
How the lending model works
The protocol pools assets in a vault and extends fixed-term, uncollateralized loans through a broker. Depositors hold shares in the vault, and the value of those shares falls when the vault's assets suffer losses. The model is designed to protect the pool with a reserve, but the way that reserve is released per default creates a striking asymmetry.
In the modeled comparison, two loan books start with the same 1 million tokens in debt, a 200,000-token reserve, and identical protection settings. The only difference is the structure of the loans: one book has a single 100,000-token default, the other has ten separate 10,000-token defaults. The total debt and reserve are the same, yet depositor losses differ by a factor of 20.
Why the gap is so wide
The key is how the reserve is applied to each default. Every default gets its own separate cover calculation, and the payout uses the minimum required cover from three fields: CoverAvailable, CoverRateMinimum, and CoverRateLiquidation. Because the cover is calculated per default, a single large default exhausts a bigger chunk of the reserve in one go, while many small defaults each trigger a smaller, separate cover release.
The numbers are stark. In the single-default case, depositors lose 90,000 tokens. In the ten-default case, they lose just 4,500 tokens. The model's code rounds cover upward and vault loss downward, which further skews the outcome. The base case assumes zero interest and fees, so the gap comes purely from the reserve mechanics, not from any extra costs.
Status on the mainnet
The figures are hypothetical, based on documented rules and the matching 3.3.0 release code announced Aug. 6. The protocol itself, LendingProtocolV1_1, is still listed as in development on the official amendment registry. As of Sept. 6, its activation on the XRP Ledger mainnet was unconfirmed.
The amendment remains in development, and its activation on mainnet is still unconfirmed as of Sept. 6. Whether the gap persists in practice will depend on how the protocol is deployed.
