Leveraged liquid-staking vault

A leveraged liquid-staking vault stakes deposited ETH, pledges the resulting liquid-staking claim as collateral, borrows a stablecoin, and converts that debt into more ETH staking exposure.

This is a generic educational composition with one leverage loop. It is not a recommendation, a promise of positive carry, or a model of one deployed vault. Every implementation must be checked for its own token, oracle, lending, staking, swap, accounting, governance, and liquidation rules.

Objective and system boundary

The objective is to increase ETH staking exposure through borrowing, so the vault holds more staked-ETH exposure than the ETH initially deposited. It packages five connected transformations:

1. ETH becomes a liquid-staking claim.
2. The vault pledges that claim as collateral.
3. A lending pool creates stablecoin debt.
4. A swap converts borrowed stablecoins into ETH.
5. The vault stakes that ETH, increasing both assets and exposure.

Depositor --ETH--> Vault --ETH--> Liquid-staking protocol
Depositor <--vault share-- Vault <--liquid-staking claim-- Liquid-staking protocol

Vault --liquid-staking collateral--> Lending pool --stablecoin debt--> Vault
Vault --stablecoin--> DEX --ETH--> Vault --ETH--> Liquid-staking protocol

The system boundary includes the proof-of-stake network, validator operators, liquid-staking protocol, withdrawal path, lending market, collateral oracle, stablecoin, exchange route, vault, and every authority that can change or pause them.

Layer mapping

Table: Layer mapping

System layer	Component	Economic role
Money and assets	ETH and borrowed stablecoin	ETH is the exposure and staking asset; the stablecoin is the debt asset and swap input
Staking primitive	Proof-of-stake validators	Perform network duties and receive protocol issuance, transaction fees, or service payments while accepting penalties
Claim layer	Liquid-staking token	Represents a pooled share or redeemable claim whose value reflects controlled stake, rewards, fees, exits, and losses
Lending primitive	Collateralized borrowing	Encumbers the liquid-staking claim and creates a stablecoin liability
Trading primitive	Stablecoin-to-ETH swap	Converts borrowed capital into additional ETH under price, fee, slippage, and execution constraints
Strategy	One-loop leveraged staking	Repeats staking exposure once and manages debt, collateral, rewards, and exit liquidity
Product	Vault and vault share	Packages the strategy behind one pooled share

Leverage does not create an independent return source. It increases the amount of staking exposure financed by a liability.

Actors, assets, claims, and liabilities

Table: Actors, assets, claims, and liabilities

Actor	Asset controlled or action taken	Claim, liability, or authority
Depositor	Transfers ETH to the vault	Holds vault shares and any pending redemption claim
Vault	Controls ETH, liquid-staking tokens, swap proceeds, and lending position	Owes shareholders their rule-based portion of net assets
Liquid-staking protocol	Pools ETH, allocates validators, reports rewards and losses, and handles exits	Issues the liquid-staking claim and any queued-withdrawal claim
Validator operator and network	Operate consensus and account for rewards, penalties, and slashing	Receive operator fees or impose protocol-defined loss
Lending pool	Controls pledged collateral and lends stablecoins	Holds the vault’s principal-and-interest debt claim and liquidation entitlement
Oracle path	Values the liquid-staking collateral and stablecoin debt	Provides trusted inputs rather than a financial claim
DEX, pool, router, or solver	Converts stablecoins into ETH and may support unwind trades	Receives fees and executes within route and slippage constraints
Keeper, governance, guardian, or admin	Rebalances, reports, pauses, changes parameters, or upgrades components	Exercises disclosed control over user assets and claims
Liquidator	Repays eligible debt and receives permitted collateral plus incentive	Has no entitlement beyond the executed liquidation rules

The vault share is a pooled share of net assets, not direct ETH. The liquid-staking token is a separate pooled share or redeemable claim, not ETH in the vault’s wallet. The stablecoin borrow is a debt claim held by the lending pool and a liability even after its proceeds are swapped and staked.

Step-by-step mechanism

1. Deposit and mint. A user deposits ETH. The vault mints shares from the pre-deposit net asset value under its fee and rounding rules.
2. Stake. The vault deposits ETH into an approved liquid-staking protocol and records the claim actually received.
3. Pledge collateral. The vault supplies or encumbers the liquid-staking claim in a lending market that recognizes it as eligible collateral.
4. Borrow. The vault borrows a bounded amount of stablecoin, creating debt that accrues interest independently of staking performance.
5. Swap. The strategy swaps stablecoin for ETH with maximum input, minimum output, deadline, route, and recipient constraints.
6. Restake once. The acquired ETH becomes another liquid-staking claim. The worked example adds it to collateral but does not borrow again.
7. Accrue and monitor. Staking rewards, penalties, token exchange rates, collateral prices, debt interest, fees, and health factor update the vault’s net value and liquidation buffer.
8. Deleverage or redeem. The strategy must obtain stablecoins, repay debt, release collateral, exit or trade the liquid-staking claim, and only then satisfy executable shareholder redemptions.

Repeated borrowing loops can approach much higher leverage and create recursive claim, oracle, liquidity, and transaction dependencies. They are outside this one-loop example and must not be inferred from its numbers.

The six connecting flows

Table: The six connecting flows

Flow	Trace through this composition	What must remain inspectable
Capital flow	ETH → vault → staking; stablecoin → vault → DEX → ETH → staking; deleveraging runs the route in reverse	Asset identity, amount, route, recipient, fees, slippage, and actual balance changes
Claim flow	Vault share → vault net assets; liquid-staking token → pooled stake; lending debt → vault collateral and repayment obligation	Issuer, holder, backing, conversion rate, encumbrance, priority, mint, burn, and release rules
Information flow	Validator reports, staking exchange rate, withdrawal status, collateral and debt prices, rate indices, health factor, and swap quotes	Source, units, decimals, freshness, validity, aggregation, and fallback behavior
Return flow	Network issuance, transaction users, and service customers → staking system → liquid-staking claim → vault NAV; vault → lending suppliers through borrow interest	Gross source, dilution, operator and protocol fees, borrowing cost, swap cost, vault fee, and net result
Control flow	Vault roles choose limits and routes; staking and lending authorities control operators, parameters, pauses, exits, listings, or upgrades	Proposer, approver, executor, delay, emergency power, recovery path, and shareholder exit window
Risk flow	Slashing, claim discount, ETH decline, debt growth, oracle error, or illiquidity → health factor or realizable collateral → liquidation or impairment → vault NAV → shareholder	Trigger, propagation order, liquidation incentive, reserve or backstop, and final loss absorber

The labels carry meaning independently of any category or edge color.

Balance sheet and leverage accounting

The simplified strategy identity is:

vaultNetAssetsEth = realizableLiquidStakingValueEth
                  + idleAssetsEth
                  - stablecoinDebtValueEth
                  - recognizedLiabilitiesEth

Gross exposure and leverage are:

grossStakingExposureEth = realizableLiquidStakingValueEth
leverageMultiple = grossStakingExposureEth / vaultNetAssetsEth

The lending position’s health factor follows its protocol-defined formula. For the single-collateral illustration below:

healthFactor = collateralValueUsd * liquidationThreshold / debtValueUsd

Every value must use a stated time, unit, price source, decimal convention, and recognition policy. Liquid-staking token balance, pooled-ETH exchange value, market sale value, direct-redemption value, and lending-oracle value can differ.

Table: Balance sheet and leverage accounting

Event	Vault assets	Vault liabilities and claims	External state
User deposits ETH	Idle ETH rises	Vault shares rise by fair pre-deposit value	No lending debt exists
Vault stakes ETH	Idle ETH falls; liquid-staking claim rises	Vault shares do not change	Controlled network stake and protocol claim supply rise
Vault pledges claim	Asset remains on the vault balance sheet but is encumbered	Lending pool obtains a conditional seizure right	Collateral and oracle state become active
Vault borrows stablecoin	Stablecoin cash rises	Principal-and-interest debt rises	Lending-pool cash falls and borrower debt rises
Vault swaps and stakes	Stablecoin cash falls; staking exposure rises by actual output	Debt remains; trading costs reduce net assets	DEX reserves or counterparty balances and staking claim supply change
Rewards or penalties accrue	Claim value rises or falls	Fee liability may change; debt interest accrues separately	Network and staking protocol account for reward, penalty, and fee
Vault repays and withdraws	Assets used for repayment fall; collateral becomes releasable	Debt falls and liquidation entitlement is reduced	Lending-pool cash rises; staking exit or market sale may remain pending

Numerical one-loop example

Assume, only for this arithmetic example:

• the vault starts with 100 ETH of shareholder net assets;
• it stakes the 100 ETH and receives a liquid-staking claim valued at 100 ETH;
• the lending market applies an 80% liquidation threshold;
• the vault borrows stablecoins worth 40 ETH at the starting ETH price;
• the swap produces exactly 40 ETH after any entry cost, and the vault stakes it and adds the resulting claim to collateral;
• the period’s gross staking return is 5% of 140 ETH;
• debt interest for the period is 3% of the initial 40-ETH-equivalent debt;
• other strategy costs are 0.30 ETH; and
• a 10% vault performance fee is charged on positive strategy gain after borrowing and other costs, recognized as a liability rather than fee shares.

Table: Numerical one-loop example

Measure	Calculation	Result
Gross staking exposure	100 + 40	140 ETH
Opening net assets	140 − 40	100 ETH
Opening leverage	140 ÷ 100	1.40×
Opening health factor	140 × 80% ÷ 40	2.80
Gross staking return	140 × 5%	7.00 ETH
Borrowing cost	40 × 3%	1.20 ETH
Gain before vault fee	7.00 − 1.20 − 0.30	5.50 ETH
Vault performance fee	5.50 × 10%	0.55 ETH
Ending net assets	100 + 5.50 − 0.55	104.95 ETH

The 4.95 ETH shareholder gain is modeled net of the stated debt cost, strategy cost, and vault fee. It is not guaranteed. It also ignores intra-period price movement, compounding, changing rates, taxes, and execution differences.

The strategy has positive carry in the reporting unit only when staking income and other explicit income exceed borrowing interest, trading and exit costs, operator and protocol fees, vault fees, penalties, slashing, and valuation loss.

Return path

Protocol issuance, transaction fees, and other named staking payments accrue
→ liquid-staking claim value or balance grows after operator and protocol fees
→ the larger leveraged staking position earns more gross return
→ stablecoin debt accrues borrowing interest owed to lending suppliers
→ swap, exit, keeper, and vault costs are recognized
→ residual net gain, if positive, increases vault NAV per share

The proof-of-stake protocol, transaction users, and any separately identified service customers or incentive budget fund gross staking return. Lending suppliers receive the vault’s borrowing cost. Leverage magnifies the spread between those flows; it does not guarantee that the spread stays positive.

Loss and liquidation paths

ETH decline or liquid-staking discount

ETH price or liquid-staking collateral value falls relative to stablecoin debt
→ collateral value and health factor fall
→ keeper cannot or does not repay or add collateral in time
→ permissionless liquidation repays debt and seizes collateral plus incentive
→ vault retains less staking exposure and pays liquidation cost
→ vault NAV per share falls and shareholders absorb the residual loss

With the opening values above and no debt growth, the modeled liquidation price factor is:

liquidationPriceFactor = debtValue / (collateralAmount * liquidationThreshold)
                       = 40 / (140 * 0.80)
                       = 0.357142...

Under the simplified single-price model, a fall to about 35.71% of the starting ETH price makes health factor equal 1. That is about a 64.29% decline, not a safety guarantee: debt interest, a liquid-staking discount, oracle differences, parameter changes, fees, or execution loss can move liquidation closer.

Slashing or validator penalty

A slashing event can reduce the controlled stake or liquid-staking claim value. That loss simultaneously reduces vault NAV and collateral value while stablecoin debt remains. The staking pool or an explicit reserve may absorb some loss first; vault shareholders bear the portion that reaches the claim. If liquidation leaves unrecovered debt, lending suppliers or another stated backstop can also lose.

Borrow-rate and exit-liquidity shock

Debt can grow even when ETH is unchanged. Deleveraging requires stablecoins, which may require selling the liquid-staking claim at a discount or entering a staking withdrawal queue. A valid accounting value does not guarantee the required stablecoin can be obtained before liquidation.

Control, oracle, and integration boundaries

Before treating the vault share as “staked ETH with higher yield,” inspect:

• which liquid-staking claim is accepted, how rewards and penalties change it, which validators and reporters it depends on, and how direct withdrawal, queueing, and secondary-market sale differ;
• which oracle values collateral, whether it uses ETH parity, an exchange rate, a market price, or a conservative combination, and how staleness, depeg, or sequencer failure is handled;
• who sets collateral eligibility, maximum LTV, liquidation threshold, bonus, close factor, interest-rate model, caps, pause state, and reserve use;
• which DEX route, approvals, slippage limits, deadlines, recipients, and MEV assumptions apply to leverage and unwind trades;
• who may loop, harvest, rebalance, deleverage, migrate, charge fees, pause, recover tokens, or upgrade the vault; and
• whether one component’s pause, cap, withdrawal queue, upgrade, or accounting change can strand assets or prevent debt repayment elsewhere.

The composition links existing concepts rather than defining another graph. Its principal dependency pages include staking return, loan-to-value, lending liquidation, net asset value, oracle risk, liquidity risk, solvency risk, and integration risk.

Protocol context and source boundaries

Lido’s wstETH documentation describes one protocol-specific wrapper used to integrate a non-rebasing representation of stETH into other DeFi systems. Its withdrawal-queue documentation shows that a withdrawal request can become a separate queued claim before ETH is claimable. These details illustrate layered claims and exit states; they do not establish that every liquid-staking token has Lido’s accounting, operators, governance, queue, or loss rules. The Lido references were reviewed 2026-08-10.

Aave’s health-factor and liquidation guide documents one protocol’s threshold-based health factor and permissionless liquidation path. Health-factor formulas, collateral eligibility, thresholds, bonuses, close behavior, and governance differ across lending systems. The numerical example above is therefore an independent generic model, not an Aave or Lido position reconstruction. The Aave guide was reviewed 2026-08-10.

Ethereum.org’s staking-withdrawal guide describes network-level reward payments and validator exits, including a queue whose timing depends on demand. A liquid-staking protocol adds its own pooling, claim, operator, reporting, liquidity, and governance layers on top. The network guide was reviewed 2026-08-10.

Security properties to test or verify

These are desired properties, not claims of proof for any deployed system:

• every deposit, stake, wrap, collateral transfer, borrow, swap, restake, repay, withdrawal, and redemption reconciles actual balances, claims, debt, fees, and eligible vault shares;
• borrowing and recursive looping cannot exceed approved assets, markets, leverage, LTV, debt, price-impact, slippage, or loss limits;
• the health factor used for monitoring, new borrowing, collateral withdrawal, and liquidation derives from the same reconciled prices, units, thresholds, and debt state used for settlement;
• liquidation repays no more debt and seizes no more collateral than exists or the selected close, bonus, fee, and rounding rules permit;
• staking reward, penalty, slashing, rebase, exchange-rate, fee, and withdrawal events cannot be omitted or counted twice in NAV;
• a liquid-staking accounting value cannot be treated as executable ETH or stablecoin liquidity when queues, discounts, caps, or pauses prevent exit; and
• every validator, reporter, oracle, keeper, router, governance, guardian, admin, and upgrade authority remains disclosed and bounded.

Common misunderstandings

• “Liquid staking removes staking lockup.” It creates a transferable claim; direct redemption can still depend on exits, queues, accounting, and protocol liquidity.
• “The borrowed stablecoin disappears after the swap.” The token is spent, but principal and accruing interest remain a vault liability.
• “More staked ETH guarantees more profit.” Leverage increases gross staking exposure and also borrowing cost, price sensitivity, slashing exposure, and liquidation loss.
• “ETH and a liquid-staking token always move one-for-one.” Exchange-rate, market-price, direct-redemption, and oracle values can diverge.
• “A health factor above 1 is universally safe.” Formula, threshold, update timing, liquidity, correlation, and transaction execution are protocol- and state-specific.
• “The strategy can always unwind atomically.” Debt repayment may depend on DEX depth, private or public order flow, stablecoin liquidity, withdrawal queues, blockspace, and unpaused integrations.

Review checklist

1. Which asset is the direct deposit, which tokens are layered claims, and which balances are encumbered?
2. How much gross staking exposure and stablecoin debt exist after every loop?
3. Who funds each staking-return component, who receives each fee, and which costs must be paid even when staking income falls?
4. Which price or exchange rate controls NAV, LTV, health factor, liquidation, and executable unwind value?
5. How do ETH decline, token discount, debt interest, slashing, and withdrawal delay interact rather than occur in isolation?
6. Who can change or pause the vault, staking, lending, oracle, swap, and exit paths, and how much time do shareholders have to respond?
7. Which reserve bears first loss, when can lending suppliers lose, and which residual loss reaches vault shareholders?

Continue with liquid staking, health factor, lending liquidation, and vault.