ZelCore v2.0.4 Update — XRP, Custom Explorers & more

Flux Official
2 min readJun 6, 2019

--

ZelCore Desktop release today, Mobile will be available after App Stores reviews are complete

NOTE: BitMEX integration has been put on hold only for a little bit. There are potential legal items to overcome between BitMEX and our proxy service built into ZelCore that must be addressed before a release. We will keep the community updated.

Please see the release notes here

Release Notes (See top Note about BitMEX)

Features

  • User can select their own block explorers, APIs, Electrum, and node endpoints, can use private ones if desired
  • Portfolio Tracker — Edit records and import/manage ZelCore wallets transaction history
  • Monero rescan option with sync status
  • Supported languages updated | Added Український (Ukrainian)
  • RVN asset layer support updated
  • Exchanges utilize proxy options
  • ETC default node updated to fix some connection issues

Assets Added

  • Ripple XRP added
  • AXE asset added
  • UNUS SED LEO Token added
  • Full node binaries updated for multiple assets

Bug Fixes

  • Fixed when sending ETH to own address, the address was saved to contacts
  • General news was not loading correctly in some cases
  • Binance DEX was showing incorrect error messages for certain conditions
  • Binance DEX asset change percentages were not showing correct values

Notes:

- If you have auto-update enabled in Settings, ZelCore Desktop will automatically update when the release is pushed

- ZelCore Mobile updates are handled by the App Store/Play Store

- After Zel pushes the release, the app stores have a review period that can take additional time before the update is available

— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — -

Written by Zel Technologies, GmbH — 07 June 2019 — Rev. 2

<https://zel.network>

--

--

Flux Official
Flux Official

Written by Flux Official

Blog source for all things Flux, officially; from the Flux Team | https://runonflux.io | https://twitter.com/runonflux

Responses (1)