TradingView
JanLosev
8 maj 2023 13:52

Open Interest All Exchanges 

COINBASE:BTCUSD240
Bitcoin / United States DollarCoinbase

Beskrivning

⋅
The indicator collects data from available exchanges based on open interest. The indicators are calculated in the amount of Bitcoin.

Below are the tickers of the exchanges that provide the data:
- BITFINEX:BTCUSD
- BITFINEX:BTCUST
- KRAKEN:BTCUSDPERP
- BITMEX:XBTUSD
- BITMEX:XBTUSDT
- BINANCE:BTCUSDTPERP
- BINANCE:BTCUSDPERP (due to low volumes and limitations of 40 requests of the request.security function, the code contains data without using the calculation)

For me, Open Interest indicators play an important role in the trading system, for this reason I share with you. I am not a financial advisor.

**Open for cooperation**

Versionsinformation

⋅
Ticker bug fixed (removed):
- BINANCE:BTCUSDPERP

The calculation of the data is still in Bitcoin.
p.s 1Bitcoin = 1Bitcoin. Think about it.

Versionsinformation

⋅
1. Fixing errors in code
2. Improved script performance, thanks @NoveltyTrade
3. Indicator list updated:
- BITFINEX:BTCUSD
- BITFINEX:BTCUST
- KRAKEN:BTCUSDPERP
- BITMEX:XBTUSD
- BITMEX:XBTUSDT
- BINANCE:BTCUSDTPERP
- BINANCE:BTCUSDPERP
VolumeVolume IndicatorOIOpen Interestexchange
Kommentarer
ShahzibRehmanAwan
⋅
nice effort good indicters i also Learn Open intret education and mathodlge in MP Professional trader youtube chennal its free education
JanLosev
⋅
@ShahzibRehmanAwan, Thank you, good luck to you.
fondZebra16015
⋅
Thank you! Binance seems to dominate by far, making the others irrelvant in Volume. But this script and the collection of the tickers of the different exchanges was very helpful!
NoveltyTrade
⋅
to get all binance data you need you may use much less securities(4 times less) at your script, Here is example for KRAKEN how to use only 2 securities instead of 8 securities:
f_req(simple string _ticker, simple string _ticker_oi) => [_o, _c, _h, _l] = request.security( _ticker, "", [open, close, high, low]) [_o_oi, _c_oi, _h_oi, _l_oi] = request.security(_ticker_oi, "", [open, close, high, low]) [_o_oi / _o, _c_oi / _c, _h_oi / _h, _l / _l_oi] [OPEN_KRAKEN, CLOSE_KRAKEN, HIGH_KRAKEN, LOW_KRAKEN] = f_req('KRAKEN:BTCUSDPERP', 'KRAKEN:BTCUSDPERP_OI') // it gives the same as below but uses 4 times less securities // OPEN_KRAKEN = request.security('KRAKEN:BTCUSDPERP_OI',"", open) / request.security('KRAKEN:BTCUSDPERP',"", open) // CLOSE_KRAKEN = request.security('KRAKEN:BTCUSDPERP_OI',"", close) / request.security('KRAKEN:BTCUSDPERP',"", close) // HIGH_KRAKEN = request.security('KRAKEN:BTCUSDPERP_OI',"", high) / request.security('KRAKEN:BTCUSDPERP',"", high) // LOW_KRAKEN = request.security('KRAKEN:BTCUSDPERP_OI',"", low) / request.security('KRAKEN:BTCUSDPERP',"", low)
JanLosev
⋅
@NoveltyTrade, Thank you for your part of the code 🤝, I will update it.
The early script was written according to personal capabilities.
JanLosev
⋅
@NoveltyTrade, We fix it
Mer