Shutdown redemption
When a branch is shut down, redemption against that branch switches to a different pricing schedule designed to clear the branch's debt quickly. Other branches keep operating on normal-mode redemption.
When this is relevant
You'll see shutdown-mode redemption if:
- A specific branch was shut down (triggered because its TCR fell below SCR, because its price feed failed, or because its collateral custody failed: a collateral pool holds less than its ledger says, or a blacklistable collateral can no longer be transferred out of a pool).
- The whole system is shut down (every branch in shutdown state).
In both cases you can still redeem on that branch; it is the primary path by which the protocol returns collateral to RD holders as the branch winds down. New borrows on a shut-down branch are blocked, and interest stops accruing on it.
What changes vs. normal redemption
Four things:
- Pricing. Normal mode uses the oracle price minus the branch redemption fee. Shutdown mode charges no branch redemption fee and no 0.25% protocol fee; instead it applies a time-based price multiplier to how collateral is valued (against the branch price, or the last good price if the oracle failed) — starting slightly against the redeemer and ramping steadily in their favor. The growing discount is what draws redeemers in to wind the branch down.
- Troves with and without Redemption Shield can be redeemed. Normal-mode redemption walks only the base list. Shutdown-mode redemption walks both cohort lists together in ascending ICR order, on the same pricing curve.
- No quota and no bootstrap gate. Shutdown redemptions are not limited by the redemption quota, and the 14-day bootstrap restriction does not apply to them.
- One branch at a time. You redeem directly against the shut-down branch, not through the Aggregator's basket.
The discount schedule
The exact discount you get depends on why the branch was shut down and how long ago:
| Trigger | Starting point | Maximum discount | Ramp window |
|---|---|---|---|
| TCR fell below SCR, or collateral custody failed | 1% premium | 5% | 1 day |
| Oracle failure | same first-day ramp | ≈ 100% | 14 days |
Pricing starts at a 1% premium. Shutdown redemptions are not rate-limited by the redemption quota, so a discount that was instantly profitable would make forcing a shutdown a prize that scales with the size of the branch — the premium start removes that incentive. The first hour ramps quickly from the 1% premium to a 1% discount (crossing break-even about 30 minutes in); from that kink it continues more gently:
- A TCR-below-SCR or collateral-failure shutdown reaches its 5% discount cap after one day and holds there. A 5% discount means the collateral you receive is valued 5% below oracle — about $105 of collateral per 100 RD at par.
- An oracle-failure shutdown follows the identical ramp for the first day, then keeps deepening toward ~100% at day 14. The branch has no reliable price, so the protocol lets redeemers accept ever-larger discounts — receiving ever more collateral per RD — until the branch clears. If the oracle of a branch already shut down for another cause fails later, the deeper curve starts from the moment of that failure.
Both causes share the identical first day — a 1% premium at shutdown, a 1% discount by the end of the first hour, and a 5% discount by day one. A TCR-below-SCR or collateral-failure shutdown then holds at 5%; an oracle-failure shutdown keeps deepening toward ~100% by day 14, since the branch has no trusted price and pays out whatever collateral remains. Explore either with a cursor in Collateral shutdown.
What you do
Normal-mode redemption automatically excludes shut-down branches (they drop out of the basket weights), so a normal redemption call never accidentally hits one. To redeem from a shut-down branch, you (or your front end) call that branch's Redemptions.redeemCollateralForShutdown(amount, maxIterations) directly. It takes no hints: the protocol works out where partially redeemed troves are reinserted.
Developer reference: Redemption for the shutdown path and triggers.
Timing considerations
For TCR-below-SCR and collateral-failure shutdowns, the protocol discount reaches its maximum of 5% after one day and does not increase after that. Execution conditions and the amount of collateral still available can continue to change.
For oracle-failure shutdowns, waiting increases the protocol discount, but the branch may run out of redeemable collateral first. Other redemptions can consume some or all of the collateral before your transaction executes.
What if the discount eats too much?
For the first half hour after a shutdown, pricing sits at a premium: the payout is smaller than the RD you redeem. That's deliberate. Shutdown redemption bypasses the redemption quota, so an instantly profitable discount would reward whoever could force a shutdown — a prize that scales with branch size. The premium start makes a forced shutdown worthless to its instigator. Once the ramp crosses break-even (≈ 30 minutes in), the discount is in your favor and grows from there.
In shutdown, the branch pays out what it can under this pricing schedule to clear debt. Redemption is optional: RD remains transferable, and other branches may still be operating normally.
Deep dive
Collateral shutdown covers the full trigger surface, the cross-branch effects, how the Aggregator excludes shut-down branches from issuance quotas, drips, and basket weights, and what happens to debt left over once a branch's collateral is gone.