TL;DR: Funding rate and open interest describe how crowded and how leveraged a perp market is. They make useful triggers and filters, such as fading extreme funding or confirming a breakout with rising open interest, but they are ideas to test, not known edges. In Trigr you can use funding, open interest, long/short ratio and liquidations as nodes, then backtest net of funding and slippage before trusting any result.
What do funding rate and open interest actually measure?
A perpetual future has no expiry, so exchanges use funding payments to keep its price near the underlying index. When the perp trades above the index, longs pay shorts; when it trades below, shorts pay longs.
On Hyperliquid, the documentation on funding describes a rate computed from an average premium index plus a clamped interest-rate component, paid every hour at one eighth of the computed 8-hour rate and capped at 4% per hour. Persistent positive funding usually means demand for leveraged longs exceeds demand for shorts.
Open interest (OI) is the total number of outstanding contracts. Every contract has a buyer and a seller, so OI does not tell you direction. It tells you how much leveraged exposure exists and whether it is growing or shrinking.
Two related series round out the picture:
- Long/short ratio: the share of accounts or positions that are net long versus net short, as reported by the data source.
- Liquidations: forced closures when positions fall below maintenance margin. Hyperliquid's liquidation mechanics explain when that happens.
Why can these series carry information?
The usual argument is about positioning. When many traders hold leveraged positions on the same side, the market becomes fragile. A move against them triggers stops and liquidations, which push price further in the same direction.
That argument suggests two broad families of ideas:
- Contrarian: extreme funding or a lopsided long/short ratio marks crowding, and crowded trades tend to unwind.
- Confirmation: a price breakout accompanied by rising OI reflects new money entering, which some traders read as more durable than a breakout on falling OI.
Both stories are plausible, and both can be wrong for long stretches. Crowded trades can stay crowded while trending strongly. Treat every idea below as a hypothesis for a backtest.
Which funding and OI strategy ideas are worth testing?
The table lists illustrative structures. None is known to be profitable, and parameters are deliberately left open.
| Idea | Trigger | Filter | Direction | What could break it |
|---|---|---|---|---|
| Crowded-long fade | Funding crosses above a high percentile of its own history | Price below a short-term moving average | Short | Strong trends keep funding high for weeks |
| Crowded-short squeeze | Funding turns deeply negative | OI still rising | Long | Negative funding can precede further declines |
| OI-confirmed breakout | Price breaks a Donchian high | OI up over the last N bars | Long | OI rises on hedging as well as on new longs |
| Liquidation flush reversion | Long liquidations spike above a threshold | Higher-timeframe trend still up | Long | Cascades can continue for several bars |
| Ratio extreme | Long/short ratio at an extreme | Volatility regime filter | Contrarian | Ratio definitions differ across sources |
Some practical notes on building these:
- Normalize the input. Funding levels change across market regimes. A trigger based on a rolling percentile or z-score of funding is usually more stable than a fixed number.
- Use funding as a filter too. Instead of a trigger, funding can veto trades, for example skipping longs when funding is already very high.
- Go cross-asset. BTC funding or OI can gate a strategy on another asset. A SOL momentum strategy that only trades when BTC funding is moderate is a simple example.
How do you build a funding or OI strategy in Trigr?
In Trigr's no-code Studio, funding rate, open interest, long/short ratio and liquidations are API data nodes. They plug into the same graph as indicators: one trigger, any filters, a signal and a risk node. The no-code strategy builder guide covers the full structure.
A typical graph for the OI-confirmed breakout might be:
- Trigger: ETH 4H close above the 20-bar Donchian high.
- Filter: ETH open interest change over the last 6 bars above zero.
- Filter: BTC 1D close above its 100 EMA.
- Risk: 10% size, 2x leverage, long only, 4% stop-loss, ATR trailing stop, 30-bar time stop.
Before building, check the live data status board to see whether each series is currently fresh and how far its coverage goes back. Derivatives data often has shorter history than price data, and a backtest can only be as long as its shortest input.
If you work with an AI assistant, it can search the same catalog over MCP, draft this graph and run the backtest for you, subject to approvals. It cannot start live trading.
How do you keep the backtest honest?
Derivatives data is especially prone to two errors: reading a value before it existed and ignoring the cost of holding.
Point-in-time alignment
A funding rate is often labeled with the period it applies to, not the moment it became known. If your backtest attaches it to the wrong bar, the strategy effectively sees the future. The article on look-ahead bias in crypto backtests shows how easy this is to get wrong.
Trigr's engine uses only information available at each bar's close, carries coarser inputs forward rather than reading ahead, and fills orders at the next bar's open. Missing values are never filled with invented data.
Funding as a cost, not just a signal
Using funding as a signal and paying funding while you hold are separate things. A contrarian short entered when funding is high collects funding, which flatters the gross result; a long entered into high funding pays it.
In Trigr, funding costs are opt-in and off by default, so the first result is labeled gross. When you enable funding, it accrues at roughly 8-hour settlements, signed by side, using the source venue's historical series (Binance USDT-M for history) or a flat per-8h rate you choose. Hyperliquid itself settles hourly, and a source-venue series is not a quote of what Hyperliquid would have charged, so treat the net number as an estimate. The backtesting docs describe exactly what is and is not modeled, and the guide to slippage and funding in perp backtests walks through reading the gross-to-net gap.
Add a flat slippage assumption as well. Trigr applies it in basis points against you on every fill; it does not model order-book depth or market impact, so pick a value appropriate to the market and your size.
Reading the result
Funding and OI strategies tend to trade rarely, which means few trades and wide uncertainty. An ML optimization run on Trigr reports the Deflated Sharpe Ratio, which discounts for the number of variants tried, and the Probability of Backtest Overfitting; a standard backtest marks both as not yet computed. If you tested twenty funding thresholds and kept the best, expect the deflated figure to be much less impressive than the raw Sharpe.
The shaded trailing 25% in Studio is a recent-period diagnostic, not an out-of-sample holdout. After you freeze a version, forward-testing on a paper agent is the honest next check.
What are the main pitfalls?
- Regime dependence. Funding behaves differently in bull and bear phases. A fade that works in a range can bleed in a trend.
- Sparse signals. Extreme readings are rare by definition. Ten trades are not enough to separate skill from luck.
- Source differences. Aggregated OI, single-venue funding and long/short ratios are built differently. Know which series your node reads.
- Short history. Many derivatives series start later than price data, so the backtest window may miss whole market cycles.
- Leverage creep. Low-frequency strategies tempt traders to size up. Backtests are not guarantees; perps are leveraged and can lose more than expected.
Next steps
Browse published strategies on the strategy marketplace to see how others combine derivatives data with price filters, then build one simple funding or OI idea and backtest it with funding and slippage turned on.