No Surprises: How Flux Monitors Manager Positions

Most DeFi vaults don't measure risk. They measure balances.

You deposit funds. A manager deploys them. The vault tracks how much went in and how much came back. If the manager makes money, great. If they don't, you find out when withdrawals fail.

This isn't risk management. It's accounting with hope attached.

Flux takes a different approach. Every manager position is continuously monitored against multiple risk factors. The protocol doesn't wait for problems to surface—it calculates exactly how close each position is to trouble, updates that calculation with every block, and acts automatically when thresholds are crossed.

The Health Ratio: One Number That Matters

At the core of Flux's risk system is a single metric: the health ratio.

Health Ratio = Total Position Value / Total Debt

A manager borrows $100,000 from a vault. They post collateral and deploy that capital into various positions. If their total position value (deployed capital + collateral bond) is $150,000 and their debt (including accrued interest) is $100,000, their health ratio is 1.5—or 150%.

The health ratio isn't static. It moves constantly as asset prices change, as interest accrues on debt, and as the manager's positions gain or lose value. Flux recalculates this with every block.

Each vault’s strategy defines a liquidation threshold. If a manager’s health ratio drops below that threshold, anyone can liquidate their position. Above it, they’re safe.

A vault accepting stable collateral might tolerate a lower threshold. One accepting volatile assets might require a larger buffer. The curator makes this call when configuring the strategy.

This simplicity is intentional. One number, one threshold, one outcome. No complex tiered systems or governance votes. The math is transparent and the rules are enforced automatically.

Beyond Simple Ratios

A health ratio alone isn't enough. Two positions can have identical ratios but vastly different risk profiles.

Consider two managers, both at 140% health. The first holds a diversified mix of established assets with deep liquidity. The second holds concentrated positions in volatile tokens with thin order books. On paper, they look the same. In practice, the second position could become unliquidatable if markets move quickly—no one can sell illiquid assets at fair prices during a crash.

Flux accounts for this through strategy parameters that vault creators configure at deployment. Four core parameters define how risk is measured for each vault:

• Minimum bond ratio determines how much of their own capital managers must post. A 20% bond ratio means managers put up $20,000 of their own money to borrow $100,000. This creates skin in the game and sets the maximum leverage.
• Liquidation buffer creates a safety margin between a position's actual health and the point where liquidation triggers. A 10% buffer means positions are liquidated before they become truly dangerous, not after.
• Interest rate matters because debt grows continuously. A position that looks healthy today may not be healthy next month if interest keeps accruing. Flux models this growth to estimate time-to-liquidation.
• Liquidation profit margin determines how much incentive liquidators receive. Higher margins mean faster liquidations but more cost to the manager. Lower margins protect managers but may slow response times.

These parameters aren't hidden. They're set at vault creation, visible on-chain, and in many cases immutable. Users can evaluate risk before depositing, not after.

Pricing That Doesn't Lie

A health ratio is only as good as the prices feeding into it. If a vault thinks an asset is worth $100 when it's actually worth $50, every risk calculation is wrong.

Flux solves this through asset wrappers. Each wrapper knows how to value a specific type of asset, including where to get its price. The oracle source is determined by the wrapper design, not a global rule.

A wrapper for ETH might pull from an aggregated price feed. A wrapper for a yield-bearing vault token might calculate value from the underlying share price. A wrapper for a Uniswap V3 position might compute the value of concentrated liquidity across a price range. A wrapper for a stablecoin might use a fixed price.

This design means the protocol can support any asset type, as long as someone builds a wrapper that knows how to value it. The curator decides which wrappers to approve for their vault, and that determines what collateral managers can hold.

Every price is normalized to 18-decimal USD values for consistent comparison. Wrappers can implement staleness checks, fallback sources, or any other logic appropriate for their asset type.

This matters because during market stress—exactly when accurate pricing is most critical—getting reliable prices is hard. Flux pushes that complexity into the wrapper layer, where it can be handled appropriately for each asset type.

Different Assets, Different Risks

Not all collateral is equal. A position backed by USDC has different risk characteristics than one backed by volatile tokens or exotic LP positions.

Each wrapper type carries different risks:

• Pricing reliability: How trustworthy is the oracle this wrapper uses? Aggregated feeds for major tokens are battle-tested. Custom pricing logic for exotic assets may be less proven.
• Liquidity depth: Can the collateral actually be sold at the reported price? Deep markets mean yes. Thin markets mean slippage.
• Composition complexity: A single-asset position is simple to value. An LP position holding two tokens, each with its own pricing and liquidity profile, is more complex.

The curator controls risk by choosing which wrappers to approve. A vault accepting only established assets can use aggressive parameters. One accepting exotic collateral might require higher bond ratios and larger buffers.

Continuous Monitoring, Not Periodic Checks

Traditional risk management often works on schedules. Daily reports. Weekly reviews. Monthly audits. This cadence made sense when computing power was expensive and data was hard to aggregate.

On-chain, there's no reason to wait. Flux monitors positions continuously:

• Current health ratio: Where is the position right now?
• Debt trajectory: How fast is interest accruing? What will debt be in a week? A month?
• Time-to-liquidation: If nothing changes, how long until this position crosses the liquidation threshold?
• Safety margin: How much buffer exists between current health and danger zone?

The system doesn’t wait for problems. Every position’s health ratio can be checked at any time, by anyone, on-chain.

This transparency lets managers monitor their own buffer. A position with a health ratio of 150% and a liquidation threshold of 110% has room to breathe. One sitting at 115% is close to the edge.

Managers can see this coming. Debt accrues continuously as interest compounds. If asset prices are flat and debt keeps growing, health ratio declines over time. A manager paying attention knows when to add collateral, close positions, or repay debt before crossing the threshold.

The protocol doesn’t send alerts or warnings. It doesn’t need to. The state is public, the math is simple, and the consequences are clear: stay above the threshold or get liquidated.

What Happens When Thresholds Are Crossed

Monitoring is only valuable if it triggers action. In Flux, crossing the liquidation threshold enables automatic position closure.

When a position's health drops below the liquidation threshold, anyone can liquidate it. Not a governance committee. Not the vault creator. Anyone. The liquidator pays off the manager's debt, takes their collateral, and the position closes.

This permissionless design means liquidations happen quickly. There's no waiting for someone with authority to notice and act. Economic incentives ensure that unhealthy positions get closed while there's still collateral to recover.

For situations where positions are healthy but the vault needs liquidity, Flux's Auto-Deallocating mechanism allows force-closing positions in a specific risk zone. The manager gets their full equity back—no penalty—but the vault regains access to capital for depositor withdrawals.

The Contrast With Trust-Me Vaults

Most yield vaults have no equivalent to any of this.

They don't calculate health ratios because they don't require collateral. They don't monitor continuously because there's nothing to monitor—capital goes into a black box and either returns or doesn't. They don't liquidate automatically because there's no threshold defined and no mechanism to enforce it.

When something goes wrong in these vaults, the response is manual: the team investigates, governance deliberates, and eventually some action is taken. By then, the damage is often done.

Flux inverts this model. Risk assessment isn't an afterthought—it's the foundation. Every position has a health ratio. Every vault has defined thresholds. Every breach triggers automatic response. The protocol doesn't trust managers to maintain healthy positions. It verifies continuously and acts immediately when they don't.

This is what risk management looks like when it's built into the protocol rather than bolted on afterward: transparent, automatic, and uncompromising.