Ethereum Classic -v0.9.1pre

Ethereum Classic Wallet which downloads latest stable Geth release.

598711eacb76ab4a5e48e32523017c296d3ad339c0cb1c4038ade176d095ca89  Ethereum-Classic-Wallet-macosx-0-9-1.dmg
43b2da0e1c87957c4a9dbf49a7d1494518e993fce96b962c76b1ff23f4bbb590  Ethereum-Classic-Wallet-win64-0-9-1.exe


Source code (tar.gz)
Source code (zip)

DashPay Dash Wallet-v0.12.1.4

Dash Core Release Announcement

We are happy to announce the release of This release includes binaries, which can be downloaded below.

About this Release

Dash Core is a maintenance release of the Dash Core 0.12.1.x series

In this minor release only bugfixes have been included and we consider this a stable release.

Changelog changelog

- fix docs (#1404)
- fix unsafe vNodes access (#1403)
- Fix mn list sync (#1401)
- Translations201703 (#1384)
- [depends] Fixing download path and sha256 hash (#1398)
- bump libevent to 2.1.8 (stable) (#1397)
- Fix alerts (#1326)
- Disable salvagewallet in GUI (#1390)
- replace legacy dnsseed (#1395)
- Drop support for pre-12.1 nodes (#1394)
- Overhaul of coin selection for mixing (#1364)
- Node eviction fix (#1392)
- implement importelectrumwallet (#1377)
- [UI] Typo fixed (#1391)
- Locking fix for UpdatePreferredDownload (#1389)
- Fix deadlocks on cs_vSend in RequestGovernanceObject (#1387)
- Periodicially request orphan objects (#1383)
- Implemented utility functions for copying/releasing vNodes vector (#1382)

Thanks to 
@UdjinM6, @tgflynn, @crowning-, @schinzelh

[Source code (tar.gz)](
[Source code (zip)](


  • Breaks Safari on purpose out of an abundance of caution. We already take special steps to provide support for Safari, but may remove support in the next update. I’m not comfortable with…anything anymore. We test on Chrome/FF. You should use Chrome/FF?

  • Prep for redesign of flow for generate page tomorrow. Tonight, we sleep. ##Downloads
    Source code (tar.gz)
    Source code (zip)

ByteBall Wallet -v1.6.0

  • Now you can bind payments to events posted by oracles, which enables Bytes-vs-BTC exchange among other things. See
  • Back button in Android now works correctly
  • Chinese translation (partial)
  • List of balances by addresses in settings
  • After receiving a "message encrypted to unknown key" the undecipherable message is now deleted and the error does not pop up the next time
  • Performance improvements

The first time you start the app after the upgrade, it may be slow to start as it creates new indexes for better performance.##Downloads
Source code (tar.gz)
Source code (zip)


rippled 0.60.0 release includes Escrow, (previously called SusPay), which introduces a new ledger node type and several new transaction types to the Ripple network. Escrow permits users to cryptographically escrow XRP on RCL with an expiration date using a crypto-condition called preimage-sha-256, commonly referred to as a hashlock. An XRP Escrow transaction on RCL can be used together with Interledger, to allow a payment to be routed without having to trust third-party intermediaries. We believe this will open a range of possibilities and use cases for XRP, particularly when sending high value, low volume payments cross-border.

Payment Channels
The amendment for Payment Channels was originally introduced in version 0.33.0, but is now ready for Payment Channels to be enabled on the production Ripple Consensus Ledger. XRP Payment Channels are intended for high volume, low value payments. They provide a method for scalable, intermittent, off-ledger settlement flowing in a single direction. For bidirectional payment channels, an XRP Payment Channel can be used in each direction. The recipient can claim any unpaid balance at any time before the channel closes. The owner can top off the channel as needed and must wait out a delay to close the channel to give the recipient a chance to supply any claims. The total amount paid increases monotonically as newer claims are issued.

Dynamic UNL Lite
At the core of RCL is the consensus process. Through the consensus process, validating nodes agree on a specific subset of the candidate transactions to be considered for the next ledger. Consensus is an iterative process in which nodes relay proposals, or sets of candidate transactions. Nodes communicate and update proposals until a supermajority of peers agree on the same set of candidate transactions.

During consensus, each node evaluates proposals from a specific set of peers, called chosen validators. Chosen validators represent a subset of the network which, when taken collectively, is “trusted” not to collude in an attempt to defraud the node evaluating the proposals. This definition of “trust” does not require that each individual chosen validator is trusted. Rather, validators are chosen based on the expectation they will not collude in a coordinated effort to falsify data relayed to the network.

The rippled 0.60.0 release introduces new Dynamic UNL configuration options, which allow rippled to update its set of trusted validators without reconfiguring and restarting. Instead of specifying a static list of trusted validators in the config or validators file, you can configure a trusted publisher key and a URI where the publisher serves signed lists of validators. rippled will regularly query the configured URIs for the latest recommended list of validators from the trusted publishers. Configuring the validation quorum is no longer required, as rippled will automatically update its quorum based on its current trusted validator set.

Dynamic UNL Lite is a progressive step towards fully automated dynamic UNLs, to which each client of the Ripple network determines its UNL through policies, rather than trusting a pre-provided list of validators.

fix1368 Amendment
rippled 0.60.0 also introduces the fix1368 Amendment to fix a minor bug in transaction processing that causes some payments to fail when they should be valid. Specifically, during payment processing, some payment steps that are expected to produce a certain amount of currency may produce a microscopically different amount, due to a loss of precision related to floating-point number representation. When this occurs, those payments fail because they cannot deliver the exact amount intended. The fix1368 amendment corrects transaction processing so payments can no longer fail in this manner.
These features underline Ripple’s continued support to improving RCL by making it more stable, distributed and scalable for settlement of global payments.

Upcoming Features

We do not have an update on the previously announced changes to the hash tree structure that rippled uses to represent a ledger, called SHAMapV2. At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).

You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.

0.60.0 Change Log

  • Add Escrow support (#2039)](
  • Dynamize trusted validator list and quorum (#1842)
  • Simplify fee handling during transaction submission (#1992)
  • Publish server stream when fee changes (#2016)
  • Replace manifest with validator token (#1975)
  • Add validator key revocations (#2019)
  • Add SecretKey comparison operator (#2004)
  • Reduce LEDGER_MIN_CONSENSUS (#2013)
  • Update libsecp256k1 and Beast B30 (#1983)
  • Make Config extensible via lambda (#1993)
  • WebSocket permessage-deflate integration (#1995)
  • Do not close socket on a foreign thread (#2014)
  • Update build scripts to support latest boost and ubuntu distros (#1997)
  • Handle protoc targets in scons ninja build (#2022)
  • Specify syntax version for ripple.proto file (#2007)
  • Eliminate protocol header dependency (#1962)
  • Use gnu gold or clang lld linkers if available (#2031)
  • Add tests for lookupLedger (#1989)
  • Add unit test for get_counts RPC method (#2011)
  • Add test for transaction_entry request (#2017)
  • Unit tests of RPC sign (#2010)
  • Add failure only unit test reporter (#2018)

    Bug Fixes

  • Enforce rippling constraints during payments (#2049)
  • Fix limiting step re-execute bug (#1936)
  • Make wss work the same as wss2 (#2033)
  • Check for malformed public key on payment channel (#2027)
  • Config test uses unique directories for each test (#1984)
  • Send a websocket ping before timing out in server (#2035)


    Source code (tar.gz)
    Source code (zip)

WavesPlatform Wallet-v0.6.1

Testnet v0.6.1

WARNING Please, remove your existing Testnet blockchain.