Trove Concepts Deep Dive
Deep dive on what a Trove is — isolated-position mental model, branch ring-fencing, and why CDP systems are designed this way
This page explains what a Trove is at the concept level, and why CDP systems use “position containers” instead of a single pooled margin account. It also maps Troves to familiar trading concepts like isolated margin (carefully, without pretending they are identical).
Not investment advice — This page explains mechanics and design trade-offs. It does not recommend any strategy or collateral ratio.
At a glance
A Trove is an on-chain position that bundles collateral and USDHN debt.
Your Trove is an isolated position: liquidation is determined by what’s inside that Trove, not by your wallet’s other assets.
Different collateral types can be separated into collateral branches with their own parameters (ring-fencing risk).
The key safety number is still CR, but the “isolated position” framing helps users reason about risk.
What a Trove actually is (mechanically)
At a high level, a Trove is a stateful on-chain “position record” that tracks:
what collateral you posted (amount + type, depending on branch)
how much USDHN you owe (principal + any accrued fees/interest)
a status/lifecycle (opened → adjusted → closed or liquidated)
which collateral branch parameters apply (minimum CR, fees, shutdown rules, etc.)
User-facing consequence:
you can add/withdraw collateral and mint/repay USDHN over time
to close, you must repay the full USDHN debt
Trove as an “isolated position” (mapping to isolated margin)
If you are familiar with exchange trading:
isolated margin means “this position has its own collateral; other balances are not automatically used to save it”
A Trove is similar in that sense:
each Trove’s liquidation risk is determined by its own collateral and its own debt
other assets in your wallet (or other Troves) are not automatically pulled in to prevent liquidation
Concept mapping table (not 1:1)
Isolated margin position
Trove
Trove mints a stable asset; it’s not a perp “position”
Maintenance margin
Minimum CR (MCR)
Defined per collateral branch; shown in UI (values differ by branch)
Liquidation price
UI liquidation price
Usually based on oracle price, not necessarily spot
Borrowed asset
Minted USDHN debt
You “owe USDHN units”; repayment cost depends on USDHN market price
Deleveraging
Repay USDHN / add collateral
Requires on-chain actions and can involve swaps/slippage
Why “not 1:1” matters — A Trove is not a derivatives position. It is a collateralized debt position. The mapping above is only to transfer intuition about risk isolation and liquidation thresholds.
Why design it this way? (advantages)
CDP systems use Troves because they make risk and integrations easier to reason about:
Risk is isolated per position: one risky position does not automatically drain your entire wallet.
You can run multiple risk profiles: e.g., one conservative Trove and one higher-risk Trove, without mixing them.
Parameters can be ring-fenced by collateral branch: different collateral types can have different minimum CRs, fees, and risk controls.
Integration is cleaner: positions can be represented as NFTs and indexed explicitly (ownership, history, health).
No fixed maturity by default: you manage the position over time (subject to protocol rules and safety constraints).
What is not isolated (shared system risks)
Even though a Trove is “isolated” as a position container, some risks are shared across users:
USDHN peg risk: USDHN can trade above/below
$1in markets.Oracle and smart contract risk: if pricing or contracts fail, many positions can be affected.
Liquidity conditions: stressed liquidity can increase slippage and make deleveraging harder.
Collateral branches can ring-fence some risk, but they do not eliminate system-level risk.
Practical mental checklist for users
Minting USDHN creates a repayment obligation. Spending or selling USDHN does not remove it.
CR is the “safety dial.” Lower CR means higher liquidation sensitivity.
Treat liquidation price as a risk indicator, not a target.
If you plan to use leverage or loops, first understand the unwind path (repay USDHN).
Next reads
Main flow: Borrowing & Liquidation
CR and liquidation math: CDP Safety Deep Dive
Redemption impacts on Troves: Redemptions Deep Dive
Leverage mechanics: Looping & Leverage Deep Dive
Last updated