BitMEX Enables Bech32 Sending Support

BitMEX is delighted to announce that customers can now withdraw bitcoin to the Bech32 (native SegWit) address format. This upgrade is effective immediately.


Bech32 Technical Details

Bitcoin currently has three address formats:

Address Format

Comments

Example Address

Pay to Public Key Hash (P2PKH)

Bitcoin’s original address format

Addresses starting with the number 1

19CPBGKkxj
4iPyfLu6E3
Wboydopqs6
U2GE

Pay to Script Hash (P2SH)

Enabled in April 2012

Addresses starting with the number 3

3BMEXScSmZ
yb22WhUpW6
XnX7FDwBbd
Xv2e

Bech32

The native SegWit address format

Addresses starting with bc1

bc1qdzac2x
4j6kcthjrc
dek4mdqghw
shkg30hgf60p

As of today, BitMEX is delighted to announce that customers can withdraw to all three address formats. Please note, when depositing to BitMEX, you must still send to our Pay to Script Hash (P2SH) format addresses, due to our multi-signature wallet solution. Bech32 address formats can currently only be used as the receiving address, when you withdraw from BitMEX.

This upgrade is part of BitMEX’s continued commitment to optimize our Bitcoin wallet infrastructure and technology, in order to reduce our usage of blockweight and to lower transaction fees for our customers. When BitMEX launched in 2014, we were one of the first companies to use P2SH multi-signature technology. BitMEX is keen to remain at the forefront of Bitcoin technology, and this announcement is only part of our wallet upgrade process, which will continue going forwards.

The Advantages of Bech32 Addresses

As explained in BIP173, the new address format has several advantages:

  • More efficient use of blockweight (and therefore lower fees)
  • Improved error detection
  • More efficient QR codes

Fee savings resulting from Bech32

The key advantage of Bech32 addresses is that transaction fees can be saved when spending bitcoin, which was already sent to a Bech32 address. Therefore this upgrade will not directly result in fee savings when customers withdraw from BitMEX, however in the next transaction, when the bitcoin already withdrawn from BitMEX is spent again, our customers may benefit from lower transaction fees.

When spending from a non-native address using SegWit, one must add around 20 bytes of overhead. When using native SegWit-style addresses (Bech32), this overhead is no longer necessary. The absence of this overhead generates the savings.

In the below tables we have quantified the blockweight savings. As one can see, based on our example 1 input 2 output transaction, in terms of blockweight, native SegWit spends save around 37% compared to pre-SegWit style spends and 17% compared to non-native SegWit spends.

Typical transaction sizes for a 1 input 2 output transaction (Illustrative figures)

Input redemption type

Witness size (bytes)

Witness size
(virtual bytes)

Total transaction size (bytes)

Total transaction size (virtual bytes)

P2PKH

110

110

220

220

P2SH SegWit

110

28

240

167

SegWit (Native)

110

28

220

138

(Source: BitMEX Research)

Typical percentage savings for a 1 input 2 output transaction (Illustrative figures)

Input redemption type

Witness size (bytes)

Witness size
(virtual bytes)

Total transaction size (bytes)

Total transaction size (virtual bytes)

P2SH SegWit compared to P2PKH

0%

75%

(9%)

24%

SegWit (Native) compared to P2PKH

0%

75%

0%

37%

SegWit (Native) compared to P2SH SegWit 

0%

0%

8%

17%

(Source: BitMEX Research)

Since the savings are generated by the witness discount on the signature/scripts, the more inputs a transaction has, the higher the percentage savings. Therefore larger transactions, with more than one input, will typically experience higher savings that those in the above table.

Future BitMEX Wallet Upgrades

The next upgrade priority for the BitMEX wallet is enabling SegWit (non-native), compared to our current non-SegWit P2SH multi-signature wallet solution.

As explained above, SegWit can result in significant blockweight savings of around 25% to 40%, however in the case of BitMEX, the savings will be even higher. A BitMEX withdrawal is a 3 of 4 multi-signature P2SH transaction, each input therefore requires three digital signatures and four public keys. Currently, a typical 2 input 2 output BitMEX withdrawal can be as large as 1,200 bytes. The benefits of applying the witness discount to these large transactions is far greater than for typical non-BitMEX transactions. Therefore BitMEX would benefit from a blockweight saving of around 65% by adopting SegWit.

If you would like to help develop our Bitcoin wallet technology, please consider applying here to join the team.

Q1 2020 Index Weights

On 27 December 2019 12:00:05 UTC, BitMEX will update its index weights.

From today, the hypothetical values of the indices with the new weights will be published as the “NEXT” index family (Eg .BXBT_NEXT). 

As of 27 December 2019 at 12:00:05 UTC, assuming no constituent exchanges have been excluded due to Index Protection Rules, BitMEX index weights will be:

 
Binance
Bitstamp
Bittrex
Coinbase
Gemini
Huobi
Itbit
Kraken
Poloniex
.BXBT
10.61%
2.53%
52.30%
6.89%
4.21%
23.46%
.BETH
4.69%
58.81%
7.62%
28.88%
.BETHXBT
60.59%
5.96%
25.83%
4.13%
3.49%
.BXRPXBT
67.98%
3.62%
6.56%
16.24%
5.60%
.BBCHXBT
47.18%
5.97%
46.85%
.BLTCXBT
51.94%
10.07%
34.30%
3.69%
.BEOSXBT
46.98%
53.02%
.BADAXBT
83.48%
6.20%
7.36%
2.96%
.BTRXXBT
57.21%
42.79%

The BitMEX “NEXT” indices are available for your reference and include the index weights calculations. You can also read BitMEX “NEXT” specific documentation to further understand BitMEX indices.

If you have any further questions, please contact Support via our contact form.

Q1 2020 Quarterly Futures Listings

On 13 December 2019 08:30 UTC, BitMEX will list new quarterly futures.

Please see the table below of listing and settlement dates for current and upcoming futures contracts for Q1 2020. The new contracts are in bold.

Code Pair Listing Date Settlement Date
ADAZ19 Cardano / Bitcoin 13 September 2019 27 December 2019
ADAH20 Cardano / Bitcoin 13 December 2019 27 March 2020
BCHZ19 Bitcoin Cash / Bitcoin 13 September 2019 27 December 2019
BCHH20 Bitcoin Cash / Bitcoin 13 December 2019 27 March 2020
EOSZ19 EOS Token / Bitcoin 13 September 2019 27 December 2019
EOSH20 EOS Token / Bitcoin 13 December 2019 27 March 2020
ETHZ19 Ether / Bitcoin 13 September 2019 27 December 2019
ETHH20 Ether / Bitcoin 13 December 2019 27 March 2020
LTCZ19 Litecoin / Bitcoin 13 September 2019 27 December 2019
LTCH20 Litecoin / Bitcoin 13 December 2019 27 March 2020
TRXZ19 Tron / Bitcoin 13 September 2019 27 December 2019
TRXH20 Tron / Bitcoin 13 December 2019 27 March 2020
XRPZ19 Ripple Token (XRP) / Bitcoin 13 September 2019 27 December 2019
XRPH20 Ripple Token (XRP) / Bitcoin 13 December 2019 27 March 2020
XBTZ19 Bitcoin / USD 15 March 2019 27 December 2019
XBTH20 Bitcoin / USD 13 September 2019 27 March 2020
XBTM20 Bitcoin / USD 13 December 2019 26 June 2020

 

Temporary change to BitMEX .BBCHXBT Index, 28 November 2019

Effective 28 November 2019 at 02:00 UTC, BitMEX will temporarily remove Binance from its .BBCHXBT index in response to Binance’s scheduled symbol change. This Binance symbol change is expected to take 8 hours and will affect the BitMEX .BBCHXBT index only. Binance will be reintroduced as a constituent of .BBCHXBT once trading on Binance has resumed. 

If you have any further questions, please contact Support via our contact form.

Websocket Latency, 26 November 2019

Between 21:30 UTC 25 November 2019 and 07:05 UTC 26 November 2019 the Websocket API was running with degraded capacity. This resulted in slightly more latent feeds during this time and some isolated occurrences of substantial lag during traffic spikes correlated with large market moves.

The issue was identified when latency thresholds were breached in our automated monitoring systems around 06:55 UTC. From 07:05 the issue was resolved and full capacity was restored. We continue to monitor the impacted services closely.

The issue was caused by incorrect CPU pinning following a release of a market data distribution component at 21:30 UTC 25 November 2019. The impact of this was only observed during large traffic spikes which occurred several hours later and so was not identified during the post release checks at the time. The configuration of this service has been corrected and the deployment tested to prevent this from happening again.

We apologise for any inconvenience this may have caused. If you have any further questions, please contact Support via our contact form.

Updated Fees for ETHZ19 – Effective from 29 November 2019 12:00:05 UTC

We are rolling out reduced fees and rebates on ETHZ19 between 29 November 2019 12:00:05 UTC and 27 December 2019 12:00 UTC.

During this period, maker fees will be -0.025% and taker fees will be 0.075% for all trades on ETHZ19 only.

When the ETHH20 contract is listed, it will have a maker fee of -0.05% and a taker fee of 0.25%. For more information you can visit our updated Fees page here.

Thanks for your continued support!

If you have any further questions, please contact Support via our contact form.

Email Privacy Issue: What Is Happening And How Can We Help

We understand many of you are concerned about the email disclosure which happened over this weekend and no doubt have many questions.

Our teams across the world have been working around the clock to protect your account security and make sure we are back on course. Our support team has already assisted many of our users and we are continuing to establish contact with everyone. This is a staggered process, to ensure that the proper processes are all followed, the delivery is logistically smooth and that all underlying security concerns are appropriately covered. If you have not yet heard from us already, you will do very soon.

We would like to apologise unreservedly for the concern this has caused. Below contains further information about what happened, how we can assist you and some steps that you can take to improve your protection.

What happened?

On Friday, November 1 at 06:00 UTC, many of our users received an email which contained the email addresses of other users in the “To:” field. This was a general email update to our users about upcoming changes to the weighting of our indices. As a result, many BitMEX user email addresses, including a large number of inactive addresses, were disclosed to other users in small batches. No other information was disclosed.

BitMEX is a global business that sends emails to many different email providers. Email deliverability itself is a multi-layered problem, involving decades of work in building sender reputation systems and automatic spam filters. Unfortunately, this makes the job of large services such as BitMEX difficult at times: we only send mass emails to all users on rare occasions. We intend to keep a high signal-to-noise ratio, and only send emails when absolutely necessary.

The index change we published on 1 Nov was of sufficient importance – it will impact pricing of all of our products – that we felt it necessary to inform all our users about it. However, bulk mail sends such as this are a difficult and complex undertaking when it’s on a global scale, to all recipients. Some mail servers, especially the global arms of large brands like Yahoo and 163, have very tight controls that are often triggered when we send large amounts of mail. For system notifications such as withdrawals, password resets, and liquidations, it is imperative that the customer receives mail dependably.

To remedy this, we built an in-house system to handle the necessary rendering, translation, staging, and piecemeal (as not to trigger rate limits) sending of important email. BitMEX has not sent an email to every customer at once since 2017, and much has changed since then. When we initiated the send, it became clear that it would take upwards of 10 hours to complete, and there was a desire on the team to ensure users received the same material information on a more reasonable timescale.

To handle this, the tool was quickly rewritten to send single SendGrid API calls in batches of 1,000 addresses. Unfortunately, due to the time constraints, this was not put through our normal QA process. It was not immediately understood that the API call would create a literal concatenated “To:” field, leaking customer email addresses. As soon as we became aware, we immediately prevented further emails from being sent and have addressed the root cause. Since then we have been aiding all who have been affected as best we can and mitigating the damage to contain the leak.

BitMEX is a company that takes engineering seriously, and we are disappointed that this lapse in care has resulted in unwanted disclosure for our customers. We believe that processes, not engineers, are to blame for these failures. Our processes failed here. We are working around-the-clock to revamp them and to ensure that even the simplest-looking code changes are put under strict review.

Additionally, and unrelated to this action, the BitMEX Twitter account was accessed by an external individual. The account was back under BitMEX control within 6 minutes and re-secured, and the event is under security review.

Beyond email addresses, no personal or account information has been disclosed. At no point were any of our core systems at risk.

Who was affected?

Most BitMEX users were affected by this action. You can self-diagnose your exposure with the following steps:

  • If you received an email about the index change, and your email was the only one listed in the “To:” field, you were not affected.
  • If you received the index change email, and you saw multiple addresses in the To: field, you were affected.
  • If you did not receive an index change email, you may have been affected and we still recommend that you follow steps below to improve your protection online. While the system was cut-off before it completed entirely, many recipients began marking BitMEX emails as spam, understandably out of hope that it would stop further emails. This caused deliverability issues at some hosts, causing mail not to be delivered. Unfortunately, someone else in your batch may have received the email, exposing your email address.
    • The deliverability issues caused by the spam reporting caused some follow-up password resets to be delayed for several hours. Our operation teams remedied this by 06:00 UTC on Nov 2.

What are we doing to help?

After the discovery of the disclosure, BitMEX employees have since worked through the nights and days to reduce risk for users. We are aware that many users reuse email addresses across services. This, combined with a very human tendency to reuse passwords, meant that many of our users may have been at risk due to password hash dumps on other platforms, even ones unrelated to crypto.

For this reason, we took the following steps after we notified our users of the disclosure:

  • Our Security and Support teams began enhanced monitoring of access patterns to flag accounts with suspicious activity after the disclosure. This led to several account password resets and human review with Support.
  • At 13:00 UTC on the day of the email, we conducted additional checks during our usual human review of withdrawals. We identified criteria that could be indicative of a compromise given the circumstances. We cancelled requests from accounts that (i) did not have two-factor authentication, (ii) were withdrawing to a previously unseen Bitcoin address, (iii) were submitted with previously unseen new IP address, and (iv) were made after the email address disclosure had occurred. All other withdrawal requests were unaffected. These actions were taken in the interest of protecting our users and those affected have already been contacted.
  • As it became clear that several groups were working to collate BitMEX email addresses in order to attempt to compromise them, BitMEX engineers forced a password reset for all users with balances and without Two-Factor devices. Affected users were notified via email (after a thorough QA review and retrospective on the original bug).
  • BitMEX Support (contact here) is working shifts with extra agents, continuing to handle customer requests to change email addresses, answer questions, and provide security assessment and advice.

If you are concerned about your personal exposure, on BitMEX or on any other platform, the best thing you can do is to enable Two-Factor Authentication on all critical services. Start with your email address first. We have  published advice on this topic, as have others, including this very helpful guide by Paul Stamatiou.

BitMEX engineering teams are working on new features to increase the number of security keys supported by the platform, to improve the signal of account notifications, and to give users more tools to avoid and contain account takeovers.

Do I need to do anything?

Although no-one’s personal information or account details beyond their email address were disclosed, as best practice, we recommend that you:

  • Please be vigilant against phishing attempts. Emails from BitMEX are sent from “support@bitmex.com” and “noreply@bitmex.com”. We recommend adding these addresses to your contacts list. We will never ask for your password.
  • Note that BitMEX will never ask you to transfer any funds. The only way to fund your BitMEX account is to send Bitcoin to your unique BitMEX deposit address. Your unique BitMEX deposit address will begin with “3BMEX” or “3BitMEX” and can be found on the deposit page of your BitMEX account.
  • Please take note of our official BitMEX communications channels. Only instructions provided via these avenues should be observed.
  • Protect your account by using strong and unique passwords; enabling Two-Factor Authentication (2FA) for all of your accounts (both BitMEX and personal); and to use a password manager.

We want to reassure you that beyond email addresses, no personal or account information has been disclosed. At no point during this issue were any of our systems at risk, and they remain secure, as we continue to take measures to enhance our security. Your privacy and security remain our top priority.

In the meantime, if you need any immediate assistance, please contact Support via our contact form.

Vivien Khoo,
Deputy Chief Operating Officer

Updated: Statement on the Email Privacy Issue Impacting Our Users

Earlier today, some of our users received an email which contained the email addresses of other users in the ‘to’ field. We apologise for the concern this communication may have caused. This was the result of a software error which has now been addressed.

BitMEX takes the privacy and security of our users very seriously. Rest assured that in this instance, beyond email addresses, no other personal data or account information have been disclosed and no further emails have been sent. The error which has caused this has been identified and fixed, ensuring our usual high standards of privacy are upheld.

We are continuing work to ensure this will not occur again in future, and will be introducing additional features to further protect our users. Further communications on this matter will be issued in due course.

In the meantime, please find below some immediate guidance which should be observed in order to ensure the continued safety of your account:

  1. Please be aware of phishing attempts. Emails from BitMEX are sent from “support@bitmex.com” and “noreply@bitmex.com”. Please add these email addresses to your contacts list to ensure that these emails do not land in your spam folder. BitMEX will never ask for your password.

  2. BitMEX will never ask you to transfer funds. The only way to fund your BitMEX account is to send bitcoin to your unique BitMEX deposit address. Your unique BitMEX deposit address will begin with “3BMEX” or “3BitMEX” and can be found on the deposit page of your BitMEX account.

  3. Please take note our official BitMEX communications channels. These are our primary, official social media communications channels and only instructions provided via these avenues should be observed.

  4. We would like to remind all of our users to please protect their accounts by using strong and unique passwords; enabling Two-Factor Authentication (2FA) for all of your accounts (both BitMEX and personal); and to use a password manager. Further advice can be found here.

We will continue to communicate updates on our blog. We take the security and privacy of our users very seriously and will take steps to ensure this does not occur again in future.

Statement on Email Privacy Issue Impacting Our Users

We are aware that some of our users have received a general user update email earlier today, which contained the email addresses of other users.

Our team have acted immediately to contain the issue and we are taking steps to understand the extent of the impact. Rest assured that we are doing everything we can to identify the root cause of the fault and we will be in touch with any users affected by the issue.

The privacy of our users is a top priority and we are very sorry for the concern this has caused to our users.

BitMEX Indices Update

On 22 November 2019 at 12:00:05 UTC, BitMEX will update its indices across all products to ensure that the reference prices our users trade against more closely reflect the market consensus price of underlying assets. This will allow you to trade against data which is better optimised for fairness, robustness and accuracy.    

We will achieve this by calculating index weights based on observed trading volumes across a broader set of index constituent exchanges. Volume data is obtained directly from each such exchange via API connection. This change could reduce the impact that movements on a single exchange that are contrary to the market consensus might have on your trading positions. Index calculations will continue to be transparent and easy to replicate.   

The affected indices are .BXBT, .BETH, .BETHXBT, .BXRPXBT, .BBCHXBT, .BLTCXBT, .BEOSXBT, .BADAXBT and .BTRXXBT.

When the constituent of an index is updated, the related index price may change. This is why over the coming days we will be publishing BitMEX “NEXT”, a new family of indices that will run in parallel and reflect anticipated changes. BitMEX “NEXT” indices will not be used for valuation or settlement but by publishing them in advance, we hope to help our users better understand any differences before changes are applied to our indices during the 22 November 2019 switchover.

Please see below some Q&As on the upcoming changes.

How will the updated indices be more representative?

  • More exchanges: BitMEX is adding three new exchanges to its constituent universe to make a total of nine exchanges. This expanded set of exchanges will be reviewed periodically and updated in line with market developments. Through these additions, more data will be available to assist HDR Global Trading Limited (“HDR”), as the operator of BitMEX trading platform, in its determination of the true price of each relevant underlying asset, creating a more accurate and robust reference price for our users.
  • More constituents per index: Every constituent exchange is considered for inclusion in every index. This may lead to data from more constituent exchanges being used in an index resulting in increased price accuracy in relation to its underlying asset.
  • Weights based on observed trading volumes: Updated indices will reflect higher weights for exchanges with higher volumes. This approach will ensure that BitMEX index prices are more representative of the trade price per trade than per exchange.

How are the index prices calculated?

Each BitMEX index price is calculated as a weighted average of the Last Price for each constituent exchange. Index prices are calculated and published every 5 seconds.

How are the weights calculated? 

For each index, BitMEX observes the traded volumes of the underlying asset, obtained directly via API connection, across each exchange in the constituent universe. Proprietary mechanisms are used to identify malformed and anomalous data, which is discarded. The BitMEX index weights are computed using this volume data with the calculation removing constituents with insufficient trade volume.   

For the avoidance of doubt, and in accordance with BitMEX Terms of Service, HDR accepts no responsibility for the accuracy of any volume (or other) data received from any exchange and used to calculate the price of any BitMEX index and excludes all liability for any claimed losses arising in connection with its calculation and publication of any such index.

When are the weights updated?

Index weights will be updated on a quarterly basis. The initial index weights are shown in the table below. After this initial update, future index weights will be updated immediately after quarterly future expiries at 12:00:05 UTC. The updates to the weights will be announced three weeks in advance.

As of 22 November 2019 at 12:00:05 UTC, assuming no constituent exchanges have been excluded due to Index Protection Rules, BitMEX index weights will be:

 

Binance

Bitstamp

Bittrex

Coinbase

Gemini

Huobi

Itbit

Kraken

Poloniex

.BXBT

26.81%

44.44%

6.19%

4.20%

18.36%

.BETH

18.12%

47.83%

8.15%

5.41%

20.49%

.BETHXBT

60.62%

2.76%

7.23%

24.53%

4.86%

.BXRPXBT

60.89%

2.72%

5.61%

9.63%

12.94%

3.31%

4.90%

.BBCHXBT

43.66%

2.93%

3.08%

10.21%

37.20%

2.92%

.BLTCXBT

57.08%

2.71%

16.67%

20.23%

3.31%

.BEOSXBT

57.55%

42.45%

.BADAXBT

80.84%

9.20%

6.84%

3.12%

.BTRXXBT

67.75%

32.25%

How can I track the prices of the new indices?

BitMEX will introduce a new family of indices, the BitMEX “NEXT” indices. The purpose of BitMEX “NEXT” indices is to display, in advance, the hypothetical prices of BitMEX indices which include any new weights, allowing our traders to experience and better understand the potential impact of forthcoming index changes. BitMEX “NEXT” indices will be published on the BitMEX website and API.

The weights for BitMEX “NEXT” indices will be updated as soon as new BitMEX index weights are announced. On 22 November, once the weights are updated for BitMEX indices, the BitMEX indices prices will be the same as the BitMEX “NEXT” indices.

Please note that BitMEX “NEXT” indices are not used for valuation or settlement.

What can I expect when the index updates are switched on?

When the index weights are updated, index prices may experience small shifts. Experienced users will know that BitMEX is well equipped to handle large shifts thanks to our exchange protection mechanisms. We encourage you to monitor the differences between the current and future index prices using the BitMEX “NEXT” indices and factor possible shifts into your risk assessment.

Where can I find out more?

The BitMEX “NEXT” indices are available for your reference and include the index weights calculations. You can also read BitMEX “NEXT” specific documentation to further understand BitMEX indices.

If you have any further questions, please contact Support via our contact form.

 

HDR Global Trading Limited Hires Derek Gobel as General Counsel

As a growing company we are always looking to bring on exciting new talent. It is our mission to be as successful and relevant in decades to come, as we are today. To do this, we recognise we need the right people, resources and capabilities to help us stay ahead of the market and continue to provide the best experience for our traders.  

This is why we are thrilled to announce that HDR Global Trading Limited has appointed Derek Gobel as our group’s General Counsel. He will oversee the group’s legal function and help us move forward in today’s continually evolving regulatory environment.

Derek brings with him 28 years of experience working on a wide range of legal matters, including his most recent role as BNP Paribas’ General Counsel for APAC. Recognised in the 2017 Legal 500’s GC Powerlist in China and Hong Kong, we look forward to having him on board.

Q4 2019 Quarterly Futures Listings & TRX Index Rename

On 13 September 2019 at 08:30 UTC, BitMEX will list new quarterly futures.

Please see the following tables for listings and settlements for current and upcoming futures contracts for Q4 2019. Bolded rows are the new contracts.

The .TRXXBT index will retire on 27 September 2019. It will be replaced by the .BTRXXBT Index. TRXU19 will reference .TRXXBT until its Settlement Date, TRXZ19 will reference .BTRXXBT from its Listing Date. 

Code Pair Listing Settlement
ADAU19 Cardano / Bitcoin 14 June 2019 27 Sept 2019
ADAZ19 Cardano / Bitcoin 13 Sept 2019 27 Dec 2019
BCHU19 Bitcoin Cash / Bitcoin 14 June 2019 27 Sept 2019
BCHZ19 Bitcoin Cash / Bitcoin 13 Sept 2019 27 Dec 2019
EOSU19 EOS Token / Bitcoin 14 June 2019 27 Sept 2019
EOSZ19 EOS Token / Bitcoin 13 Sept 2019 27 Dec 2019
ETHU19 Ether / Bitcoin 14 June 2019 27 Sept 2019
ETHZ19 Ether / Bitcoin 13 Sept 2019 27 Dec 2019
LTCU19 Litecoin / Bitcoin 14 June 2019 27 Sept 2019
LTCZ19 Litecoin / Bitcoin 13 Sept 2019 27 Dec 2019
TRXU19 Tron / Bitcoin 14 June 2019 27 Sept 2019
TRXZ19 Tron / Bitcoin 13 Sept 2019 27 Dec 2019
XRPU19 Ripple Token (XRP) / Bitcoin 14 June 2019 27 Sept 2019
XRPZ19 Ripple Token (XRP) / Bitcoin 13 Sept 2019 27 Dec 2019
XBTU19 Bitcoin / USD 15 Mar 2019 27 Sept  2019
XBTZ19 Bitcoin / USD 14 June 2019 27 Dec  2019
XBTH20 Bitcoin / USD 13 Sept 2019 27 Mar 2020