Skip to main content

Redemption

Any RD holder can exchange RD for collateral at $1 of value per RD (par, normally exactly $1.00), less small fees. This is the mechanism that puts a price floor under RD.

This page describes normal-mode redemption. When a branch or the whole system is shut down, redemption follows a different mechanism and pricing; see Shutdown redemption.

Exchange RD for Collateral​

YouRD holderProtocolRAI Dollaryou give RDRDWETHwstETHWBTCrETHweETHtBTCPAXGyou receive one basket of collateral
Redemption is a single atomic swap with the protocol: you give RD and receive one basket of collateral — a slice from every active branch in the same transaction, each RD worth $1 of value at par, minus small fees.

You give the protocol some RD. It burns that RD against the debt of one or more borrowers, gives you their collateral at the oracle price, and charges two small fees: a branch redemption fee taken out of the collateral, and a 0.25% protocol fee in RD. The borrowers end up with less debt and less collateral, and a slightly higher ICR.

If you're an arbitrageur and RD is trading below par on a DEX, you buy cheap RD, redeem at par, sell the collateral, and pocket the spread, pushing RD's market price back up. That's the floor.

What "at par" means​

For every 1 RD you redeem, you receive collateral worth 1 × par USD at the current oracle price, minus the branch redemption fee. On top, you pay the redemption protocol fee of 0.25% in RD. Example (par = $1.00, WETH = $3,000, 0.75% branch fee, as if the whole amount were redeemed on the WETH branch):

  • Redeem 3,000 RD → (3000 × $1.00) / $3,000 = 1.00 WETH of value at par, minus 0.75% in collateral fee, so you receive 0.9925 WETH.
  • Your RD balance must cover the 3,000 RD plus the 0.25% protocol fee (7.5 RD), so 3,007.5 RD is burned from your wallet.

The branch redemption fee is per-branch, fixed at deployment within the contract bounds of 0.5% to 2.5%; every mainnet branch is set to 0.75% (see Collaterals). It is denominated in collateral and is retained by the redeemed trove as residual collateral: the trove's debt drops by the full redeemed amount, but only the net-of-fee collateral leaves it, so the fee stays inside and increases the trove's post-redemption ICR. It does not flow to MOAI stakers.

The 0.25% redemption protocol fee is charged on the RD actually redeemed (rounded up). It is burned from you along with the redeemed RD, and the same amount is routed through the GlobalFeeRouter to keeper rewards, LP stakers and MOAI stakers (see Fees).

How multi-branch redemption works​

You call one function on the top-level Aggregator. It splits your RD across all active (non-shutdown) branches in proportion to each branch's base debt (debt of troves without Redemption Shield, smoothed by an EMA with a 72-hour half-life), so you receive a basket of collateral, not just one token. A branch with 50% of the system's base debt gets 50% of your redemption flow; a branch with 5% gets 5%.

1,000 RD redeemedsplits by base debt share into ↓WETH48.8%wstETH18.6%WBTC16.3%rETH10.5%weETH 5.8%WETH48.8%wstETH18.6%WBTC16.3%rETH10.5%weETH5.8%
You send RD and receive a basket of collateral, not a single token. The protocol splits your redemption across every active branch in proportion to its base debt share, then hands you that mix at the oracle price, minus the per-branch fee. A branch whose troves all have Redemption Shield enabled (tBTC here) or that is shut down (PAXG here) has zero weight and is left out. Weights shown are illustrative.

Inside each branch, redemption claims collateral from the lowest-ICR troves without Redemption Shield first and works upward. Below-MCR troves and "mini-dwarf" troves (debt at or below the 200 RD gas reserve) are skipped automatically. A trove redeemed down to its 200 RD reserve is closed, and any leftover collateral is credited to its owner as claimable surplus. Troves with Redemption Shield enabled are not touched in normal mode; only branch shutdown can route redemption through the Redemption Shield cohort book.

A revert in one branch reverts the entire redemption transaction, so scripted redemptions should account for it. A branch reverts the call if it is eligible for shutdown or its oracle has failed (it must be shut down first, which removes it from the basket). A branch may fill less than its share only when it has run out of redeemable troves; otherwise every branch must fill at least 90% as completely as the best-filled one, or the call reverts.

Developer reference: Redemption for the exact redemption call, the per-branch hint arrays, and the shutdown path.

When you can redeem​

  • After the bootstrap period. Redemption is disabled for the first 14 days after deployment. The system needs that time to settle.
  • When there is redeemable supply. The protocol enforces a redemption "quota" that refills over time. A request larger than the quota currently available reverts, so if a lot of redemption has already happened recently, you may need to wait a bit or redeem less. The quota starts empty when the bootstrap period ends. The dashboard shows live capacity (integrators: see the developer reference). Here is what the quota does during a redemption demand shock — about 1% of system debt is redeemable instantly, and capacity refills at 4% of system debt per day, so even a large wave clears within a couple of days (mechanics in Redemption mechanism):
0%4%8%12%example wave — 9% of system debt1% redeemable instantly(burst reserve)refills +4% of system debt / daywave cleared ≈ day 2day 0day 1day 2day 3redeemedwaiting for refillavailable to redeem (1% + 4%/day)
The quota is a token bucket sized in % of system debt, not a fixed number of RD. About 1% is redeemable instantly (the burst reserve) and it refills at 4% per day. A wave bigger than the bucket doesn't fail everyone at once — the excess simply waits for the refill, so even a large shock clears in a couple of days. Live capacity: Aggregator.redemptionQuotaAvailable().
  • When at least one branch has base debt. Redemption walks the base book first, by branch. If every branch has only troves with Redemption Shield enabled left, normal-mode redemption is exhausted (and you'd be looking at shutdown-mode redemption, see Shutdown redemption).

What it costs​

  • The branch redemption fee, in collateral. 0.75% on every mainnet branch (contract bounds 0.5%–2.5%), paid out of the collateral you receive.
  • The redemption protocol fee, in RD. 0.25% of the RD actually redeemed, burned from your wallet on top of the redeemed amount.
  • Gas. Each branch walk is O(troves walked). _maxIterations is a per-branch cap. Multi-branch redemption is generally more gas-intensive than a Liquity v1 redemption was.

Every redeemed RD is credited against borrower debt at par; the branch fee comes out of the collateral leg and the protocol fee is paid in RD on top.

What the redeemed borrower experiences​

Their trove ends up with less debt and less collateral, and a slightly higher ICR. They're not "liquidated", that's a different path. If the redemption takes the trove's debt down to the 200 RD reserve, the trove is closed and its remaining collateral is credited to the borrower as claimable surplus. A partial redemption can leave a trove below the usual 2,000 RD minimum debt. See Redemption shield for how borrowers can opt out.

They also keep the branch redemption fee. The fee is taken in collateral but stays inside the redeemed trove as residual collateral, which raises its post-redemption ICR, a small compensation for being chosen. The one exception: while a shut-down branch has bad debt (a bad-debt sink), that fee is instead charged in RD and used to pay down the bad debt, together with an extra 0.5% surcharge on the redemption. See bad-debt sink.

Shutdown redemption​

When a branch is shut down (or the whole system is), redemption switches to a different pricing schedule. See Shutdown redemption.

Deep dive​

Redemption mechanism covers the full per-branch walk, basket weights, hint construction, Redemption Shield and base bookkeeping, and bad-debt-sink branch handling.