Bitrue Announces XRP Pairs for EOS, VeChain (VET), NEM (XEM), and Polymath (POLY)

Siamak Masnavi

On Monday (January 14th), Singapore-headquartered cryptocurrency exchange Bitrue announced that by the end of January it would be listing XRP-based trading pairs for EOS, NEM (XEM), Polymath (POLY), and VeChain (VET).

Bitrue, which was founded in 2018, has quickly become a favorite with members of the XRP community because of the high degree of enthusiasm, support, and transparency shown by its management towards XRP. What is interesting about Bitrue is that it supported XRP as a base currency on the day that its trading platform was launched (19 July 2018).

Here is how Bitrue announced today's news on Twitter:

We need to remember what Bitrue announced on 27 December 2018:

And right after the start of 2019, Bitrue has been working hard to keep this promise:

  • January 3rd: XRP-based trading pairs added for TRON TRX), Stellar (XLM), NEO, Gas (GAS), and OmiseGo (OMG).
  • January 4th: XRP-based pair added for Bee Token (BEE).
  • January 7th: XRP-based trading pairs for Holo (HOT), Pundi X (NPSX), district0x (DNT), and Propy (PRO) announced (to be listed by January 11th).
  • January 11th: Trading for all four XRP-based pairs announced on January 7th was enabled.

So, by the end of last week, Bitrue had 26 XRP trading pairs: BCH/XRP; ETC/XRP; GTO/XRP; GUSD/XRP; KNC/XRP; LINK/XRP; LTC/XRP; PAX/XRP; QKC/XRP; TUSD/XRP; WAN/XRP; WTC/XRP; ZRX/XRP; XRP/BTC; XRP/USDT; XRP/ETH; XRP/TRX; XRP/XLM; XRP/NEO; XRP/GAS; XRP/OMG; BEE/XRP; HOT/XRP; NPXS/XRP; DNT/XRP; and PRO/XRP.

Also, on January 11th, Bitrue announced that four more XRP trading pairs would get listed within the next 2-3 weeks (i.e. by January 31th):

And since we had 26 XRP trading pairs before today's announcement, it looks like Bitrue will have at least 30 XRP trading pairs by the end of this month, just as they promised on January 11th.

Crypto Investors Buy Bitcoins at $0.32 as Amazon Cloud Outages Affect Exchanges

Update 10:32 UTC - It soeems some cryptocurrency traders were also able to buy Ethereum's ether at $0.33 per coin as cryptocurrencies seemingly flash-crashed on BitMax.

The exchange hasn't yet commented on the incident and has only made it clear withdrawals are halted on its platform. Rolling back the trades may be a possibility.


Cryptocurrency investors were able to buy bitcoin for as little as $0.3 worth of USDT after Amazon‘s cloud service, AWS, suffered an outage that affected various crypto exchanges.

According to Founding partner at Primitive Ventures Dovey Wan, an unnamed Asian exchange saw price instability affect in a way that some trades were executed and allowed investors to buy bitcoin, which was trading at around $10,200 at the time, for less than $1 in Tether’s stablecoin.

The image Dovey Wan posted reportedly came from a Telegram group related to BitMax. The order book data, however, may not have come from BitMax itself as the exchange isn’t certain it's from its own platform. Since the outage, however, it has halted withdrawals.

Other cryptocurrency exchanges were notably also affected by AWS’ outage. Binance, one of the world’s leading crypto exchanges in terms of trading volume, revealed the outage affected some of its users throughout the world. As its CEO Changpeng Zhao tweeted:

KuCoin, another popular Exchange, posted a notice on its website revealing that “due to the overheating of part of our chassis in the machine room we deployed in AWS, Tokyo, part of our services might become unavailable.” It added its engineers were looking o deploy resources to deal with the problem.

On its status page, AWS reports its facilities in Tokyo have been facing problems, but the company has claimed it found the root cause of the problem and working to recover from the problem.

AWS' status pageSource: AWS

Amazon Web Services notably controls a large part of the cloud market, and runs the backend of various popular websites – including Netflix, Pinterest, Spotify, and Slack. It faced other services outages in the last few months and when it did, a large part of internet-based services relying on it went down.