1. Minimum backing and posted backing
Every live position has two different backing numbers:- the minimum backing required for that request,
- the amount the solver actually posts.
2. Why solvers often post more than the minimum
Posting only the minimum leaves very little room for the book to breathe.- reduced chance of forced backing liquidation,
- more room for floating costs to move,
- more time to migrate to a better venue,
- more resilience if the borrower closes at an inconvenient time.
3. When backing is still healthy
A position can lose backing health before backing reaches zero. Health is one check: drawdown from accumulated floating losses, measured against the posted backing, must stay within the protection threshold chosen at origination (the bond LLTV). A quote can only use a bond LLTV the protocol has enabled; on Ethereum mainnet that is 90%. A position can still look funded in absolute terms while already being too far underwater relative to the remaining backing.4. When a solver can remove backing
Solver backing can come back out only when it is truly excess. In practice:- posted backing must still sit above the required floor after the withdrawal,
- the position still has to remain healthy after the withdrawal,
- floating losses cannot already be eating through that apparent excess,
- open positions can still need meaningful backing even after maturity, until their bond requirement is zero.
5. How losses hit backing
When a position is closed or forcibly liquidated, IRIS compares what the borrower owes under the fixed terms with what the venue actually cost. If venue funding ended up more expensive than the borrower obligation, solver backing absorbs that shortfall first. If venue funding ended up cheaper, the solver keeps the positive spread, and any recognized collateral-side surplus is booked separately as solver value. The protocol fee takes its share of both before they reach the solver. If the shortfall is larger than the remaining backing, someone closing the position still has to cover the residual debt-side gap. Backing can also be hit before the close, when a venue liquidation is recognized. Repayment the liquidation retires over the principal is floating interest the borrower’s collateral paid: it nets against the fixed leg, and the excess is refunded from the backing to the borrower’s claimable balance, a wipe of the whole position included. The refund is capped at the value of the collateral the borrower lost. Backing slashed below its required floor cannot be withdrawn while the venue debt remains, so the solver’s exit is to repay. A slash that exhausts the backing zeroes the bond requirement and forfeits the surplus, as a distress liquidation would. Once the venue debt is fully retired, the bond requirement is zero and the floor no longer applies.6. Backing distress liquidation
If backing health fails, anyone can force a distress liquidation. That waterfall is simple:- slash solver backing,
- repay as much venue debt as possible with the slashed amount,
- pay the liquidator incentive,
- end fixed-rate protection for the position.
maturity + overduePeriod or recoverable in full with escape at any time.
7. How to think about capacity
For operations, it helps to separate four buckets:- minimum required backing,
- posted backing currently committed to protection,
- true excess backing that could be removed without harming health,
- realized economics that are already claimable but are not the same thing as free backing capital.

