# SpiceUSD Documentation

## Official Liquity V2 fork on Blast

<figure><img src="https://3456306496-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLAJRqJBYPF3BKLJ4cnWh%2Fuploads%2FR4Vkbu95ZBEQaCHBtnYc%2FSpice%20USD%20(full%20logo).jpg?alt=media&amp;token=b6f86db1-5e47-4060-b671-f45bac9cbb35" alt=""><figcaption></figcaption></figure>

SpiceUSD is an official fork of Liquity V2, which is a decentralized borrowing and stablecoin protocol that builds on the success of V1.

It enhances it in several ways to offer the best borrowing experience, a highly resilient Blast-native stablecoin (SPICE), and sustainable on-chain yield.


# General

### What is SpiceUSD? <a href="#what-is-liquity-v2" id="what-is-liquity-v2"></a>

SpiceUSD is an official fork of Liquity v2.

Liquity v2 is a decentralized borrowing protocol that lets users deposit tokens as collateral, and mint the stablecoin BOLD. In SpiceUSD, the stable coin to mint is SPICE.

There are two main use-cases:

* Borrow SPICE
* Earn yield by depositing SPICE

### Does SpiceUSD have governance? <a href="#does-liquity-v2-have-governance" id="does-liquity-v2-have-governance"></a>

SpiceUSD is subject to minimal governance which is solely tasked with distributing Protocol Liquidity Incentives (PIL), directing 25% of the protocol's revenue to external initiatives.

Governance has no other functions or powers, as SpiceUSD's smart contracts are immutable and not upgradeable.


# Borrowing and Liquidation

### What makes borrowing in SpiceUSD so unique? <a href="#what-makes-borrowing-in-v2-so-unique" id="what-makes-borrowing-in-v2-so-unique"></a>

Pioneering user-set interest rates, SpiceUSD allows users to borrow the stablecoin SPICE on their own terms. Borrowers can choose and adjust the rate they are willing to pay for their loans. Borrowers will establish market rates in accordance with their individual risk tolerance without relying on governance or algorithm rate management. Each collateral will also have their own respective borrow market which allows room for a market of rates to develop.

SpiceUSD builds on the fundamentals that Liquity V1 introduced - a highly secure and immutable protocol which issues the most decentralized stablecoin in all of crypto.

All of this makes for a highly capital efficient, secure and decentralized borrowing experience which cannot be matched anywhere else.

### What is a Trove? <a href="#what-is-a-trove" id="what-is-a-trove"></a>

A Trove is SpiceUSD version of a 'vault'. Each Trove is linked to an Blast address, and each address can have multiple Troves.

Each Trove allows you to manage a loan, adjusting collateral and debt values as needed, as well as setting your own interest rate.

### What types of collateral can I use? <a href="#what-types-of-collateral-can-i-use" id="what-types-of-collateral-can-i-use"></a>

You are able to use WETH, USDB, BLAST, FNX, HYPER and THRUST

### Is there a minimum debt? <a href="#is-there-a-minimum-debt" id="is-there-a-minimum-debt"></a>

Yes, a minimum debt of 100 SPICE is required for borrowing.

### **When do I need to pay back my loan?** <a href="#when-do-i-need-to-pay-back-my-loan" id="when-do-i-need-to-pay-back-my-loan"></a>

Loans issued by the protocol do not have a repayment schedule. You can leave your Trove open and repay your debt any time, as long as you maintain a healthy LTV.

### Is there a lockup period? <a href="#docs-internal-guid-e33469f8-7fff-3873-3b78-742f370cf298" id="docs-internal-guid-e33469f8-7fff-3873-3b78-742f370cf298"></a>

There is no lockup period. Users are free to withdraw their collateral deposits whenever they want. As an exception, withdrawals by borrowers are temporarily suspended if the total LTV of a borrow market goes above 75%.

### How do I decide on my LTV? <a href="#how-do-i-decide-on-my-ltv" id="how-do-i-decide-on-my-ltv"></a>

This depends on your personal preferences, primarily your risk tolerance and how actively you want to manage your position(s). To help with the decision, you'll find preset options on the user interface that can serve as a guide.

![](https://docs.liquity.org/~gitbook/image?url=https%3A%2F%2F2342324437-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FE2A1Xrcj7XasxOiotWky%252Fuploads%252FKYV7j08QhkPfeWdSZCE5%252Fltv_preset.png%3Falt%3Dmedia%26token%3D98dda88c-18ee-4993-9993-ece6d9242a86\&width=768\&dpr=4\&quality=100\&sign=6093ec1\&sv=2)

LTV quick-selection options

Please note that these examples are for illustration purposes only and do not represent definitive risk or safety thresholds. It's essential to determine your own risk tolerance and comfort level as a user.

If your LTV becomes too high, your position will be liquidated.

### How do Liquidations work in SpiceUSD? <a href="#how-do-liquidations-work-in-liquity-v2" id="how-do-liquidations-work-in-liquity-v2"></a>

Troves get liquidated if the LTV goes above the maximum value (for example, 80% for WETH).

SpiceUSD uses Stability Pools as its primary liquidation mechanism to absorb liquidated debt and collateral. Each borrow-market has its own dedicated Stability Pool earning liquidation gains (in the respective collateral) in exchange for burning debt.

Just-In-Time liquidations and a redistribution of debt and collateral across borrowers of the same market handle liquidations as a last resort when the Stability Pool is empty.

A liquidated borrower usually incurs a penalty of 5% and will be able to claim the remaining collateral after liquidation.

A special case is when a Redistribution is necessary, then:

* For ETH, the loss amounts to 10% of the debt (at most). That corresponds to a max. loss of 9.09% expressed in terms of collateral.
* For rETH/wstETH the loss is 20% of the debt, corresponding to a max. loss of 16.67% expressed in terms of collateral.

![](https://docs.liquity.org/~gitbook/image?url=https%3A%2F%2F2342324437-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FE2A1Xrcj7XasxOiotWky%252Fuploads%252FhaTvXYC1FTrAwmfXQZ14%252Fliqtable.png%3Falt%3Dmedia%26token%3Da2ab7753-5fd6-4741-8c43-871fc704aa1a\&width=768\&dpr=4\&quality=100\&sign=fba442d0\&sv=2)

### How am I compensated for liquidating a Trove? <a href="#how-am-i-compensated-for-liquidating-a-trove" id="how-am-i-compensated-for-liquidating-a-trove"></a>

The liquidation of Troves is connected with certain gas costs which the initiator has to cover. The protocol offers a gas compensation given by the following formula:

`0.0375 WETH + min(0.5% trove_collateral, 2_units_of_LST_or_WETH)`

The `0.0375 WETH` is funded by a [refundable gas deposit](#what-is-the-refundable-gas-deposit) while the variable `0.5%` part comes from the liquidated collateral, slightly reducing the liquidation gain for Stability Providers.

### What is the max Loan-To-Value (LTV)? <a href="#what-is-the-max-loan-to-value-ltv" id="what-is-the-max-loan-to-value-ltv"></a>

That depends on the collateral type you will use.

ETH will have a LTV of 90.91% while wstETH and rETH will have it at 83.33%.

### What is the refundable gas deposit? <a href="#what-is-the-refundable-gas-deposit" id="what-is-the-refundable-gas-deposit"></a>

To open a new Trove, the protocol requires a liquidation reserve of 0.0375 ETH regardless of the chosen collateral, which is set aside to cover the gas costs of a potential liquidation. The deposit is returned when the Trove is closed by the user (including upon redemptions).

### How much will I pay for my loan? <a href="#how-much-will-i-pay-for-my-loan" id="how-much-will-i-pay-for-my-loan"></a>

In SpiceUSD, there are no upfront fees. Instead, you pay interest on an ongoing basis, making it suitable for short-term loans as well.

The interest you pay is determined by the rate you set yourself. For example, if you borrow 10,000 SPICE at a 5% interest rate, you'll pay \~500 SPICE in interest after one year. This interest is added to your outstanding debt.

### What are user-set rates? <a href="#what-are-user-set-rates" id="what-are-user-set-rates"></a>

In SpiceUSD, users can set their own interest rates, giving them full control over costs and improving predictability. This feature allows for adaptability to various market conditions and helps stabilize BOLD's peg.

User-set interest rates facilitate a capital-efficient equilibrium between SPICE borrowers and holders in a fully market-driven manner. Additionally, these rates serve as the primary revenue source for SPICE holders, generating a continuous, sustainable real yield for SPICE depositors and liquidity providers.

Borrowers should set their rates based on their [redemption](/faq/redemptions-and-delegation) risk tolerance.

Read more about setting your rates [here](https://www.liquity.org/blog/interest-rate-management-in-liquity-v2).

### Can I adjust the rate? <a href="#can-i-adjust-the-rate" id="can-i-adjust-the-rate"></a>

Yes, you can always adjust your interest rate at any time. Since you as a user get to set your own interest rate, you have full autonomy over your borrowing costs.

Note however, that a fee corresponding to 7 days of average interest is charged when opening the loan, as well as on any rate adjustments that happen less than 7 days after the last adjustment. Without it, low-interest rate borrowers could evade redemptions by sandwiching a redemption transaction with both an upward and downward interest rate adjustment, which in turn would unduly direct the redemption against higher-interest borrowers.

### How do I decide on the right rate for me? <a href="#how-do-i-decide-on-the-right-rate-for-me" id="how-do-i-decide-on-the-right-rate-for-me"></a>

Setting an interest rate determines a user’s redemption risk and needs to be aligned with your goals and how actively you want to manage your position.

Users can also decide to delegate interest rate management to a third party, who can set your interest rate and charge a fee for this service (see [link](/faq/redemptions-and-delegation)).

By opting to manage your own rate, you will have to weigh the savings from a lower rate against the higher redemption risk and the increased adjustment frequency with potential additional costs (premature adjustment fees and gas costs).

Since redemptions are performed in ascending order of interest rate (for the respective collateral asset), you will typically want to keep a buffer of other borrowers with lower rates in front of you. Choosing higher rates may increase the recurring costs of your loan, but give you peace of mind regarding unexpected market fluctuations.

You can see the distribution of other users’ rates in a histogram and position yourself accordingly.

![](https://docs.liquity.org/~gitbook/image?url=https%3A%2F%2F2342324437-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FE2A1Xrcj7XasxOiotWky%252Fuploads%252FHkqGvdaJxndhC8uhzLw0%252Frerwere.png%3Falt%3Dmedia%26token%3D796599d0-6785-4cd2-ad6a-bad02d062f45\&width=768\&dpr=4\&quality=100\&sign=c26f7d49\&sv=2)

Redemptions usually occur when SPICE is trading below $1 minus the current redemption fee. Keeping an eye on the past [redemption activity](/faq/redemptions-and-delegation) can help you assess the overall redemption risk, serving as an additional data point for your rate selection.

In general, those willing to actively monitor their positions, or borrowing for shorter periods of time, may opt for lower rates. Conversely users optimizing for a more passive, long-term position would be better off with setting a higher relative interest rate.

### What could the average interest rate be? <a href="#what-could-the-average-interest-rate-be" id="what-could-the-average-interest-rate-be"></a>

These will be set, continuously, by the market and will vary over time. We would expect that, on average, rates should be similar to borrowing on Sky or Aave using ETH or staked ETH. However, due to the flexibility of user-set rates, it is possible that some users will pay significantly lower rates during certain periods.

Given that 75% of the interest revenue is directly paid out to SPICE depositors , we further expect that stablecoin deposit yields should be comparable, if not higher than what competing CDP’s and lending markets offer. Thanks to the attractiveness of SPICE and assuming the emergence of external use cases (monetary premium), this could lead to lower borrow rates overall than offered by other platforms. Learn more about the spread between borrowers and lenders in this [article](https://www.liquity.org/blog/liquity-v2-a-de-facto-reference-rate-for-defi).

### What determines the riskiness of my Trove? <a href="#what-determines-the-riskiness-of-my-trove" id="what-determines-the-riskiness-of-my-trove"></a>

There are two key parameters to consider:

* **Loan-to-value (LTV)**: This is based on your debt-to-collateral ratio and affects your risk of [liquidation](#how-do-liquidations-work-in-liquity-v2).
* **Interest rate (IR)**: You set this rate yourself, and it influences your risk of being [redeemed](/faq/redemptions-and-delegation).

You have the flexibility to set these parameters as you see fit, allowing you to control the relative riskiness of each Trove. You can create multiple Troves under the same address, enabling you to manage different risk profiles for different portions of your portfolio.

![](https://docs.liquity.org/~gitbook/image?url=https%3A%2F%2F2342324437-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FE2A1Xrcj7XasxOiotWky%252Fuploads%252FPtoSsrpN4nxIZviPrc1s%252FLoan%2520personas.png%3Falt%3Dmedia%26token%3D649cb0e4-eb3e-44e4-8fe6-4432dbaed967\&width=768\&dpr=4\&quality=100\&sign=bb12995f\&sv=2)

### Are there any other fees related to borrowing? <a href="#are-there-any-other-fees-related-to-borrowing" id="are-there-any-other-fees-related-to-borrowing"></a>

To impede Trove redemption evasion strategies where borrowers try to minimize their interest payments in an unfair manner, a small “premature adjustment fee” is charged on interest rate changes that happen within less than 7 days since the last adjustment (or the opening of the Trove). The premature adjustment fee is equal to 7 days of average interest on the respective borrow market. Note that this fee differs from the user’s set interest rate.

The fee is denominated in SPICE and added to the Trove's debt. The same fee is charged when a new Trove is opened or when its debt is increased (only affecting the added debt).

### How many Troves (loans) can I open with the same address? <a href="#how-many-troves-loans-can-i-open-with-the-same-address" id="how-many-troves-loans-can-i-open-with-the-same-address"></a>

You can have multiple open Troves for the same collateral or across different collateral types, all represented as separate NFTs.

### Are Troves transferable? <a href="#are-troves-transferable" id="are-troves-transferable"></a>

Yes, they are represented as a NFT (ERC-721), hence easily transferable between wallets. When you send the NFT you also send full access to your Trove and all the funds within it.

Please note that more advanced strategies like ‘selling’ Trovess on secondary markets like OpenSea comes with inherent risks, and caution is advised.

### How do I loop my exposure? <a href="#how-do-i-loop-my-exposure" id="how-do-i-loop-my-exposure"></a>

Looping allows you to borrow SPICE against your deposited collateral and use it to buy more collateral, increasing your exposure to the underlying. SpiceUSD comes with built-in automation to achieve this with one click (zappers).

Make sure you choose a frontend that supports this functionality, and be mindful of liquidity / slippage.

### How are collateral risks mitigated? <a href="#how-are-collateral-risks-mitigated" id="how-are-collateral-risks-mitigated"></a>

SpiceUSD will have three separate borrow markets for the different collateral types with their own Stability Pools (for efficient liquidations), user-set interest rates, and LTV factors for their respective assets.

Risks are mitigated through temporary borrowing restrictions in times of low collateralization of a given market, a redemption logic prioritizing collateral with less Stability Pool backing, and a collateral shutdown as an emergency measure to maintain system balance and protect against market instability.

Keep in mind that despite all these measures, SPICE remains dependent on the three mentioned collateral assets and there is no strict guarantee that it remains over-collateralized in case of a sudden collapse of a collateral asset.

### What mechanisms are in place if the Stability Pool is empty? <a href="#what-mechanisms-are-in-place-if-the-stability-pool-is-empty" id="what-mechanisms-are-in-place-if-the-stability-pool-is-empty"></a>

If the Stability Pool doesn’t cover the full entire debt and gets completely emptied by the liquidation, the system falls back to the following liquidations modes.

The liquidator can freely choose between two fallback liquidation modes for the debt exceeding the funds in the Stability Pool:

1. Just-in-time (JIT) liquidation: the liquidator sends an amount of SPICE corresponding to the (remaining) debt in exchange for 105% of its nominal value in (staked) token.
2. Redistribution: the liquidator triggers a redistribution, through which the Trove’s entire debt and collateral is redistributed to all fellow borrowers of the respective collateral market, in proportion to their own collateral amounts. Thus, the respective borrowers will receive a share of the liquidated collateral and see their debts increase proportionally.


# SPICE & Earn

### What is SPICE? <a href="#what-is-bold" id="what-is-bold"></a>

SPICE is the USD-pegged stablecoin issued in SpiceUSD. It’s fully decentralized, over-collateralized and backed by collateral in the protocol.

In contrast to most of its competitors, SPICE is a resilient stablecoin by design:

* only backed by crypto assets (no real world assets or custody by centralized players)
* not subject to collateral changes and protocol upgrades (immutable)
* directly redeemable (always convertible in a fast and liquid way)

### What are SpiceUSD's main benefits compared to other stablecoins? <a href="#what-are-bolds-main-benefits-compared-to-other-stablecoins" id="what-are-bolds-main-benefits-compared-to-other-stablecoins"></a>

* SPICE uses only the most decentralized assets as collateral - like WETH, USDB and THRUST
* It is always redeemable for the underlying assets, meaning you can always swap it as if worth $1, for the collateral backing it
* The contracts used to issue SPICE are immutable, not allowing any changes and significantly reducing attack vectors
* SPICE has native incentives via Protocol Incentivized Liquidity directed by governance, ensuring that there will always be sufficient liquidity to handle transactions

### What is SPICE's peg mechanism? <a href="#what-is-bolds-peg-mechanism" id="what-is-bolds-peg-mechanism"></a>

SpiceUSD's market-driven monetary policy through user-set interest rates enables SPICE's peg to dynamically respond to situations where the token is above or below $1.

When SPICE trades above $1, borrowers tend to reduce their rates due to lower [redemption](/faq/redemptions-and-delegation) risk, making borrowing more and holding SPICE less attractive. This helps correct the price downwards.

In contrast, when SPICE trades below $1, arbitrageurs will initiate redemptions to restore the peg. Moreover, borrowers' exposure to redemption risk prompts them to increase interest rates, boosting demand for SPICE (and Earn deposits) and pushing its price upward.

![](https://docs.liquity.org/~gitbook/image?url=https%3A%2F%2F2342324437-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FE2A1Xrcj7XasxOiotWky%252Fuploads%252FOPagS0zx2PSCiAFmH8Uq%252Flight%2520-%2520BOLD%2520peg%2520mechanism.png%3Falt%3Dmedia%26token%3Dfcc3163a-a96d-4085-a1ea-d5c4606ab3b7\&width=768\&dpr=4\&quality=100\&sign=37ed4c8c\&sv=2)

### How can I earn with SpiceUSD? <a href="#how-can-i-earn-with-liquity-v2" id="how-can-i-earn-with-liquity-v2"></a>

* Stability Pool deposits (Earn): Earn protocol revenue by depositing SPICE into the various Stability Pools.
* Protocol Incentivized Liquidity (PIL): Supply liquidity for SPICE onto the incentivized external DEXes.

### Where does the yield for Earn come from? <a href="#where-does-the-yield-for-earn-come-from" id="where-does-the-yield-for-earn-come-from"></a>

The yield comes from two sources:

* **Interest payments:** Each borrow-market funnels 75% of the of its revenue to its Stability Pool depositors (Earners). This is paid out in SPICE.
* **Liquidation gains:** Your SPICE will be used to liquidate under-collaterized loans, effectively buying their collateral with a \~5% discount. This is paid out in (staked) collateral token.

All the yield is fully sustainable, scalable and “real”, with no token emissions and lockups.

### Is there a lockup period? <a href="#docs-internal-guid-e33469f8-7fff-3873-3b78-742f370cf298" id="docs-internal-guid-e33469f8-7fff-3873-3b78-742f370cf298"></a>

There is no lockup period. Users are free to withdraw their SPICE deposits whenever they want.

### What is the estimated yield on Earn? <a href="#docs-internal-guid-9adfe211-7fff-6cdc-ba63-258b45131fbf" id="docs-internal-guid-9adfe211-7fff-6cdc-ba63-258b45131fbf"></a>

The yield is a representation of the rates borrowers are paying. Since 75% of the borrowers’ interest payments go to Earn, the effective yield can exceed the average interest rate paid in a borrow market if less than 75% of the SPICE supply is deposited to the respective Stability Pool. This yield amplification sets SpiceUSD apart from competitors and money markets where lending rates cannot be higher than borrow rates.

Check historic rates our Dune Dashboard (currently in preparation).

### Why are there multiple Stability Pools? <a href="#why-are-there-multiple-stability-pools" id="why-are-there-multiple-stability-pools"></a>

The goals are to:

* Establish separate borrow markets for different collateral assets with their own market driven interest rates, using the Stability Pool backing to dynamically split [redemptions across the available collaterals](/faq/redemptions-and-delegation).
* Compartmentalize the risks as much as possible when depositing to the respective Stability Pools (Earn) by giving the depositors control over which collateral assets they want exposure to in case of liquidations.

### How do risks differ for the different Stability Pools? <a href="#how-do-risks-differ-for-the-different-stability-pools" id="how-do-risks-differ-for-the-different-stability-pools"></a>

Users can deposit their stablecoins into the Stability Pool of their choice, aligning with their risk preference and the types of collateral they're comfortable being exposed to. By selecting pools associated with specific collateral tokens, participants can tailor their risk exposure and potential reward profile.

By offering separate pools for different collateral types, the system allows users to choose their exposure based on the perceived risk and potential return. This compartmentalization helps manage systemic risk, ensuring that impacts from liquidations in one asset class don't disproportionately affect the entire ecosystem.

It is important to note that all SPICE holders including depositors still remain dependent on SPICE to keep its peg, remaining exposed to the collateral tokens.


# Redemptions and Delegation

### What are redemptions? <a href="#what-are-redemptions" id="what-are-redemptions"></a>

Redemptions serve the crucial purpose of keeping SPICE pegged to the US Dollar, creating a price floor around $1. They do this in a decentralized way without reliance on centralized assets or 3rd parties.

A redemption is essentially swapping SPICE for collateral tokens at face value, as if 1 SPICE is exactly worth $1. Redemptions can be initiated by anyone, but are only profitable when SPICE <$1.

The redeemer sends SPICE to the protocol and in return gets a mix of collateral tokens (minus the redemption fee). The redeemed amount is split among the different collateral assets based on their current Stability Pool backing (see [link](#docs-internal-guid-6cda6d73-7fff-78b8-1c4f-6cb96385a98a) for more info).

![](https://docs.liquity.org/~gitbook/image?url=https%3A%2F%2F2342324437-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FE2A1Xrcj7XasxOiotWky%252Fuploads%252F0XdFvKy05sdM3JClXcI5%252Flight%2520-%2520BOLD%2520individual%2520redemption.png%3Falt%3Dmedia%26token%3D3037c032-5464-4614-b206-d9d5157c0228\&width=768\&dpr=4\&quality=100\&sign=abb38c31\&sv=2)

Redemptions start from the borrower paying the least interest.

Read more about how to [protect yourself ](#how-can-i-stay-protected)from redemptions and what happens if [you are redeemed](#what-happens-if-my-trove-gets-redeemed).

You can also watchi this [9 min video](https://www.youtube.com/watch?v=CQVmjFx987A) on redemptions.

### What happens if two Troves have the same IR? <a href="#docs-internal-guid-85409cf3-7fff-2712-b20f-92b229718cbb" id="docs-internal-guid-85409cf3-7fff-2712-b20f-92b229718cbb"></a>

In this case, the "Last In, First Out" (LIFO) principle applies, meaning the Trove that set its interest rate more recently will be redeemed first.

### When can redemptions occur? <a href="#docs-internal-guid-85409cf3-7fff-2712-b20f-92b229718cbb-1" id="docs-internal-guid-85409cf3-7fff-2712-b20f-92b229718cbb-1"></a>

A redemption can occur at any time, but will likely only happen when it is profitable to do so. This is usually the case when the price of SPICE is less than $1 (minus the current redemption fee).

### Who can initiate a redemption? <a href="#docs-internal-guid-595b4008-7fff-7d35-9a38-68d9e7feef1a" id="docs-internal-guid-595b4008-7fff-7d35-9a38-68d9e7feef1a"></a>

Any Ethereum address can initiate a redemption, provided that they have a sufficient amount of SPICE to do so. However, we expect redemptions to be mainly performed by professional bots rather than humans.

### What happens if my Trove gets redeemed? <a href="#what-happens-if-my-trove-gets-redeemed" id="what-happens-if-my-trove-gets-redeemed"></a>

You can think of redemptions as if somebody else is repaying your debt and retrieving an equivalent amount of your collateral in return.

If your collateral is redeemed, an equivalent amount of your debt in USD terms is repaid. The redeemer receives your collateral, less the redemption fee, which remains in your Trove. This means that at the time of redemption you have not lost any money in USD terms, likely even made a small gain with the received redemption fee as the peg recovers.

Example with ETH at $3,000:

* Before the redemption: 10 ETH collateral, 20,000 SPICE debt.
* After the redemption: 5.025 ETH collateral, 5,000 SPICE debt.

You can see your collateral and debt reduced equally (in USD terms) and the redemption fee (0.025 ETH) being added to your collateral value.

Partially affected Troves whose debt stays above the minimum debt threshold of 2000 SPICE continue to work as before, while Troves whose debt is reduced to a lesser amount (or 0) switch to a dormant operating mode (see below for [more](#docs-internal-guid-927901d5-7fff-c7a0-2e9f-964ab271257a) info).

### How do redemptions work using three collateral assets? <a href="#docs-internal-guid-6cda6d73-7fff-78b8-1c4f-6cb96385a98a" id="docs-internal-guid-6cda6d73-7fff-78b8-1c4f-6cb96385a98a"></a>

In contrast to LUSD, SPICE is backed by a multitude of collaterals. Instead of letting the redeemer freely choose the collateral to redeem, SpiceUSD optimizes the process for economic safety. Redemptions are thus serviced through a collateral mix in a way that enhances the overall backing of SPICE.

The process starts with the Troves paying the lowest interest rates in each collateral market and continues until the full amount of SPICE is exchanged for collateral assets. Redemptions can be partial or full, as illustrated below.

In this example, the rETH market shows a full redemption of the first Trove and a partial redemption of the second. The wstETH and ETH markets have one partial and two full redemptions, respectively

![](https://docs.liquity.org/~gitbook/image?url=https%3A%2F%2F2342324437-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FE2A1Xrcj7XasxOiotWky%252Fuploads%252FJtx0jgGBkGisNExyXZ5a%252Fredemption%2520split%25202.png%3Falt%3Dmedia%26token%3D79f895c0-290c-41e9-9aeb-b3fa5a3709f5\&width=768\&dpr=4\&quality=100\&sign=17e818d8\&sv=2)Example redemption across all three collateral markets

### How is the collateral split determined? <a href="#how-is-the-collateral-split-determined" id="how-is-the-collateral-split-determined"></a>

The split is dynamic, optimizing for the economic safety of the system. The logic is straightforward: the riskier a collateral is, the more redemption volume is directed to that market. In other words, if a market's Stability Pool is relatively small compared to its total debt, it's considered riskier, as there's a higher likelihood of bad debt occurring in extreme events.

To mitigate this risk, the system redeems proportionally to the "outside debt" of each collateral type. This is calculated as the total debt borrowed against a specific collateral minus the size of the Stability Pool for that borrowing market.

Here is an example: given outside debt amounts of 100 SPICE, 50 SPICE and 100 SPICE respectively, a redemption will result in a 40% (WETH), 20% (wstETH) and 40% (rETH) split.

![](https://docs.liquity.org/~gitbook/image?url=https%3A%2F%2F2342324437-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FE2A1Xrcj7XasxOiotWky%252Fuploads%252FjSQv4scadWPAaEtb0whz%252Fredeem2.png%3Falt%3Dmedia%26token%3D6b7dc320-1b97-4cd7-9ad1-1afbbb7c70fe\&width=768\&dpr=4\&quality=100\&sign=eeabe72d\&sv=2)

### Is there a redemption fee? <a href="#is-there-a-redemption-fee" id="is-there-a-redemption-fee"></a>

Yes. The redemption fee mechanics are broadly the same as in Liquity V1, but with adapted parametrization leading to a faster fee decay. The redemption fee is taken as a cut of the total collateral tokens drawn from the system in a redemption. Contrary to V1, the fee does not go to the LQTY stakers but stays with the users as part of their collateral.

Redemption fees are based on the `baseRate` state variable, which is dynamically updated. The `baseRate` increases with each redemption, and exponentially decays according to time passed since the last redemption (half-life of 6 hours).

Upon each redemption of x SPICE: `baseRate` is decayed based on time passed since the last fee event and incremented by an amount proportional to the fraction of the total SPICE supply to be redeemed, i.e. `x/total_spice_supply`

The redemption fee percentage is given by `min (0.5% + baseRate, 100%)`.

![](https://docs.liquity.org/~gitbook/image?url=https%3A%2F%2F2342324437-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FE2A1Xrcj7XasxOiotWky%252Fuploads%252FoS6SRJ41pw82HYtf9Wd2%252Fredem.png%3Falt%3Dmedia%26token%3D244f49b2-3587-4d26-bb9e-b90b9713361d\&width=768\&dpr=4\&quality=100\&sign=59cf6c\&sv=2)

The redemption fee (red line) follows this dynamic over time as redemptions occur (blue bars).

### How can I stay protected? <a href="#how-can-i-stay-protected" id="how-can-i-stay-protected"></a>

The risk of redemption depends on two factors: the interest rate you set and the price of SPICE.

**The interest rate** you set determines how much SPICE must be redeemed before it's your turn. The higher your rate, the more SPICE is redeemable before you, and vice versa.

You can see this on any frontned, in the example below the number is 41M.

![](https://docs.liquity.org/~gitbook/image?url=https%3A%2F%2F2342324437-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FE2A1Xrcj7XasxOiotWky%252Fuploads%252FHkqGvdaJxndhC8uhzLw0%252Frerwere.png%3Falt%3Dmedia%26token%3D796599d0-6785-4cd2-ad6a-bad02d062f45\&width=768\&dpr=4\&quality=100\&sign=c26f7d49\&sv=2)

This means that 41M SPICE must be removed from the system before it would reach you. However, this number is relative, and you also need to consider recent redemption activity. While past events don't guarantee future outcomes, they can serve as a useful guide.

For example, if only 200K SPICE were redeemed in the last week, you're comparatively safer than if 15M were redeemed. You can monitor past redemptions in our [Dune dashboard.](https://dune.com/liquity/liquity-v2#redemptions)

**The price of** SPICE is the second crucial factor. When it trades above $1, redemptions become unprofitable and should cease. If demand for SPICE is strong, it can maintain a price above $1 for an extended period, as was often the case for LUSD.

During such times, you can comfortably reduce the interest rate you're paying without increasing your risk of redemption.

### What is delegation of interest rates? <a href="#what-is-delegation-of-interest-rates" id="what-is-delegation-of-interest-rates"></a>

Interest rate delegation is a feature in SpiceUSD that allows borrowers to delegate the management of their interest rate to a third party. This enables them to create a passive, hands-off position, while still keeping a competitive rate and low redemption risk.

There are three types of delegations:

* To a third party manager: A specialized entity which provides predetermined strategies for batches of multiple Troves and charges a fee for the service
* To an automated and decentralized contract strategy: A predefined strategy managing interest rates in an autonomous manner
* To your own wallet: Delegate to a hot wallet when on vacation, or to a friend

It is important to note that a delegate or contract strategy can do nothing else but set the interest rate in a predetermined range, significantly limiting the risks of the borrowers.

Borrowers should thus keep an eye on the interest rate range and the maximum update frequency (relevant in case of premature adjustments) preset by the manager.

### Who are the current active interest rate delegates? <a href="#docs-internal-guid-441d8c3f-7fff-4efa-6319-4ba00d908597" id="docs-internal-guid-441d8c3f-7fff-4efa-6319-4ba00d908597"></a>

Coming soon.

EntityCollateral AssetDelegate AddressDescription

*Note that SpiceUSD is not responsible for the actions of any delegates. Please do your own research.*

### What happens if there are issues with the smart contract for delegating interest rates? <a href="#docs-internal-guid-441d8c3f-7fff-4efa-6319-4ba00d908597-1" id="docs-internal-guid-441d8c3f-7fff-4efa-6319-4ba00d908597-1"></a>

Your Trove would not be affected - the only thing would get affected is the interest rate at which your position is set.

### Why are redemptions not a feature of both LTV & interest rate, but only interest rate? <a href="#docs-internal-guid-61a948e4-7fff-84a3-24cb-31bc5739c81a" id="docs-internal-guid-61a948e4-7fff-84a3-24cb-31bc5739c81a"></a>

Given that the *raison d’etre* for redemptions is to diminish SPICE supply in response to reduced demand, and interest rates drive demand, rate-based redemption processing is a more sustainable and effective lever to reach market equilibrium. Actively managing for both interest rate and LTV would weaken the ability to enforce market-level interest rates and deposit yields, while complicating the process for the system and its users

### What happens when redemptions cause a debt of a Trove to fall below the minimum amount? <a href="#docs-internal-guid-927901d5-7fff-c7a0-2e9f-964ab271257a" id="docs-internal-guid-927901d5-7fff-c7a0-2e9f-964ab271257a"></a>

If the redeemed amount exceeds the debt of an affected Trove, it doesn’t get closed as in Liquity V1, but remains open with 0 SPICE debt and the remaining collateral. The owner of a fully redeemed Trove may close it by withdrawing the remaining collateral, or borrow anew to bring its debt above the minimum of 2000 SPICE, topping up its collateral if needed.

In the scenario that the redeemed amount of a Trove does not exceed the debt of a Trove, but would leave it between 0 and 2000 SPICE, the Trove would remain open with the remaining debt, and the remaining collateral. The owner of the Trove may close it by paying off the remaining debt and withdrawing the remaining collateral, or borrow anew as described above.


# Technical Docs & Code Repository

A technical system summary including contract descriptions, function descriptions, and more is available in the V2 developer README.

### Technical papers <a href="#technical-papers" id="technical-papers"></a>

[Whitepaper](https://bafybeibjommrelqjw22vewpddgfdnm5geoz747gv2zeuy7njwivpfcy3xa.ipfs.w3s.link/Liquity%20v2%20-%20Whitepaper%20rev.%200.3%20\(November%2C%202024\)%20\(1\).pdf)

### Code base <a href="#code-base" id="code-base"></a>

[Bold Core](https://github.com/liquity/bold) [Governance](https://github.com/liquity/V2-gov/tree/main)

### Audit reports <a href="#audit-reports" id="audit-reports"></a>

[ChainSecurity - Core Protocol Audit Report](https://www.chainsecurity.com/security-audit/liquity-bold-smart-contracts), December 2024

[Dedaub - Core Protocol Audit Report I](https://dedaub.com/audits/liquity/liquity-v2-aug-28-2024/), August 2024

[Dedaub - Core Protocol Audit Report II](https://dedaub.com/audits/liquity/liquity-v2-second-audit-nov-11-2024/), November 2024

[Certora - Formal Verification](https://certora.cdn.prismic.io/certora/Z1tLJJbqstJ98b8J_LiquityVerificationReport.pdf), December 2024

[Coinspect - Bold Core Smart Contract Audit](https://www.coinspect.com/doc/Coinspect%20-%20Smart%20Contract%20Audit%20-%20Liquity%20-%20Bold%20-%20v241231.pdf), December 2024

[Coinspect - Bold Governance Audit](https://www.coinspect.com/doc/Coinspect%20-%20Smart%20Contract%20Audit%20-%20Liquity%20-%20Bold%20Governance%20-%20v250120.pdf), January 2025

[ChainSecurity -Governance Smart Contract Audit](https://www.chainsecurity.com/security-audit/liquity-v2-governance), January 2025

[Dedaub - Governance Audit 1](https://dedaub.com/audits/liquity/liquity-v2-governance-1st-audit-aug-12-2024/), August 2024

[Dedaub - Governance Audit 2](https://dedaub.com/audits/liquity/liquity-v2-governance-2nd-audit-nov-11-2024/), November 2024

[Dedaub - Governance Audit 3](https://dedaub.com/audits/liquity/liquity-v2-governance-3rd-audit-dec-22-2024/), January 2025

### Economic modelling and simulation <a href="#economic-modelling-and-simulation" id="economic-modelling-and-simulation"></a>

[Chaos Labs: Mechanism Design Review](https://cdn.sanity.io/files/zmh9mnff/production/ca6a4815e62b05f33fb3ec56c5a4c42d6b7ddbec.pdf), October 2024

### Contract Addresses <a href="#contract-addresses" id="contract-addresses"></a>

### **nrETH (non-rebasing ETH)**

* **addressesRegistry**: 0x43e79fb974acc05020bc1910bee38716c7415113
* **activePool**: 0x52a16962d013efa6ccf85b86c01368582a4c422d
* **borrowerOperations**: 0xa2c8fa4c9dfca47ad613b336a7ef96de109d645f
* **collSurplusPool**: 0xa00a9090db9fbfbb065b1d9906b4d3ef91b3d79d
* **defaultPool**: 0x4814c48cb60bd751d4145f14f7f988a55b3a954a
* **sortedTroves**: 0x844509b14b87ceaff985b8df31fe34f4afbba8f9
* **stabilityPool**: 0x3b2e65d1bafa6b50c79392c8079e52db0b1c1701
* **troveManager**: 0x8772a716c5974d0f213567c9021a0ffc5a4ad12e
* **troveNFT**: 0xe71c26f00992d4bb51275a630a27254adf9a7095
* **metadataNFT**: 0x1560d6d5d2f4f2173ace316159b845e58f4eaaa4
* **priceFeed**: 0xee7a9f5e1136e9f48fd5a4cc2e751bac165c40e7
* **gasPool**: 0x7674fadf9e77872060d340c1b71f7784c0aa6e15
* **interestRouter**: 0xd3240d8eb011253302e47c9536134bc44102469b
* **leverageZapper**: 0x6b35ea9c4bc24dc52cc9c299494c26e794eacc09
* **collToken**: 0x9d020b1697035d9d54f115194c9e04a1e4eb9af7

### **nrUSDB (non-rebasing USDB)**

* **addressesRegistry**: 0x5c1ef18d7f48997f0259b69dd5620fd103094571
* **activePool**: 0xc8effc42d0aca45f7ef6e0ce704ce14e1cee34a9
* **borrowerOperations**: 0x2f58928ef53201f875906b80639f239c19269a85
* **collSurplusPool**: 0xfead5c9ae483e105fc44342d11cd1086311a4825
* **defaultPool**: 0xa7cc4cc485b505ffee1b22e9be1537818a93afa9
* **sortedTroves**: 0x3d1e26f02663dc573a1c8fc6425ac365cd5ba9a3
* **stabilityPool**: 0x1fb7cc03f91020ae1daef130f6e53726a9d39011
* **troveManager**: 0x24c5257ab35c05e8d9f0ce440b1a03f1a83b1e77
* **troveNFT**: 0x9a32c611f90a04db8a175b4fe75a5dcd241ae140
* **metadataNFT**: 0xa9742d715818915d48e39c4e382d4adb3788ec24
* **priceFeed**: 0xf7bf4ee0ea98fd69145c5af98e979ff5ab48367e
* **gasPool**: 0xb105256ad606b51bdfbd2d6537e790b368b9cbd0
* **interestRouter**: 0xd3240d8eb011253302e47c9536134bc44102469b
* **leverageZapper**: 0x817a9e5517bb2e6b4b2d8b7948a7c1d100cfd344
* **collToken**: 0x96f6b70f8786646e0ff55813621ef4c03823139c

### **BLAST**

* **addressesRegistry**: 0x0e676732af49b783295f53681a6308d24c657a58
* **activePool**: 0xafa4395940aaff3cdd0a13f8278344c8516f200f
* **borrowerOperations**: 0x140e081fc41765226cd5281378232388095733f4
* **collSurplusPool**: 0xdcde3b080be8605f3070ba8f6c775733a59cf926
* **defaultPool**: 0xaaeb5ca3f281a046c5967e86d5fda97db9600726
* **sortedTroves**: 0x0b90402f2ff0eadb59b66c48a1cbc548bd204e77
* **stabilityPool**: 0xa9ba18c3bde34281a67a30840e3c980a1ca190d3
* **troveManager**: 0xe418d20add263ba8b10651998a15ec3069a644a1
* **troveNFT**: 0x85879411dff72c443566ee4abc408354562d3d2c
* **metadataNFT**: 0xa7d11fdc25256b34e0ef51f644e7ea1cd7ff7197
* **priceFeed**: 0xf5a489994405c7ae1e1724de5a085256253a510c
* **gasPool**: 0x85a057aa483f99c937be06be8e91623756b25f77
* **interestRouter**: 0xd3240d8eb011253302e47c9536134bc44102469b
* **leverageZapper**: 0xe0b030068e266912a1e8aa6fd42393c8bc131e78
* **collToken**: 0xb1a5700fa2358173fe465e6ea4ff52e36e88e2ad

### **FNX**

* **addressesRegistry**: 0x1005b48d3cba7b0dbc33d6178afead7d4c2cb023
* **activePool**: 0xa70fbf5b7fca7c11dd09b3bfca23bbed924c7c32
* **borrowerOperations**: 0x28def7c56622e13b5aa2f288aa9d6a1c87dac33e
* **collSurplusPool**: 0xb76cf3417762dbd90d0f2ee904c90f7112f1809e
* **defaultPool**: 0x19d8408e92340a55e7a2a69de4c70f11d35036d8
* **sortedTroves**: 0xf05b3b2879a78d78cc824116f7f62ecaea104edb
* **stabilityPool**: 0x58b689ff7ac3a5bc428189b5e4863918fef4a917
* **troveManager**: 0x85bda3e34a44c7415aecd628ee410119810b5a39
* **troveNFT**: 0xe7f8123c24b76fb1d801cac2477b09b29f594b05
* **metadataNFT**: 0xb1e2fd6d6309d7a46df7639f02b290407adb0f0b
* **priceFeed**: 0x7b968d8ae7f99da2c15f016a41336458b981ffdb
* **gasPool**: 0xb603e5642f9e8f844cdb25006d2a1f01908c7924
* **interestRouter**: 0xd3240d8eb011253302e47c9536134bc44102469b
* **leverageZapper**: 0x9ff7d7a80b68cdc9934d8185f4d1e5ea01eb87de
* **collToken**: 0x52f847356b38720b55ee18cb3e094ca11c85a192

### **HYPER**

* **addressesRegistry**: 0x32730cc18170a8523e2e36bc7f316db368bf6467
* **activePool**: 0xf723db403ae2ef384ef6d19ee666778ac75dc3e0
* **borrowerOperations**: 0x2b0369d02614ce5634bb173926f8f1dbfb236195
* **collSurplusPool**: 0x03ac6af5055ec034d62d2aabc62547cb83a77ec1
* **defaultPool**: 0x7cb60ff3cb3b3168a737e7ce091b927656d5b11a
* **sortedTroves**: 0x9686e71c7d0a3e04814de7ca5e20d4b3f6b6aebf
* **stabilityPool**: 0x31e22aa4732c2208194e147d09181dea20957735
* **troveManager**: 0xda43403971485687ff2b7442732544cba6a88781
* **troveNFT**: 0x6c14cda0cee0cadaff661379a052e4d50b67da26
* **metadataNFT**: 0x6fde3a9525a711ed4147ab9f8b1fa37b40e16d2e
* **priceFeed**: 0x4ea4d874dd0f1a1eba9d95853578cce63d6e2180
* **gasPool**: 0xb1ec1f622dbe61acfc44f305aa508dfd69113e02
* **interestRouter**: 0xd3240d8eb011253302e47c9536134bc44102469b
* **leverageZapper**: 0xa28af83476a73924d8afcad14a3b3f69747e59a4
* **collToken**: 0xec73284e4ec9bcea1a7dddf489eaa324c3f7dd31

### **THRUST**

* **addressesRegistry**: 0x3df2b1c72ef11390c67ddfc8c763f9030405c20e
* **activePool**: 0x4d6a3bee7d6586f4b4d467df08c23dc06a7abfeb
* **borrowerOperations**: 0x11eefb11a21c12ad1d86259571207683e5268975
* **collSurplusPool**: 0x21dfe73e99c3eb939012aa949979a273b3ce2e1f
* **defaultPool**: 0x12efc1381573938cb706c880245d44d204e864b1
* **sortedTroves**: 0xafcd80ac38a6928253b8589e39f6cd5ebb4e526a
* **stabilityPool**: 0x1f799c2b77022a2a8edfc1503570930a58004bcc
* **troveManager**: 0xff1abb2eb7112b362d5914fd078452712e02322e
* **troveNFT**: 0xddec926f9ada5ebfd5792f8216251e38c036f14e
* **metadataNFT**: 0x1489a5558ad356ceef66871f757b564e633668ad
* **priceFeed**: 0x43a8e12d7c3aa0726b373ca5cb9b8565622a6ffb
* **gasPool**: 0xf836b065ed8a4bf332459265fa4ba0c382272d14
* **interestRouter**: 0xd3240d8eb011253302e47c9536134bc44102469b
* **leverageZapper**: 0x3d3db337d37972c686469e6cedef3c2d00d4a107
* **collToken**: 0xe36072dd051ce26261bf50cd966311cab62c596e


# Brand Assets

{% file src="/files/1gshjl9KFtJUHBQRHb1p" %}


# Risk Disclosure

### **Dependencies** <a href="#dependencies" id="dependencies"></a>

* Oracles: Pyth for collaterals

### Chain Risk <a href="#chain-risk" id="chain-risk"></a>

* Deployment chain: Blast Mainnet
* Cross-chain: none (native to Mainnet and no cross-chain risks)

### **Smart Contract Risks** <a href="#smart-contract-risks" id="smart-contract-risks"></a>

SpiceUSD has no manual pause, freeze, or shutdown functions. However, the protocol is capable of initiating an automatic shutdown of a borrow market in case of an extreme price drop of the respective collateral asset leading to insufficient collateralization, or an oracle failure of that particular collateral asset.

* See our audits for more information: DeDaub and ChainSecurity
* Pause function: none
* Protocol freeze function: none
* Protocol shutdown function: Yes, it would be algorithmically targeted towards a specific branch
* SPICE whitelist or blacklist: none
* SPICE transfer freeze functionality: none

### Collateral Risk <a href="#collateral-risk" id="collateral-risk"></a>

* Collaterals assets accepted: WETH, USDB, BLAST, FNX, HYPER and THRUST
* Collaterals assets accepted within the protocol are non-upgradeable and cannot be changed

**What’s the shared-collateral risks?**\
Each supported collateral asset constitutes an individual borrow market with its own group of borrowers and a separate Stability Pool backing their debts. This separation impacts user groups differently:

* Borrowers: Collateral risk is limited to the collateral asset held by the borrower. A borrower isn’t negatively affected by a failure of another collateral asset.
* SPICE Holders: As a multi-collateral stablecoin, SPICE is reliant on effective liquidations of undercollateralized loans in every borrow market to remain overcollateralized. Holders are subject to the risks of all supported collateral assets.
* Earners: SP depositors only get exposure to the asset they have opted for. However, as SPICE holders, they are similarly affected by potential depegging.

**Are there any safety mechanisms in place for potential de-pegs of the underlying collateral asset?**\
The protocol aims to protect each borrow market from becoming undercollateralized by throttling debt creation and collateral withdrawal in unhealthy markets and by shutting down the entire market as a last resort. There are two safety thresholds:

* Critical Threshold (CT): If the TCR of a borrow market falls below the CT (e.g., 150%), new debt creation is prohibited. Collateral withdrawal is allowed as long as it goes along with a debt repayment greater than or equal to the collateral withdrawn.
* Shutdown Threshold (ST): If the TCR drops below the ST (e.g., 110%), the protocol triggers the shutdown of the borrow market and disables all borrowing operations except for closing Troves. Users can redeem SPICE against the respective collateral at a more favorable exchange rate than the current oracle price.

### Oracle Risk <a href="#oracle-risk" id="oracle-risk"></a>

If Chainlink oracles fail, collateral markets might get priced inaccurately, leading to unfavorable redemptions or excessive or delayed liquidations. Oracle staleness could also cause problems by using out-of-date prices during shutdowns, leading to improper liquidations or redemptions.

**Mitigation:**

* The system tracks staleness thresholds and shuts down a branch if the price hasn't been updated for a preset period (e.g., 48 hours for rETH).
* Upon shutdown, redemptions use the last recorded price, limiting the time window for exploiters to take advantage of a stale oracle.

#### Infrastructure Risk <a href="#infrastructure-risk" id="infrastructure-risk"></a>

* Onchain infrastructure: None other than Infura nodes (transactions could get delayed or dropped) None for on-chain functionality.
* Open-source and publicly accessible off-chain infrastructure. The Graph integration will allow for indexing and querying, but remains publicly accessible.

### Governance and Economic Risk <a href="#governance-and-economic-risk" id="governance-and-economic-risk"></a>

* Core protocol: is immutable - nothing can updated or changed
* Upgradable code: none
* Upgradable parameters: none
* Timelocks: none
* SpiceUSD multisig can only direct 25% of the revenues e.g. as liquidity incentives to LP pools. More information can be found [here](https://github.com/liquity/V2-gov/blob/main/README.md).

**Bad Debt mitigation and Branch Shutdown:**\
In extreme cases, such as a severe drop in collateral value or failure of a supported collateral, the system may become undercollateralized. This could lead to the shutdown of a specific collateral branch or market, and the remaining debt could become "bad debt"—unbacked by sufficient collateral. This could in the worst case lead to bank runs: a portion of the system debt can not be cleared, and hence a portion of the SPICE supply can never be redeemed.

**Mitigation:**\
Liquity V2 has built-in shutdown thresholds. When a collateral market's total collateral ratio (TCR) falls below the *Critical Threshold (CT)*, debt creation is paused, and collateral withdrawals are restricted. If the TCR drops further to the *Shutdown Threshold (ST)*, the protocol shuts down the market, freezes new borrowing, and triggers urgent redemptions. These redemptions are designed to clear as much debt as possible by allowing users to redeem SPICE at favorable rates. Additionally, redemptions are split in proportion to the "outside" portion of the respective debt, which is defined as the total debt borrowed against a certain collateral minus the size of the SP of the respective borrowing market.

That way, redemptions primarily reduce the debt of the borrowing market with the lowest SP backing, reducing the risks that the market ever drops below the thresholds. This triggers the liquidation of all collateral within that market to buy back and burn as much SPICE as possible. However, if the collateral price crash is severe, some portion of SPICE may become unbacked.

If this unbacked portion is small, the system can still function with SPICE retaining its peg, assuming no major loss of confidence. However, if confidence erodes, SPICE may depeg, leading to mass redemptions across healthier markets. In the worst-case scenario, the remaining debt-backed SPICE supply could be fully redeemed, leaving only the unbacked portion, potentially reducing SPICE's value to zero.This could happen even if the failed collateral represented a small portion of the entire market. The outcome ultimately depends on the market’s confidence in SPICE and the system’s ability to mitigate further risks.

### Liquidity Risk <a href="#liquidity-risk" id="liquidity-risk"></a>

Liquity V2 operates three distinct borrow markets, each backed by its own collateral types (ETH, wstETH, and rETH). Each market features separate stability pools, user-set interest rates, and individual Loan-to-Value (LTV) ratios tailored to the specific asset. This market structure allows for precise risk management, ensuring that liquidations and redistributions occur independently within each collateral market.

To support the stability of SPICE, Liquity V2 uses borrower-paid interest to create demand and facilitate liquidations. Borrower interest is directed into two primary venues:

1. Stability Pool (75%): Each borrow market is linked to a corresponding Stability Pool, where 75% of the interest paid by borrowers is deposited. SPICE depositors in the Stability Pool earn a portion of this interest, along with liquidation gains in the respective collateral asset. This structure helps maintain liquidity and solvency in each borrow market by absorbing liquidation events.

Potential risk: There's no guarantee that the liquidation gains are actually gains. In the worst case, e.g. when the oracle lags behind or an LST flash-crashes within a few blocks, the gains could turn into losses.

1. Protocol-Incentivized Liquidity (25%): The remaining 25% of interest goes to liquidity providers (LPs) as incentives, with the allocation split determined through weekly gauge voting. This incentivizes liquidity on decentralized exchanges, enhancing overall protocol stability and SPICE liquidity.

### **Redemption mechanism and risk for** SPICE **Stability**

To prevent SPICE from falling below $1, Liquity V2 includes a redemption mechanism. Any SPICE holder can redeem 1 SPICE for $1 worth of collateral, ensuring that SPICE remains pegged to its intended value. Redemptions are prioritized by the lowest interest rate Troves first, allowing borrowers to maintain their positions while keeping the system balanced. Importantly, redemptions do not result in a net loss for borrowers but ensure the peg remains intact.

### **Liquidation Process**

In the event of liquidations, the system first looks to the Stability Pool associated with the liquidated collateral type. If the Pool contains sufficient SPICE, it burns an amount equivalent to the borrower’s debt and redistributes the borrower’s collateral (105% of the debt) to the Pool’s depositors. These depositors receive both collateral and debt shares, proportional to their deposits.

If the Stability Pool is depleted and cannot cover the entire debt, the system falls back on two other liquidation modes:

* Just-in-Time (JIT) Liquidation: A liquidator deposits the amount of SPICE needed to cover the remaining debt directly into the Stability Pool, immediately triggering liquidation in exchange for 105% of the nominal debt in the collateral asset (e.g., WETH).
* Redistribution Mode: If JIT liquidation is not chosen, the entire debt and 110% of it in collateral is redistributed to fellow borrowers who hold the same type of collateral. Their debt increases proportionally, but they also receive a share of the liquidated collateral, ensuring system-wide balance.

This multi-layered liquidation process ensures that each collateral market is isolated from the others, minimizing systemic risk and allowing users to manage their positions independently.

### MEV Risks <a href="#mev-risks" id="mev-risks"></a>

**Frontrunning risk** Borrowers may attempt to evade redemptions by either adjusting their Trove’s interest rate or closing and reopening their Trove. This "frontrunning" could occur when the SPICE price falls below $1, as savvy borrowers try to protect their positions from redemptions that would otherwise target them based on their user-set interest rates. Both “hard” frontrunning (directly from mempool observations) and “soft” frontrunning (reacting to the SPICE peg) could negatively affect redemption efficiency and system stability, while also unfairly affecting borrowers that are playing by the rules.

**Mitigation:**\
Two fees are applied to disincentivize this behavior:

1. Upfront Borrowing Fee: Charged when a borrower opens a Trove or increases its debt, this fee is calculated as 7 days’ worth of average interest on the respective collateral branch. By applying this fee, borrowers are discouraged from continually closing and reopening Troves to evade redemptions, as it increases the cost of frequent adjustments.
2. Premature Adjustment Fee: When a borrower changes their interest rate too soon after the last adjustment (within a predefined cooldown period), they incur an additional opening fee. This mechanism prevents borrowers from rapidly adjusting their rates to avoid being prioritized in redemption processes, especially when rates are moving toward their redemption thresholds.

These measures help ensure that borrowers cannot easily front-run system redemptions.

**Flash Loans risk**\
In Liquity V2, redemption routing reduces the outside debt of each collateral branch proportionally. Flash loans could allow attackers to temporarily deposit SPICE into Stability Pools (SPs) of branches they wish to avoid, redirecting redemptions toward more favorable collateral branches. This could lead to arbitrage opportunities where the attacker selects assets with lower slippage on external markets.

However, while this strategy might increase profits for the attacker, it does not extract direct value from the protocol or impact the overall system health. The protocol’s design, with competitive redemption fees and the use of flash loan fees, naturally mitigates the risks associated with this manipulation. Flash loan fees reduce the profitability of such actions, and the competitive nature of redemption arbitrage further limits the potential benefits.

Mitigation: No fix is required because the risks are contained by the high costs of flash loans and the minimal impact on the protocol’s stability. Redemption routing is a soft measure designed to nudge the system toward balance, and the protocol remains reliant on the broader health of all collateral markets. Therefore, the system’s resilience is maintained despite these isolated arbitrage opportunities.

### NFT loan transfer risk <a href="#nft-loan-transfer-risk" id="nft-loan-transfer-risk"></a>

Troves are now represented as NFTs, enabling improved transferability and management of positions while maintaining the core stability mechanisms of the protocol. Troves are meant to be transferred between different owner accounts (e.g. hot and cold wallets), however, trading them in a marketplace poses additional risks. For example, Trove delegations and management accounts are not cleared after a transfer, the trove owner is able to reduce the trove's collateral before a trade, among other adversarial scenarios that could be used by malicious sellers on marketplaces.


