Skip to content

Releases: givelotus/lotusd

v4.3.3

16 Nov 04:22
9560714
Compare
Choose a tag to compare
* Supports "Numbers" upgrade
* Updates to Bitcoin ABC 0.24.11
* Updates block rewardee addresses

v1.0.3

19 Oct 21:47
Compare
Choose a tag to compare
Includes changes from Bitcoin ABC versions 0.23.8, v0.23.9, v0.24.0
0.24.1, 0.24.2:

v0.23.8
 - Add a new option `-networkactive` to enable all P2P network activity
   (default 1). To start a node offline, you can provide
   `-networkactive=0` or `-nonetworkactive`.
 - The deprecated `setexcessiveblock` RPC has been removed and is no
   longer available. The `-excessiveblocksize` option should be used
   instead.

v0.23.9:
  - Improvements to the Avalanche experimental feature.
  - Test performance improvements.

v0.24.0
 - The `-ecash` setting is now **enabled by default**. To use the old
   BCHA default unit and bitcoincash: CashAddr prefix, use the
   `-ecash=0` option.

v0.24.1:

* CLI

A new `bitcoin-cli -generate` command, equivalent to RPC
`generatenewaddress` followed by `generatetoaddress`, can generate
blocks for command line testing purposes. This is a client-side version
of the former `generate` RPC. See the help for details.

* Low-level RPC Changes

- To make RPC `sendtoaddress` more consistent with `sendmany` the
    following error `sendtoaddress` codes were changed from `-4` to
    `-6`:
  - Insufficient funds
  - Transaction has too long of a mempool chain

- Exposed transaction version numbers are now treated as unsigned 32-bit
  integers instead of signed 32-bit integers. This matches their
  treatment in consensus logic. Versions greater than 2 continue to be
  non-standard (matching previous behavior of smaller than 1 or greater
  than 2 being non-standard). Note that this includes the joinpsbt
  command, which combines partially-signed transactions by selecting the
  highest version number.

* Notification changes

`-walletnotify` notifications are now sent for wallet transactions that
are removed from the mempool because they conflict with a new block.
These notifications were sent previously before the v0.21.13 release,
but had been broken since that release.