0.29.8

Bitcoin ABC 0.29.8 Release Notes

Bitcoin ABC version 0.29.8 is now available from:

https://download.bitcoinabc.org/0.29.8/

This release includes the following features and fixes:

• Fix a potential OOM crash of bitcoin-qt when opening a BIP72 URI pointing to
  a very large file. The node will stop downloading the payment request if it
  exceeds the max size of 50kB.
• The testmempoolaccept RPC now returns 2 additional results within the
  fees result: effective-feerate is the feerate including fees and sizes of
  transactions validated together if package validation was used, and also
  includes any modified fees from prioritisetransaction. The
  effective-includes result lists the txids of transactions whose modified
  fees and sizes were used in the effective-feerate.
• Fix a data race that could prevent the staking reward winner from being
  added to the block template when the longpoll feature is used.

0.29.7

Bitcoin ABC 0.29.7 Release Notes

Bitcoin ABC version 0.29.7 is now available from:

https://download.bitcoinabc.org/0.29.7/

This release includes the following features and fixes:

• The -deprecatedrpc=getstakingreward option was under deprecation for
  several months and has been removed completely.
• The getstakingreward RPC now returns the proofid of the staking reward
  winner in addition to the payout script.
• A new setflakyproof RPC instructs the node to also accept an alternative
  staking reward winner when the flaky proof would have been selected. The list
  of these flaky proofs can be retrieved via the getflakyproofs RPC.

0.29.6

Bitcoin ABC 0.29.6 Release Notes

Bitcoin ABC version 0.29.6 is now available from:

https://download.bitcoinabc.org/0.29.6/

This release includes the following features and fixes:

JSON-RPC

All JSON-RPC methods accept a new named parameter called args that can
contain positional parameter values. This is a convenience to allow some
parameter values to be passed by name without having to name every value. The
python test framework and bitcoin-cli tool both take advantage of this, so
for example:

bitcoin-cli -named createwallet wallet_name=mywallet load_on_startup=1

Can now be shortened to:

bitcoin-cli -named createwallet mywallet load_on_startup=1

For RPC methods which accept options parameters (importmulti, listunspent, fundrawtransaction, send, walletcreatefundedpsbt), it is now possible to pass the options as named parameters without the need for a nested object.

This means it is possible make calls like:

src/bitcoin-cli -named fundrawtransaction <raw tx hex> txid fee_rate=100

instead of

src/bitcoin-cli -named fundrawtransaction <raw tx hex> options='{"fee_rate": 100}'

The JSON-RPC server now rejects requests where a parameter is specified
multiple times with the same name, instead of silently overwriting earlier
parameter values with later ones.

0.29.5

Bitcoin ABC 0.29.5 Release Notes

Bitcoin ABC version 0.29.5 is now available from:

https://download.bitcoinabc.org/0.29.5/

This is a maintenance release with no user-visible change.

0.29.4

Bitcoin ABC 0.29.4 Release Notes

Bitcoin ABC version 0.29.4 is now available from:

https://download.bitcoinabc.org/0.29.4/

This release includes the following features and fixes:

• Add a new checkpoint after the May 15th, 2024 eCash network upgrade

0.29.3

Bitcoin ABC 0.29.3 Release Notes

Bitcoin ABC version 0.29.3 is now available from:

https://download.bitcoinabc.org/0.29.3/

Chronik LOKAD ID index

To allow users to build applications on top of eCash, the LOKAD ID index has been added.

This is enabled by default, and after restarting, it takes a few hours to sync the index. If you don't need it, you should disable it with -chroniklokadidindex=0.

The LOKAD ID spec has been around for a while, and has been used in a few prominent protocols, such as SLP.

However, usage hasn't been too high, which is probably because the indexing infrastructure simply wasn't as good as it could be.

Chronik's new LOKAD ID index finds all txs that follow the spec, and also extends it by allowing LOKAD ID prefixes in eMPP pushdata to be detected, as well as LOKAD ID push op prefixes in scriptSigs. The latter is especially useful for apps building on top of SLP, which can't handle additional protocols in the OP_RETURN.

There are endpoints for /lokad-id/<lokad id hex>/{confirmed-txs,unconfirmed-txs,history}, as well as listening to WebSocket updates on LOKAD IDs. A UTXOs endpoint is not available as LOKAD IDs are per-tx, not per-output.

0.29.2

Bitcoin ABC 0.29.2 Release Notes

Bitcoin ABC version 0.29.2 is now available from:

https://download.bitcoinabc.org/0.29.2/

This release includes the following features and fixes:

• The sharing field from the getavalancheinfo RPC was deprecated since
  v0.28.0 and has now been removed.

0.29.1

Bitcoin ABC 0.29.1 Release Notes

Bitcoin ABC version 0.29.1 is now available from:

https://download.bitcoinabc.org/0.29.1/

This is a hotfix release to fix a bug that could cause the node to connect
to the same peer twice. Only v0.29.0 is affected by the bug.

0.29.0

Bitcoin ABC 0.29.0 Release Notes

Bitcoin ABC version 0.29.0 is now available from:

https://download.bitcoinabc.org/0.29.0/

Chronik

The Chronik indexer is now available as an opt-in option to the Bitcoin ABC
node software for Linux and Windows. Chronik gives you access to a brand new API
to get notified of finalized blocks, retrieve transaction history by eCash
address, gather eToken transaction data, and much more. To enable Chronik,
simply turn it on with the -chronik option.

Take a look at the full setup and API documentation
to get an overview of the features, and start building your own application with
the chronik-client npm package.

Network upgrade

At the MTP time of 1715774400 (May 15, 2024 12:00:00 UTC), the following
changes will become activated:

• Bump automatic replay protection to the next upgrade, timestamp 1731672000
  (November 15, 2024 12:00:00 UTC).

0.28.12

Bitcoin ABC 0.28.12 Release Notes

Bitcoin ABC version 0.28.12 is now available from:

https://download.bitcoinabc.org/0.28.12/

This release includes the following features and fixes:

• It is possible to manually set several staking reward winners via the
  setstakingreward RPC by setting the optional append flag. The
  getstakingreward RPC now returns an array to reflect this change. The old
  behavior remains available via the -deprecatedrpc=getsatkingreward option.
  This change of behavior only affects the node's avalanche vote and has no
  effect on mining.