Custom TradingView Indicators for DEX Trading: Pine Script for Hyperliquid Funding, Open Interest and Alerts

Sources checked September 27, 2026: TradingView’s blog posts of September 21 and 23, 2026 on Hyperliquid derivative metrics; the Pine Script docs (first indicator, limitations, alerts, publishing); the Advanced Charts docs on custom indicators; tradingview.com/pricing; TradingView symbol search; DexScreener’s docs. The _FR/_OI values were matched against the Hyperliquid API on September 25, 2026.

1. How to create a custom indicator in TradingView (5 steps)

A custom indicator is a Pine Script program that TradingView runs on every bar of your chart. The procedure is the same for a stock or a DEX market; what changes for DEX trading is which symbol you open and which data the script can reach.

1. Open a DEX symbol on tradingview.com. Search the market in the symbol box, for example HYPERLIQUID:BTCUSDC.P (Hyperliquid BTC perp) or a Raydium pool. Your indicator will calculate on that venue’s own candles.
2. Open the Pine Editor. Select the “Pine Editor” tab at the bottom of the chart.
3. Create a new indicator. Open the editor’s dropdown menu (the arrow beside the script name) and choose “Create new” → “Indicator”. Replace the template with your code; every script on this page starts with //@version=6, the current Pine Script version.
4. Save. Press Ctrl+S (Cmd+S on macOS) and name the script. It is stored in your TradingView account and stays private unless you publish it.
5. Add to chart, then set an alert. Click “Add to chart”. To be notified, create an alert (Alt+A / ⌥+A), pick your script as the condition and choose Once Per Bar Close.

You do not have to write code to get started. TradingView lists 400+ built-in indicators and 100,000+ community scripts on its pricing page. Community scripts are in the Community tab of the “Indicators, Metrics & Strategies” menu (or at tradingview.com/scripts). Pine’s publishing docs describe three kinds: open-source (you can read and copy the code), protected (closed code, free to add) and invite-only (closed code, usable only by people the author invites). An open-source script is the safest start for DEX trading, because you can check which symbol and timeframe it really requests. Every built-in, community or personal script takes one indicator slot, and the free plan has 2 per chart (see limits).

2. Where custom indicators run, and where they don’t

This is the question most DEX traders hit first. A Reddit thread that ranks on page 1 of Google (September 2026) asks how to load a Pine indicator into DexScreener’s TradingView chart, and it has no answer. The answer is that you can’t, and the reason is documented. DexScreener’s docs page on its charts (“TradingView Charts”) is about TradingView Advanced Charts, a library that websites embed. TradingView’s own documentation for that library says it ships more than 100 indicators, that the site’s developers can add custom indicators in JavaScript, that “users cannot create their own indicators”, and that “Pine Script® is not supported in the libraries.” The same applies to DEX apps that embed a TradingView chart.

TradingView Advanced Charts docs (Custom indicators) and DexScreener docs (TradingView Charts), checked September 27, 2026.

The workaround is to run the analysis on tradingview.com and trade in the app. Open the same market on TradingView (next section), add your script there, and let an alert tell you when to act. For Hyperliquid this is exact: the HYPERLIQUID: symbols use Hyperliquid’s own order book, so the candles your script reads are the ones your orders fill against.

Related:Crypto Risk Management for Perp Traders: Rules & Checklist

3. Which DEXs TradingView lists (September 27, 2026)

Pine Script cannot call outside APIs, so a custom indicator can only use markets TradingView itself carries. We queried TradingView’s symbol search exchange by exchange:

TradingView symbol search, queried September 27, 2026 with the search “SOL” per exchange (and “BTC” for dYdX). Raydium alone returned 50 results plus 992 more; LIGHTER, ASTER, EDGEX, GMX, JUPITER and DRIFT returned none.

Spot DEX symbols are per pool, not per token: RAYDIUM:SOLUSDT_7XAWHB is TradingView’s “Wrapped SOL / USDT on Solana” pool, named after the first characters of the pool address, and …_7XAWHB.USD is the same pool quoted in US dollars. So when you chart a low-cap Solana token, pick the pool with the most volume and keep the indicator on that pool, since two pools of the same token can print different wicks. Perp DEXs are the reverse: of the venues we cover, only Hyperliquid and dYdX are TradingView data sources. For Lighter, Aster and edgeX you can still chart the underlying coin on another venue, but not their own book, funding or open interest. How the venues compare is on best DEXs in 2026.

4. Indicator shortlist for perp traders, and Example 1

Most guides list the same families: trend, momentum, volatility, volume and liquidity. For a perp trader the useful question is what each one tells you and which perp-only number confirms it. Pick one tool per family: RSI, Stochastic and MACD are all momentum, so three of them agreeing is one opinion, not three.

For fast timeframes see DEX scalping strategy. Example 1 folds four of the families into one script, which matters on the free plan’s 2 slots: EMA 9/21/200 for trend, RSI as a momentum filter, ATR as a volatility filter and a volume-spike marker. It flags a pullback to the 21 EMA that holds inside an uptrend.

//@version=6
indicator("DEX starter: EMA 9/21/200, RSI, ATR, volume", overlay = true)
maxAtr   = input.float(3.0, "Skip signals when ATR is above (% of price)", minval = 0.1)
emaFast  = ta.ema(close, 9)
emaSlow  = ta.ema(close, 21)
emaTrend = ta.ema(close, 200)
rsi      = ta.rsi(close, 14)
atrPct   = ta.atr(14) / close * 100
volSpike = volume > ta.sma(volume, 20) * 2
upTrend  = close > emaTrend and emaFast > emaSlow
pullback = upTrend and low <= emaSlow and close > emaFast and rsi > 40 and atrPct <= maxAtr
plot(emaFast, "EMA 9", color = color.teal)
plot(emaSlow, "EMA 21", color = color.orange)
plot(emaTrend, "EMA 200", color = color.gray, linewidth = 2)
plotshape(pullback, "Pullback in uptrend", shape.triangleup, location.belowbar, color.green, size = size.small)
barcolor(volSpike ? color.yellow : na, title = "Volume above 2x its 20-bar average")
alertcondition(pullback, "Pullback in uptrend", "Pullback to EMA 21 held in an uptrend")

It works unchanged on HYPERLIQUID:BTCUSDC.P, a dYdX perp or a Raydium pool. On small pools raise the ATR threshold only if you accept more slippage; a 3% hourly ATR on a thin pool is a warning, not an opportunity. The RSI filter (above 40) stops the script from buying a pullback that has already turned into a breakdown. For the mirror-image short signal, flip the comparisons.

5. Hyperliquid perps data in TradingView

Hyperliquid is where TradingView goes furthest. Before July 2026 there was no Hyperliquid feed, so charting a Hyperliquid market on tradingview.com meant using a Binance or Bybit symbol as a proxy. On July 2, 2026 TradingView announced Hyperliquid and Trade[XYZ] data under the HYPERLIQUID: and HIP3XYZ: prefixes. On September 21, 2026 it added derivative metrics for “more than 170 Hyperliquid contracts” plus the HIP-3 markets of Trade[XYZ] and Paragon, over 300 contracts in all, and called Hyperliquid “the first decentralized exchange in our data set”. Two days later Hyperliquid was folded into TradingView’s aggregated open interest, funding and liquidation metrics.

TradingView blog posts of July 2, September 21 and September 23, 2026 (the last two re-read September 27, 2026); TradingView symbol search and chart pages.

Symbol names follow one pattern: the coin, then USDC, then .P for a perpetual. The BTC perp is HYPERLIQUID:BTCUSDC.P, the HYPE perp HYPERLIQUID:HYPEUSDC.P, and HYPE spot is HYPERLIQUID:HYPEUSDC. Candles and volume come from Hyperliquid’s own order book, not from a CEX average, which matters for stops and liquidations: a wick on Binance is not necessarily a wick on Hyperliquid. Chart setup itself is covered in our Hyperliquid TradingView guide; this page is about building indicators on top of that data.

6. Built-in derivatives indicators

Before writing code, check whether a built-in does the job. Built-ins cost one indicator slot like any script and need no maintenance.

• Funding rate (Fundamentals). On a Hyperliquid symbol it shows Hyperliquid’s hourly rate. TradingView’s own post points out that Hyperliquid pays funding every hour while most CEXs pay every eight, so do not compare the raw numbers one to one.
• Crypto open interest (Fundamentals). Rising price with rising OI means new positions are opening; rising price with falling OI is often shorts closing. Our open interest guide covers how to read it.
• Liquidations and the two long/short account metrics. These count accounts, not notional: many small longs can sit against a few large shorts.
• Mark price, index price, premium and basis. Hyperliquid triggers TP/SL orders and liquidations on the mark price, so plotting mark beside last price explains “why did my stop fire”.
• Aggregated OI and funding combine nine exchanges (Binance, Bitget, Bybit, Coinbase, Deribit, HTX, Kraken, OKX, Hyperliquid), and aggregated liquidations combine six. Aggregated funding is weighted by each exchange’s open interest. Useful context, but for a Hyperliquid trade use the non-aggregated Hyperliquid series.

7. Funding and OI in Pine Script: the _FR and _OI tickers

A built-in cannot feed your own logic, so for custom signals you need the metric as a series. TradingView serves each derivative metric as its own ticker: append _OI or _FR to a perp symbol. Its data feed types these series as “derivative-metrics”. We tested the Hyperliquid versions on September 25, 2026:

• HYPERLIQUID:BTCUSDC.P_OI opens as “BTCUSDC.P Open Interest” and read 3,380,586,782. A few minutes later Hyperliquid’s API put BTC open interest times the mark price at $3.375B, so the series is open interest in US dollars, counted on one side. HYPERLIQUID:SOLUSDC.P_OI read 725,131,762 against $725.3M from the API.
• HYPERLIQUID:BTCUSDC.P_FR read 0.125e-4, i.e. 0.0000125, exactly the API’s hourly funding of 0.00125%. So the series is the hourly funding rate as a fraction; multiply by 100 for percent. (_FUNDING does not exist.)

We found no public TradingView documentation for either suffix, so treat both as working but undocumented, and pass ignore_invalid_symbol = true so a missing series returns na instead of breaking the script. For the other seven metrics we found no documented ticker; use the built-ins.

8. Example 2: Hyperliquid funding rate panel

A separate pane showing the hourly rate in percent, coloured by sign, with the 0.00125% baseline marked. Paste it into a new indicator as in section 1 and click “Add to chart”.

//@version=6
indicator("Hyperliquid funding (% per hour)", precision = 5)
perp = input.symbol("HYPERLIQUID:BTCUSDC.P", "Hyperliquid perp")
// _FR = hourly funding as a fraction; x100 for percent
fr = request.security(perp + "_FR", timeframe.period, close, ignore_invalid_symbol = true) * 100
plot(fr, "Funding %/h", color = fr >= 0 ? color.teal : color.red, style = plot.style_columns)
hline(0.00125, "Baseline 0.00125%/h", color = color.gray)
hline(0, "Zero", color = color.silver)
plot(fr * 8, "8h equivalent %", display = display.data_window)
plot(fr * 24 * 365, "Annualised %", display = display.data_window)

The two extra plots only appear in the Data Window. They let you compare Hyperliquid with an 8-hour CEX rate (multiply by 8) or read an annualised carry without cluttering the pane. Over the 30 days to September 25, 2026, BTC’s hourly funding on Hyperliquid summed to 0.766%. It was positive in 93% of hours and exactly at the baseline in 72% of them, so a panel that stays mostly flat at 0.00125% is normal. The mechanics are in Hyperliquid funding rate explained.

9. Example 3: open interest vs price

This compares the percentage change in open interest with the percentage change in price over a lookback. It shades bars where price rose while OI fell, meaning the rally came from shorts closing rather than new longs.

//@version=6
indicator("Hyperliquid OI change vs price", precision = 2)
perp = input.symbol("HYPERLIQUID:BTCUSDC.P", "Hyperliquid perp")
len  = input.int(24, "Lookback (bars)", minval = 1)
oi = request.security(perp + "_OI", timeframe.period, close, ignore_invalid_symbol = true)
px = request.security(perp, timeframe.period, close)
oiChg = (oi / oi[len] - 1) * 100
pxChg = (px / px[len] - 1) * 100
plot(oiChg, "OI change %", color = color.orange)
plot(pxChg, "Price change %", color = color.blue)
hline(0, "Zero", color = color.gray)
bgcolor(pxChg > 0 and oiChg < 0 ? color.new(color.red, 85) : na, title = "Price up, OI down")

On an hourly chart a lookback of 24 compares with the same hour yesterday. Because perp is an input, one copy of the script works on any Hyperliquid market, including HIP-3 symbols. The two request.security() calls count toward the 40-call limit, and adding a CEX series for comparison (for example Binance’s OI ticker) uses one more.

10. Example 4: funding alert

Pine gives you two ways to raise alerts. alertcondition() (indicators only) creates a named condition you pick in the alert dialog. alert() is the newer function; TradingView’s docs say it “more or less supersedes” alertcondition(), and its message can carry live values. This script does both and marks the bars on the chart.

//@version=6
indicator("Hyperliquid funding alert", overlay = true)
perp  = input.symbol("HYPERLIQUID:BTCUSDC.P", "Hyperliquid perp")
level = input.float(0.01, "Alert above (% per hour)", step = 0.001)
fr = request.security(perp + "_FR", timeframe.period, close, ignore_invalid_symbol = true) * 100
hot = fr > level
plotshape(hot, "Funding above level", shape.triangledown, location.abovebar, color.red)
alertcondition(hot, "Funding above level", "Hyperliquid funding is above your level")
if hot and barstate.isconfirmed
    alert("Funding " + str.tostring(fr, "#.#####") + "%/h on " + perp, alert.freq_once_per_bar_close)

The default of 0.01% per hour is eight times the baseline (0.08% per 8 hours). Create the alert from the chart (Alt+A on Windows, ⌥+A on macOS) and choose this script as the condition. Then pick either the “Funding above level” condition or the script’s alert() calls, set the frequency to Once Per Bar Close, and choose where it goes: app, email, webhook and others. Alerts expire after 2 months on Essential and Plus; on Premium and Ultimate they can run without expiry.

11. From alert to webhook

Hyperliquid is not a TradingView broker, so an indicator cannot place a trade by itself. The usual chain is TradingView alert → webhook → your server or a bridge service → a Hyperliquid API wallet that can trade but not withdraw. TradingView’s webhook rules, from its help center:

• Webhooks are available on paid plans only (Essential and up), and two-factor authentication must be enabled.
• Requests come from four fixed IP addresses, only to ports 80 and 443, with a 3-second timeout and no IPv6.
• A message that is valid JSON is sent as application/json; anything else as plain text. Never put API keys or secrets in the message.

Bridge services that list Hyperliquid include Autoview (the platform is free; connecting a live exchange costs $39.99 a month) and Algoway ($9 a month for TradingView alert automation). A self-hosted receiver using the official Python SDK is the other route. The full setup, including API wallet permissions, is in the Hyperliquid TradingView guide, the Hyperliquid API guide and our API key security checklist. For alerts that stop at a notification, see price and liquidation alerts.

12. Plan limits and Pine limits

tradingview.com/pricing and the Pine Script docs (Limitations), checked September 27, 2026. Prices change; check the pricing page.

• Indicator slots are the first wall on the free plan: 2 per chart. The cheapest workaround is to merge several indicators into one script, as Example 1 does with EMAs, RSI, ATR and volume. You can do the same with funding, open interest and your entry signal. Each plot() in a merged script is free; only the script counts as a slot.
• Request calls: a script can make up to 40 unique request.*() calls (64 on Ultimate). Repeating a call with identical arguments usually does not count again, but a scanner that loops over 50 different symbols will hit the limit.
• Plot counts: 64 per script. plot(), plotshape(), barcolor(), bgcolor() and alertcondition() all count; hline() does not.

13. Writing Pine with AI: a checklist

Chatbots write plausible Pine quickly, and plausible is the problem: they mix versions and invent functions or tickers. Before you trust an AI-written indicator on a DEX chart:

• It starts with //@version=6 and compiles in the Pine Editor with no errors or warnings.
• Every request.security() uses a symbol that exists on TradingView (search it first) and leaves lookahead at its default, off.
• Alert logic waits for the bar to close (barstate.isconfirmed or Once Per Bar Close).
• Units are what you think: _FR is a fraction per hour, _OI is dollars.
• You have watched it on live bars for a while before wiring it to a webhook that trades.

14. Pitfalls: repainting, units, hourly funding

• Repainting. request.security() defaults to lookahead = barmerge.lookahead_off; keep it that way for anything you backtest. On a live bar values change until it closes, so trigger alerts Once Per Bar Close (or check barstate.isconfirmed, as in Example 4). TradingView’s docs recommend this to avoid repainting alerts.
• Units. _FR is a fraction per hour; _OI is dollars on one side. If you compare a Hyperliquid hourly rate with a Binance 8-hour rate without multiplying by 8, Hyperliquid looks eight times cheaper than it is.
• Venue-specific prices. An indicator on BINANCE:BTCUSDT.P is not an indicator on Hyperliquid. Hyperliquid’s mark price blends its oracle, its own book and CEX perp prices, so levels differ slightly; use the HYPERLIQUID: symbol when your stop lives there.
• Pool-specific prices. On spot DEXs each pool is its own symbol. An indicator on a thin pool can fire on a wick that the main pool never printed.
• Missing data. A new or delisted market may have no _OI or _FR series; ignore_invalid_symbol = true returns na, so guard your logic with na() checks before comparing.
• Lighter and Aster. Their funding and OI exist only in their own APIs. If you trade there, log the data yourself and use TradingView for price structure only.

If you are new to on-chain trading, start with what a DEX is and how to use Hyperliquid.

15. FAQ

Disclosure: HOLYGRAIL is our Hyperliquid referral code; we earn a share of referred accounts’ fees at no cost to you. We have no relationship with TradingView, DexScreener, Autoview or Algoway. TradingView listings, docs and prices were checked on September 27, 2026; the Hyperliquid tickers and values were checked on tradingview.com and against the Hyperliquid API on September 25, 2026. TradingView features and prices change. The scripts are examples, not trading advice.