Each instrument traded on ZUBR is based on the composite Index calculated using a certain methodology. To calculate the ZUBR Indices, we use the price data from the following spot exchanges (Reference Exchanges).
Exchange Name |
Basic Weight |
Gemini |
20% |
Bittrex |
20% |
Kraken |
20% |
Bitstamp |
20% |
Coinbase Pro |
20% |
To calculate the Index, only data from the active exchanges can be used. If any of the mentioned platforms is not able to provide us with the actual data it will be excluded from the Index calculation (“Excluded Exchanges”) as per the rules below.
To prevent the Index value deviation from the fair price of the underlying asset, we exclude the exchange, at which the price differs from the correct price significantly.
If the best price levels obtained from any of the exchanges are not updated (the best bid and ask prices do not change within 15 seconds), the exchange shall be excluded from the Index calculation until the updated price is received.
Below are the Indices that are currently calculated by ZUBR:
|
BTCUSD Index |
ETHUSD Index |
ETHBTC Index |
Description |
US Dollar price of one (1) bitcoin |
US Dollar price of one (1) ether |
Bitcoin price of one (1) ether |
Value Precision |
0.1 |
0.01 |
0.00001 |
Time Discretization |
one (1) second |
||
Data Source |
External |
External |
Internal |
Maximum Number of Exchanges |
5 |
5 |
- |
ZUBR Indices act as the Mark Price for the instruments traded on ZUBR and trigger a client’s position liquidations on the exchange. Therefore, they should represent fair market prices for the underlying assets at any moment of time.
That is why ZUBR does not use a time-weighted average. It may cause the Index deviation in case of technical problems experienced by any of the Reference Exchanges. Moreover, there can be data streaming delays during significant market movements, or connectivity problems including the ones related to ZUBR.
ZUBR Indices calculation methodology is designed to prevent price anomalies and avoid any price manipulations.
Comments
0 comments
Article is closed for comments.