Onyx

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.

This is a prerelease

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

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

• 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.

• 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.

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.

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();

• 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.

• 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.

• Updated to Chain Core 1.1.0

• Updated to Chain Core 1.1.0

This release is a minor version update, and contains new features, deprecations, and protocol breaking changes. cored 1.1.0 is backward-compatible with 1.0.x SDKs, but we strongly recommend upgrading to 1.1.x SDKs as soon as possible. cored 1.1.0 is not backward-compatible with 1.0.X coreds due to fundamental protocol changes.

Notable changes:

• The network version has been updated to 2. Chain Core instances on the same network must share the same network version. If you're upgrading to version 1.1.0, make sure to upgrade all Chain Cores in your blockchain network.
• Transaction outputs now have a unique id property.
• Transaction inputs refer to previous outputs using a new spent_output_id property. The existing spent_output property, which contains a transaction ID and position, is deprecated.
• Accounts now use receivers, a cross-core payment primitive that supersedes the Chain 1.0.x pattern of creating and paying to control programs. See the SDK changelogs for usage examples.
• The Dashboard has an improved on-boarding experience which guides new users through the basics.
• Block signing has been improved to better support HSM integration.
• Disable MockHSM and blockchain reset functions in production mode.
• Improve version string printing in cored and corectl commands.
• Bug fixes and performance improvements.

This release is a minor version update, and contains new features and deprecations. It is not compatible with cored 1.0.x; please upgrade cored before updating your SDKs.

• The createControlProgram method is deprecated. Instead, use createReceiver.
• The controlWithProgram transaction builder method is deprecated. Use controlWithReceiver instead.
• Transaction output objects and unspent outputs now have an id property, which is unique for that output across the history of the blockchain.
• The spentOutput property on transaction inputs is deprecated. Use spentOutputId instead.
• The spendUnspentOutput method now takes an outputId parameter. The transactionId and position parameters are deprecated.

This release is a minor version update, and contains new features and deprecations. It is not compatible with cored 1.0.x; please upgrade cored before updating your SDKs.

• The create_control_program method is deprecated. Instead, use create_receiver.
• The control_with_program transaction builder method is deprecated. Use control_with_receiver instead.
• Transaction output objects and unspent outputs now have an id property, which is unique for that output across the history of the blockchain.
• The spent_output property on Chain::Transaction::Input is deprecated. Use spent_output_id instead.
• The spend_account_unspent_output transaction builder method now accepts an output_id parameter. The transaction_id and position parameters are deprecated.

This release is a minor version update, and contains new features and deprecations. It is not compatible with cored 1.0.x; please upgrade cored before updating your SDKs.

Notable changes:

• Creating control programs via the ControlProgram.Builder class is deprecated. Instead, use Account.ReceiverBuilder.
• Transaction.Action.ControlWithProgram is deprecated. Use Transaction.Action.ControlWithReceiver instead.
• Transaction output objects and unspent outputs now have an id property, which is unique for that output across the history of the blockchain.
• The spentOutput property on Transaction.Input is deprecated. Use spentOutputId instead.
• Transaction.Action.SpendAccountUnspentOutput now has a setOutputId method. The setTransactionId and setPosition methods are deprecated.

• Updated to Chain Core 1.1.0

• Resolved issue running Chain Core on non-English systems

• Syntax compatibility update

• Use base URL and client token provided on initialization for MockHSM connection
• Allow users to instantiate Connection objects with new chain.Connection()