OPEN-SOURCE SCRIPT
Updated

Aggregated Perpetual Futures Open Interest

373
Purpose
Aggregates perpetual futures open interest across Binance, Bybit, and OKX for the base currency of the asset loaded in your tradingview window.

How It Works
Symbol detection: The script grabs syminfo.basecurrency (e.g., “BTC”) from whatever market is on screen.

Ticker mapping: It constructs the three perp-OI feeds that TradingView publishes in the form EXCHANGE:<BASE>USDT.P_OI

Data request: For each feed it fetches the full OHLC candle (request.security) on the chart’s timeframe. If a venue doesn’t list that perp, the request simply returns na.

Aggregation: The script adds the opens, highs, lows, and closes of all non-na feeds to produce a single aggregated OI candle.

General Notes

The status line shows each venue’s individual OI close.
Release Notes
Purpose
Aggregates perpetual futures open interest across Binance, Bybit, and OKX for the base currency of the asset loaded in your tradingview window.

How It Works
Symbol detection: The script grabs syminfo.basecurrency (e.g., “BTC”) from whatever market is on screen.

Ticker mapping: It constructs the three perp-OI feeds that TradingView publishes in the form EXCHANGE:<BASE>USDT.P_OI

Data request: For each feed it fetches the full OHLC candle (request.security) on the chart’s timeframe. If a venue doesn’t list that perp, the request simply returns na.

Aggregation: The script adds the opens, highs, lows, and closes of all non-na feeds to produce a single aggregated OI candle.

Coin denominated OI: Determined by using a contract multiplier (in all cases 1 contract != 1 coin).

General Notes
The status line shows each venue’s individual OI close.

In this update we added optionality to display coin denominated OI. Additionally, some of the language above was updated.

Disclaimer

The information and publications are not meant to be, and do not constitute, financial, investment, trading, or other types of advice or recommendations supplied or endorsed by TradingView. Read more in the Terms of Use.