Skip to content

Releases: CounterpartyXCP/counterparty-core

9.54.0

05 Mar 23:13
Compare
Choose a tag to compare

Description

This a hotfix in broadcast transaction. Fee fraction can't be greater than 1, otherwise the total amount escrowed for the bet is lower than the requested fee and cause a CreditError('Negative quantity.'). Also now invalid broadcasts don't trigger bet matching.

Mandatory Upgrade Block

  • All clients must upgrade immediately.

Protocol Changes

  • Max fee fraction of 1

Implementation Changes

  • NONE

Interface Changes

  • NONE

Upgrade Procedure

  • NONE

9.53.0

24 Jan 22:14
Compare
Choose a tag to compare

Description

This is an incremental upgrade with numerous bug fixes and performance enhancements, that adds support for 80-byte OP_RETURN.

Mandatory Upgrade Block

  • NONE

Protocol Changes

  • NONE

Interface Changes

  • Add min_message_index to get_blocks API call.
  • Add skip_missing parameter to getrawtransaction and getrawtransaction_batch API calls.

Upgrade Procedure

  • Update as normal. Note that, due to the undolog feature no longer tracking the messages table, a reparse will be required (counterparty-lib will automatically perform this upon restarting).

9.52.0

04 Nov 23:42
Compare
Choose a tag to compare

Description

This is an incremental upgrade with bug fixes and an "undolog" enhancement to allow almost instant reorg processing.

Mandatory Upgrade Block

  • NONE

Protocol Changes

  • NONE

Interface Changes

  • getrawtransaction added to API
  • getrawtransaction_batch added to API

Upgrade Procedure

  • Update as normal. Note that, due to the addition of the undolog feature, a reparse will be required (counterparty-lib will automatically perform this upon restarting).

counterparty-lib v9.51.4

26 Sep 15:23
v9.51.4
f236a12
Compare
Choose a tag to compare

Description

This is an incremental upgrade with bug fixes and major performance enhancements. It also adds a feature for 'transaction chaining'.

Mandatory Upgrade Block

  • NONE

Protocol Changes

  • NONE

Interface Changes

  • NONE

Upgrade Procedure

  • NONE

counterparty-lib v9.51.3

13 May 13:28
Compare
Choose a tag to compare

Description

This is an incremental upgrade with primarily bug fixes.

Mandatory Upgrade Block

  • NONE

Protocol Changes

  • NONE

Interface Changes

  • NONE

Upgrade Procedure

  • NONE

counterparty-lib v9.51.2

23 Apr 21:36
Compare
Choose a tag to compare

Description

This is an incremental upgrade with primarily bug fixes and performance optimizations.

Mandatory Upgrade Block

  • NONE

Protocol Changes

  • NONE

Interface Changes

  • Renamed repository to counterparty-lib

Upgrade Procedure

  • NONE

counterparty-lib v9.51.1

20 Apr 15:01
v9.51.1
Compare
Choose a tag to compare

Description

This is an incremental upgrade with primarily bug fixes and performance optimizations.

Mandatory Upgrade Block

  • NONE

Protocol Changes

  • NONE

Interface Changes

  • Rename server.api.log to server.access.log
  • Add requests_timeout parameter

Upgrade Procedure

  • NONE

counterparty-lib v9.51.0

01 Apr 14:04
v9.51.0
c54c38d
Compare
Choose a tag to compare

Description

This is an incremental upgrade with a few minor protocol changes. The most significant change is the addition of the HTTP REST API, which should make interacting with the Counterparty reference client much easier for developers.

Mandatory Upgrade Block

  • All clients must be upgraded by block 352000.

Protocol Changes

  • Check for null data chunks.
  • Disable rock‐paper‐scissors.
  • Catch unhandled exception with invalid script on testnet

Implementation Changes

  • Default to using opreturn encoding when possible

Interface Changes

  • Deprecate get_asset_info(assets) API method.
  • Deprecate get_xcp_supply() API method in favor of get_supply(asset).
  • Changed get_unspent_txouts API method parameter and return values.
  • Added HTTP Rest API.
  • Authentication on JSON‐RPC API is off by default
  • rpc_password configuration parameter is no longer mandatory

Upgrade Procedure

  • Upgrade counterparty-cli to v1.1.0 (recommended)
  • Transition away from deprecated API method calls.
  • Disable API authentication if it's unnecessary.

counterparty-lib v9.50.0

18 Mar 12:45
v9.50.0
Compare
Choose a tag to compare

Description

This a hotfix for a fatal integer overflow error that affected all clients parsing mainnet block 348076. There was insufficient sanity checking for invalid send transactions, and the problem would have been avoided if the parsing of invalid send transactions returned earlier. Indeed, there is already a complete re-implementation of send transactions currently in testing here: https://github.com/CounterpartyXCP/counterpartyd/blob/master/counterpartylib/lib/messages/versions/send2.py

Mandatory Upgrade Block

  • All clients must upgrade immediately.

Protocol Changes

  • NONE

Implementation Changes

  • NONE

Interface Changes

  • NONE

Upgrade Procedure

  • NONE

counterparty-lib v9.49.4

05 Feb 23:24
Compare
Choose a tag to compare

Description

This was a major upgrade, though non-mandatory, because it involved a complete re-architecting of the project---this package is now a 'pure' Pyton library and a PyPi package, with no wallet functionality or command-line interface. Installation of counterparty-lib is now as simple as running $ pip3 install counterparty-lib; installation of the CLI is as simple as running $ pip3 install counterparty-cli.

Migration from earlier versions may well be accompanied by some hiccups---we've tried to make the upgrade path as smooth as possible, but there are definitely edge cases we haven't been able to test. However, because this new version includes no changes to the core protocol, upgrades may proceed at a relatively leisurely pace.

Mandatory Upgrade Block

  • None

Protocol Changes

  • None

Implementation Changes

  • Re-architected this package as a library
  • Moved CLI to new repository: counterparty-cli
  • Remove all signing and broadcast functionality
  • Created setup.py build script
  • Return to using requests for handling connections to backend
  • Introduced global variable CURRENT_BLOCK_INDEX
  • Prepared version check for repository rename to counterparty-lib
  • Improved test coverage
  • Misc. bug fixes
  • Removed option of using Insight, Blockr and SoChain as a backend
  • Added option of using btcd as a backend
  • Moved API docs elsewhere

Interface Changes

  • Renamed configuration parameters: jmcorgan -> addrindex, BACKEND_RPC_* -> BACKEND_*, BLOCKCHAIN_SERVICE_NAME -> BACKEND_NAME.
  • counterpartyd.py server has been changed to counterparty-server start (CLI)
  • Paths to all configuration files, database files and log files changed. Their default locations are displayed when counterparty-server is run with --verbose.
  • Removed signing and broadcast functionality from API (do_*, sign_tx, broadcast_tx calls). The API documentation contains a guide to wallet integration.

Upgrade Procedure

  • The migration of the configuration files and database files to their new paths is handled automatically by the setup script: python3 setup.py install.
  • The names of some configuration parameters have changed---see above.
  • If you were using Insight, SoChain or Blockr for block explorer functionality, you must now switch to using a Patched Bitcoin Core or btcd as the backend.