Redemption Shield
The Redemption Shield is opt-in protection from normal-mode redemption. A trove with Redemption Shield enabled is not eligible for redemption during normal operation. Branch shutdown ends that protection. You pay a higher borrow rate in return.
What's a redemption? Any RD holder can swap RD for collateral at par — the mechanism that keeps RD near $1 (see Redemption for the full picture). If your trove without Redemption Shield is near the front of the queue, some of its collateral is taken and an equal gross value of debt is written off in the protocol's par accounting. Your ICR goes up rather than down, but your market-value outcome can differ and your collateral exposure is reduced on the protocol's timing, not yours. Redemption Shield lets you opt out during normal operation.
What the shield does
Redemption Shield turns redemption protection into an explicit, priced choice. When someone redeems, the protocol claims collateral from troves without Redemption Shield only, starting with the lowest-ICR one at or above MCR (troves below MCR are left for liquidation, and troves with 200 RD of debt or less are skipped); troves with Redemption Shield enabled are not touched at all in normal mode.
If you would rather pay a premium than monitor your queue position, enable Redemption Shield. If you prefer the lower base-cohort rate and accept normal-mode redemption exposure, keep it disabled.
The only path in which a trove with Redemption Shield enabled can be redeemed against is branch shutdown, where the protocol switches to a discount-based schedule that walks both books to clear the branch (see Shutdown redemption). In short: in normal mode, troves with Redemption Shield enabled are never redeemed against; in shutdown mode, they can be, on the shutdown discount schedule.
What it costs
If you enable Redemption Shield, your trove pays a surcharge on top of the branch rate. That surcharge is the visible "shield premium." It is paired with a discount for every trove without Redemption Shield on the same branch: the two halves of the same mechanism, priced off the same curve. The size of both halves depends on the branch's Redemption Shield share:
- If the Redemption Shield share is near zero, both the surcharge and the discount are tiny, protection is nearly free, and base troves see almost no benefit.
- As the Redemption Shield share of the branch grows, both halves grow: troves with Redemption Shield enabled pay more, while the effective rate for troves without it drops further below the branch rate. Below an 85% share the base rate falls linearly from the branch rate to 0% and the surcharge rises to half the branch rate. Above 85% the surcharge accelerates and the base rate turns negative, reaching −50% APY (the
_V_MAXendpoint) at a 100% share.
The share used for pricing is not the instantaneous one: it is the lower of the current share and its 12-hour EMA, scaled down on small branches (branch debt below the larger of 50,000 RD and the branch's lower soft band of global debt). Taking the lower of the two smooths increases only: a single transaction can't push the price up, but one that lowers the current share (for example, a large trove turning Redemption Shield off) lowers the priced share immediately.
Mechanically: troves with Redemption Shield enabled pay more than the branch rate; troves without Redemption Shield pay less. The surcharge and the discount are not balanced one-for-one: depending on the share, the branch's total interest can be above or below what the branch rate alone would charge. The contract only guarantees that total branch debt never shrinks through interest, even when the base rate is negative.
Here is the whole schedule at a branch rate of 4% APY — both books' rates as a function of the branch's shield share:
Left of the 85% kink, the surcharge stays at most half the branch rate while the base rate falls linearly to 0%. Past it, the shield is crowded: the surcharge accelerates and the base rate dives toward −50% APY. Explore other branch rates in the interactive version.
The full formula and constants are in Interest model. The user-side takeaway: the more crowded the shield is, the more it costs to enable, and the more attractive it is to keep Redemption Shield disabled. Both sides of the shield-share adjustment are visible on the dashboard.
Toggling
You can change your Redemption Shield setting, but not on demand — each change starts a cooldown before the next one is allowed. Toggle it on its own, or in the same transaction as a collateral/debt change.
Toggle cooldown. After any change to your Redemption Shield setting — including the choice you made when opening the trove — you must wait 24 hours before changing it again; an earlier attempt reverts. The clock is per-borrower and resets on each change. So the real rule is: at most one Redemption Shield change per 24 hours.
Internally the protocol moves your trove's collateral from one pool to the other and re-expresses your debt in the other cohort's accumulator. From your perspective it's one position; your ICR, debt and accrued interest are unchanged by the toggle itself (only the rate you accrue at from then on changes). A toggle needs a working price oracle and, while the branch is in normal mode, your trove must be at or above MCR. Toggling is not available after the branch shuts down.
Developer reference: Borrowing operations.
What redemption does to your trove
Important: getting redeemed against is not the same as being liquidated. Liquidation closes your trove and you lose the gas-comp reserve. Redemption is a forced partial close at par:
- The redeemer hands the protocol some RD.
- The protocol burns that RD against your trove's debt at par.
- The protocol sends the redeemer collateral worth that RD (at the oracle price and par), minus the branch redemption fee (0.75%), which stays in your trove.
- Your trove ends up with less debt and less collateral. Because collateral and debt fall by about the same value and your ICR was above 100%, your ICR goes up.
- If the redemption leaves your trove with only the 200 RD reserve of debt, the trove is closed and your remaining collateral is credited to you as claimable surplus. A partial redemption can also leave your trove below the usual 2,000 RD minimum; see Adjust, repay, or close.
You lose some collateral exposure (the protocol picked the moment, not you), but you're not unwound. Many users are fine with that; some aren't. Redemption Shield exists for the second group.
Choosing whether to enable Redemption Shield
- Enable Redemption Shield to avoid normal-mode redemption and remove the need to monitor queue depth, in exchange for the shield surcharge.
- Keep Redemption Shield disabled for the base-cohort rate if you accept that redemption can force a partial close at par and change your collateral exposure.
Notes
- The Redemption Shield setting survives adjustments. Only an explicit toggle changes it.
- During the bootstrap period (14 days post-deploy), redemption is disabled regardless, so the setting has no effect. Choose whichever mode you prefer when opening.
Deep dive: Interest model, shield pricing. User view of redemption itself: Redemption.