chain-core-server-1.2.5

Bug fix release: When UTXO reservation didn’t find enough funds, it erroneously counted recently spent UTXOs, turning permanent “insufficient funds” errors into transient “outputs reserved” errors.

Chain Core 1.2.0-rc1

This is a prerelease

Node SDK 1.1.1

• Resolved an issue where transaction feeds would halt processing unexpectedly.

Node SDK 1.0.3

• Resolved an issue where transaction feeds would halt processing unexpectedly.

Chain Core 1.1.4

• Resolved issue that could cause some annotated transaction fields to be missing under high load.
• Expand Dashboard support to Safari 8 on OS X Yosemite systems.

Java SDK 1.1.3

High availability improvements

The client keeps a list of core URLs which it uses to load balance requests to a multi-process server. It will continue to make requests to a particular URL in the list until an error occurs (at which point it should update this position to the next URL in the list). A bug has been fixed which allowed separate requests to read the same position and update it separately.

The request retry logic has also been updated to cover the maximum, potential leader election period for a multi-process server.

Chain Core 1.1.3

• The network version has been updated to 3. Chain Core instances on the same network must share the same network version. If you're upgrading to version 1.1.3, make sure to upgrade all Chain Cores in your blockchain network. This version change is due to (#648), which was resolved in version 1.1.1.
• Resolved issue where some transaction inputs were not correctly annotated with account information (#668).
• Dashboard cosmetic changes.

Java SDK 1.1.1

Trusted SSL certs

You can now specify trusted server SSL certificates via a PEM-encoded file:

Client client = new Client.Builder()
  .setURL("https://example:443")
  .setTrustedCerts("path/to/certs.pem")
  .build();

Request logging

To log requests, pass an OutputStream to the client builder:

OutputStream os = System.out;
Client client = new Client.Builder()
  .setLogger(os)
  .setLogLevel(LoggingInterceptor.Level.ALL)
  .build();

Ruby SDK 1.1.1

• Relax minimum Ruby version requirement from 2.1 to 2.0. While the Ruby SDK is now compatible with Ruby 2.0, we strongly recommend using Ruby 2.1 or greater, since Ruby 2.0 has reached end-of-life and is no longer receiving critical security updates.

Ruby SDK 1.0.3

• Relax minimum Ruby version requirement from 2.1 to 2.0. While the Ruby SDK is now compatible with Ruby 2.0, we strongly recommend using Ruby 2.1 or greater, since Ruby 2.0 has reached end-of-life and is no longer receiving critical security updates.