Valuation (NAV)
The two ways a Tuo position is valued, why they differ, and which one the contract settles on.
A Tuo position has two values, and they answer different questions. The Dashboard NAV tells you what the whole position is worth right now. The Settlement NAV is what the contract can prove and is the only figure a fee is ever charged on.
Dashboard NAV
Computed off-chain by Tuo's backend every five minutes for every active position.
- Idle balances in the vault, priced at the pool's 30-minute average.
- Open ranges, valued at the same average price, plus the fees they have actually earned. The backend simulates a fee collection to get that figure, because Uniswap V3 reports zero fees owed for a range that has never been touched. The vault computes the same figure on-chain.
- The Hyperliquid leg: the equity of the position's operator account, read across both of the venue's ledgers so that unrealised profit and loss on the short is counted once, plus any margin on its way between the vault and the venue. That is the USDC waiting on the operator's Arbitrum wallet and any bridge transfer still under way, counted at no more than what it will deliver after the bridge's maximum fee. A transfer therefore shows at most that maximum fee as a cost.
Every on-chain read in a cycle is pinned to one block. Whether a range is in range is judged from the spot price; its value is judged from the average price. The two are never interchanged.
The Dashboard NAV is indicative. It is what the app charts and what your portfolio total shows. It never charges a fee and never moves money.
If any leg cannot be priced, the cycle publishes nothing rather than a partial figure. The same holds when hedge margin is out but cannot be found on the venue, on the operator wallet or on a bridge transfer. A gap in the chart means the backend refused to guess, not that value disappeared. Stale prices are still published and flagged as stale.
Settlement NAV
Computed on-chain by the vault. It values only what the contract can measure:
- Idle balances, priced at the pool's 30-minute average.
- Open ranges, valued at the same average price, plus every fee they have earned: the ones the pool has already credited and the ones it has accrued since the range was last touched, which the vault recomputes from the pool's fee growth exactly as a collection would.
It does not value the Hyperliquid leg at all. The contract has no way to verify what an account on
another venue holds, and any keeper-attested figure would be a fee-extraction vector and a way to
burn a position's NFT against the wrong value. So while the position's Hyperliquid lifecycle is
open, the settlement value is unavailable and the contract reverts with HlMarginOutstanding. A
bridge opens the lifecycle, and only the keeper's final return closes it.
That revert is the normal state of a hedged position, not an error. It clears when the keeper's final return closes the lifecycle during a withdrawal. Until then, the withdrawal panel shows an estimate on the Dashboard NAV, Hyperliquid leg included and labelled as an estimate. The vault's own figures replace it once your withdrawal request is armed and the margin is home.
Why the two differ
| Dashboard NAV | Settlement NAV | |
|---|---|---|
| Where | Off-chain, Tuo backend | On-chain, the vault |
| When | Every 5 minutes | On demand, any block |
| Hyperliquid leg | Included at venue equity, plus margin on its way to or from the venue | Excluded; unavailable while the Hyperliquid lifecycle is open |
| Range fees | Simulated collection, the true accrual | Computed from the pool's fee growth, the same accrual |
| Price | Pool 30-minute average | Pool 30-minute average |
| Charges a fee | Never | Yes, at withdrawal |
The Dashboard NAV is usually higher than the Settlement NAV while a position is running, because it counts a hedge the contract cannot see. Range fees are not a source of difference: both figures value a live range at what burning it would return, fees included. At withdrawal, the keeper burns the ranges (which realises them into idle balances) and brings the margin home (which turns the hedge's result into idle USDC), so the two converge on the same number before the contract settles.
How the hedge result enters the settlement
The contract books margin sent to Hyperliquid at par: 1 USDC sent is 1 USDC outstanding. When margin comes back, the contract credits what actually arrived. A hedge that lost returns less; a hedge that gained returns more. The difference is the hedge's realised result, and it lands in the position's idle USDC, where the settlement value counts it.
Because a losing hedge returns less than it was sent, the outstanding figure would never reach zero on its own. The keeper's final return therefore carries a flag that clears the attribution outright. The contract accepts that flag only while a withdrawal request is armed, since that is the one state in which no new margin can leave. The extreme case, a liquidated short that leaves nothing at the venue, is a final return of zero: a write-off that lets the owner still withdraw the on-chain leg.
The reverse case gets the same care. A return can repay everything that was sent while more value is still at the venue, because a hedge that gained is worth more than its margin and a single return does not always carry all of it. The outstanding figure reaching zero therefore does not make the settlement value available. Only the final return does. Until the keeper attests it, the contract keeps the position's Hyperliquid lifecycle open, the settlement value stays unavailable, and every later return still lands on the position.
What the performance fee is charged on
Profit equals Settlement NAV minus basis. The 30% fee applies to the profit share being withdrawn and to nothing else. Hyperliquid profit and loss reaches the fee base only as the USDC that actually came back into the vault. See Performance fee.
For integrators
settlementNav(nftId) returns the on-chain value or reverts HlMarginOutstanding.
previewWithdraw(nftId) returns the gross, fee and net for the armed request under the same
rule. idleBalance(nftId, token) returns a position's undeployed balance. A withdrawal is
serviceable when the previewed gross is covered by the idle USDC; there is no readiness flag. For a
100% request the gross is the whole settlement value, so that holds only once every range is
burned and every priced WETH or WBTC balance is converted completely into USDC. See
Events and integration.
Engine v25
Engine v25 is the proprietary quantitative engine that decides ranges, hedge sizes and rebalances; this page explains what it does and how its decisions reach the chain.
Withdrawals
How to withdraw a Tuo position in two wallet calls, what happens in between, and the emergency exit that no one can block.