Up to [cvs.NetBSD.org] / pkgsrc / finance / bitcoin
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
bitcoin: updated to 30.0 30.0 https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-30.0.md
bitcoin: updated to 29.0 29.0 https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-29.0.md
bitcoin: updated to 28.1 Bitcoin Core 28.1 P2P When the -port configuration option is used, the default onion listening port will now be derived to be that port + 1 instead of being set to a fixed value (8334 on mainnet). This re-allows setups with multiple local nodes using different -port and not using -bind, which would lead to a startup failure in v28.0 due to a port collision. Note that a HiddenServicePort manually configured in torrc may need adjustment if used in connection with the -port option. For example, if you are using -port=5555 with a non-standard value and not using -bind=...=onion, previously Bitcoin Core would listen for incoming Tor connections on 127.0.0.1:8334. Now it would listen on 127.0.0.1:5556 (-port plus one). If you configured the hidden service manually in torrc now you have to change it from HiddenServicePort 8333 127.0.0.1:8334 to HiddenServicePort 8333 127.0.0.1:5556, or configure bitcoind with -bind=127.0.0.1:8334=onion to get the previous behavior. addrman: change internal id counting to int64_t Key key: clear out secret data in DecodeExtKey Build depends: For mingw cross compile use -gcc-posix to prevent library conflict depends: Fix CXXFLAGS on NetBSD Test test: add missing sync to feature_fee_estimation.py fuzz: add cstdlib to FuzzedDataProvider test: fix MIN macro redefinition rpc: Extend scope of validation mutex in generateblock Doc doc: add testnet4 section header for config file CI ci: add LLVM_SYMBOLIZER_PATH to Valgrind fuzz job Misc refactor: Drop deprecated space in operator""_mst util: use explicit cast in MultiIntBitSet::Fill()
bitcoin: fix the build with the "qt5" option
bitcoin: updated to 27.1 27.1 Miniscript * sign: don't assume we are parsing a sane TapMiniscript RPC * rpc, bugfix: Enforce maximum value for setmocktime * rpc: Reword SighashFromStr error message * rpc: move UniValue in blockToJSON Index * Fix set m_synced = true after Commit() Gui *gui812 Fix create unsigned transaction fee bump *gui813 Don't permit port in proxy IP option Test * test: Fix failing univalue float test P2P * p2p: detect addnode cjdns peers in GetAddedNodeInfo() Build * depends: fix mingw-w64 Qt DEBUG=1 build * build: Fix false positive CHECK_ATOMIC test * depends: Fix build of Qt for 32-bit platforms with recent glibc * crypto: disable asan for sha256_sse4 with clang and -O0 * depends: Fetch miniupnpc sources from an alternative website * build: Fix building fuzz binary on on SunOS / illumos * depends: Update Boost download link Doc * doc: add LLVM instruction for macOS < 13 CI * ci: Bump s390x to ubuntu:24.04 Misc * Change Luke Dashjr seed to dashjr-list-of-p2p-nodes.us * contrib: Renew Windows code signing certificate
bitcoin: updated to 27.0 27.0 https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-27.0.md
bitcoin: updated to 23.0 23.0 Notable changes P2P and network changes A bitcoind node will no longer rumour addresses to inbound peers by default. They will become eligible for address gossip after sending an ADDR, ADDRV2, or GETADDR message. Before this release, Bitcoin Core had a strong preference to try to connect only to peers that listen on port 8333. As a result of that, Bitcoin nodes listening on non-standard ports would likely not get any Bitcoin Core peers connecting to them. This preference has been removed. Full support has been added for the CJDNS network. See the new option -cjdnsreachable and doc/cjdns.md
finance/bitcoin: update to version 22.0
Notable changes:
- P2P and network changes
* Added support for running Bitcoin Core as an I2P (Invisible Internet
Project) service and connect to such services. See i2p.md for details.
* This release removes support for Tor version 2 hidden services in favor of
Tor v3 only, as the Tor network dropped support for Tor v2 with the release
of Tor version 0.4.6. Henceforth, Bitcoin Core ignores Tor v2 addresses; it
neither rumors them over the network to other peers, nor stores them in
memory or to peers.dat.
* Added NAT-PMP port mapping support via libnatpmp.
- New and Updated RPCs
* Due to BIP 350 being implemented, behavior for all RPCs that accept
addresses is changed when a native witness version 1 (or higher) is passed.
These now require a Bech32m encoding instead of a Bech32 one, and Bech32m
encoding will be used for such addresses in RPC output as well. No version 1
addresses should be created for mainnet until consensus rules are adopted
that give them meaning (as will happen through BIP 341). Once that happens,
Bech32m is expected to be used for them, so this shouldn't affect any
production systems, but may be observed on other networks where such addresses
already have meaning (like signet).
* The getpeerinfo RPC returns two new boolean fields, bip152_hb_to and
bip152_hb_from, that respectively indicate whether we selected a peer to be
in compact blocks high-bandwidth mode or whether a peer selected us as a
compact blocks high-bandwidth peer. High-bandwidth peers send new block
announcements via a cmpctblock message rather than the usual inv/headers
announcements. See BIP 152 for more details.
* getpeerinfo no longer returns the following fields: addnode, banscore, and
whitelisted, which were previously deprecated in 0.21. Instead of addnode,
the connection_type field returns manual. Instead of whitelisted, the
permissions field indicates if the peer has special privileges. The
banscore field has simply been removed.
* The following RPCs: gettxout, getrawtransaction, decoderawtransaction,
decodescript, gettransaction, and REST endpoints: /rest/tx, /rest/getutxos,
/rest/block deprecated the following fields (which are no longer returned in
the responses by default): addresses, reqSigs. The -deprecatedrpc=addresses
flag must be passed for these fields to be included in the RPC response.
This flag/option will be available only for this major release, after which
the deprecation will be removed entirely. Note that these fields are
attributes of the scriptPubKey object returned in the RPC response. However,
in the response of decodescript these fields are top-level attributes, and
included again as attributes of the scriptPubKey object.
* When creating a hex-encoded bitcoin transaction using the bitcoin-tx
utility with the -json option set, the following fields: addresses, reqSigs
are no longer returned in the tx output of the response.
* The listbanned RPC now returns two new numeric fields: ban_duration and
time_remaining. Respectively, these new fields indicate the duration of a
ban and the time remaining until a ban expires, both in seconds.
Additionally, the ban_created field is repositioned to come before
banned_until.
* The setban RPC can ban onion addresses again. This fixes a regression
introduced in version 0.21.0.
* The getnodeaddresses RPC now returns a "network" field indicating the
network type (ipv4, ipv6, onion, or i2p) for each address.
* getnodeaddresses now also accepts a "network" argument (ipv4, ipv6, onion,
or i2p) to return only addresses of the specified network.
* The testmempoolaccept RPC now accepts multiple transactions (still
experimental at the moment, API may be unstable). This is intended for
testing transaction packages with dependency relationships; it is not
recommended for batch-validating independent transactions. In addition to
mempool policy, package policies apply: the list cannot contain more than 25
transactions or have a total size exceeding 101K virtual bytes, and cannot
conflict with (spend the same inputs as) each other or the mempool, even if
it would be a valid BIP125 replace-by-fee. There are some known limitations
to the accuracy of the test accept: it's possible for testmempoolaccept to
return "allowed"=True for a group of transactions, but
"too-long-mempool-chain" if they are actually submitted.
* addmultisigaddress and createmultisig now support up to 20 keys for Segwit
addresses.
Then also the build system, files, new settings, updated settings, tools and
utilities, wallet, and GUI changes; the full list is at
https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-22.0.md.
bitcoin: updated to 0.21.0
0.21.0:
Notable changes
P2P and network changes
The mempool now tracks whether transactions submitted via the wallet or RPCs have been successfully broadcast. Every 10-15 minutes, the node will try to announce unbroadcast transactions until a peer requests it via a getdata message or the transaction is removed from the mempool for other reasons. The node will not track the broadcast status of transactions submitted to the node using P2P relay. This version reduces the initial broadcast guarantees for wallet transactions submitted via P2P to a node running the wallet.
The size of the set of transactions that peers have announced and we consider for requests has been reduced from 100000 to 5000 (per peer), and further announcements will be ignored when that limit is reached. If you need to dump (very) large batches of transactions, exceptions can be made for trusted peers using the "relay" network permission. For localhost for example it can be enabled using the command line option -whitelist=relay@127.0.0.1.
This release adds support for Tor version 3 hidden services, and rumoring them over the network to other peers using BIP155. Version 2 hidden services are still fully supported by Bitcoin Core, but the Tor network will start deprecating them in the coming months.
The Tor onion service that is automatically created by setting the -listenonion configuration parameter will now be created as a Tor v3 service instead of Tor v2. The private key that was used for Tor v2 (if any) will be left untouched in the onion_private_key file in the data directory (see -datadir) and can be removed if not needed. Bitcoin Core will no longer attempt to read it. The private key for the Tor v3 service will be saved in a file named onion_v3_private_key. To use the deprecated Tor v2 service (not recommended), the onion_private_key can be copied over onion_v3_private_key, e.g. cp -f onion_private_key onion_v3_private_key.
The client writes a file (anchors.dat) at shutdown with the network addresses of the node’s two outbound block-relay-only peers (so called "anchors"). The next time the node starts, it reads this file and attempts to reconnect to those same two peers. This prevents an attacker from using node restarts to trigger a complete change in peers, which would be something they could use as part of an eclipse attack.
This release adds support for serving BIP157 compact filters to peers on the network when enabled using -blockfilterindex=1 -peerblockfilters=1.
This release adds support for signets (BIP325) in addition to the existing mainnet, testnet, and regtest networks. Signets are centrally-controlled test networks, allowing them to be more predictable test environments than the older testnet. One public signet is maintained, and selectable using -signet. It is also possible to create personal signets.
This release implements BIP339 wtxid relay. When negotiated, transactions are announced using their wtxid instead of their txid.
This release implements the proposed Taproot consensus rules (BIP341 and BIP342), without activation on mainnet. Experimentation with Taproot can be done on signet, where its rules are already active.
Updated RPCs
The getpeerinfo RPC has a new network field that provides the type of network ("ipv4", "ipv6", or "onion") that the peer connected through.
The getpeerinfo RPC now has additional last_block and last_transaction fields that return the UNIX epoch time of the last block and the last valid transaction received from each peer.
getnetworkinfo now returns two new fields, connections_in and connections_out, that provide the number of inbound and outbound peer connections. These new fields are in addition to the existing connections field, which returns the total number of peer connections.
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.
getmempoolinfo now returns an additional unbroadcastcount field. The mempool tracks locally submitted transactions until their initial broadcast is acknowledged by a peer. This field returns the count of transactions waiting for acknowledgement.
Mempool RPCs such as getmempoolentry and getrawmempool with verbose=true now return an additional unbroadcast field. This indicates whether initial broadcast of the transaction has been acknowledged by a peer. getmempoolancestors and getmempooldescendants are also updated.
The getpeerinfo RPC no longer returns the banscore field unless the configuration option -deprecatedrpc=banscore is used. The banscore field will be fully removed in the next major release.
The testmempoolaccept RPC returns vsize and a fees object with the base fee if the transaction would pass validation.
The getpeerinfo RPC now returns a connection_type field. This indicates the type of connection established with the peer. It will return one of six options. For more information, see the getpeerinfo help documentation.
The getpeerinfo RPC no longer returns the addnode field by default. This field will be fully removed in the next major release. It can be accessed with the configuration option -deprecatedrpc=getpeerinfo_addnode. However, it is recommended to instead use the connection_type field (it will return manual when addnode is true).
The getpeerinfo RPC no longer returns the whitelisted field by default. This field will be fully removed in the next major release. It can be accessed with the configuration option -deprecatedrpc=getpeerinfo_whitelisted. However, it is recommended to instead use the permissions field to understand if specific privileges have been granted to the peer.
The walletcreatefundedpsbt RPC call will now fail with Insufficient funds when inputs are manually selected but are not enough to cover the outputs and fee. Additional inputs can automatically be added through the new add_inputs option.
The fundrawtransaction RPC now supports add_inputs option that when false prevents adding more inputs if necessary and consequently the RPC fails.
Changes to Wallet or GUI related RPCs can be found in the GUI or Wallet section below.
New RPCs
The getindexinfo RPC returns the actively running indices of the node, including their current sync status and height. It also accepts an index_name to specify returning the status of that index only.
Build System
Updated settings
The same ZeroMQ notification (e.g. -zmqpubhashtx=address) can now be specified multiple times to publish the same notification to different ZeroMQ sockets.
The -banscore configuration option, which modified the default threshold for disconnecting and discouraging misbehaving peers, has been removed as part of changes in 0.20.1 and in this release to the handling of misbehaving peers. Refer to "Changes regarding misbehaving peers" in the 0.20.1 release notes for details.
The -debug=db logging category, which was deprecated in 0.20 and replaced by -debug=walletdb to distinguish it from coindb, has been removed.
A download permission has been extracted from the noban permission. For compatibility, noban implies the download permission, but this may change in future releases. Refer to the help of the affected settings -whitebind and -whitelist for more details.
Netmasks that contain 1-bits after 0-bits (the 1-bits are not contiguous on the left side, e.g. 255.0.255.255) are no longer accepted. They are invalid according to RFC 4632. Netmasks are used in the -rpcallowip and -whitelist configuration options and in the setban RPC.
The -blocksonly setting now completely disables fee estimation.
Changes to Wallet or GUI related settings can be found in the GUI or Wallet section below.
Tools and Utilities
A new bitcoin-cli -netinfo command provides a network peer connections dashboard that displays data from the getpeerinfo and getnetworkinfo RPCs in a human-readable format. An optional integer argument from 0 to 4 may be passed to see increasing levels of detail.
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.
The bitcoin-cli -getinfo command now displays the wallet name and balance for each of the loaded wallets when more than one is loaded (e.g. in multiwallet mode) and a wallet is not specified with -rpcwallet.
The connections field of bitcoin-cli -getinfo is now expanded to return a JSON object with in, out and total numbers of peer connections. It previously returned a single integer value for the total number of peer connections.
New settings
The startupnotify option is used to specify a command to execute when Bitcoin Core has finished with its startup sequence.
Wallet
Backwards compatibility has been dropped for two getaddressinfo RPC deprecations, as notified in the 0.20 release notes. The deprecated label field has been removed as well as the deprecated labels behavior of returning a JSON object containing name and purpose key-value pairs. Since 0.20, the labels field returns a JSON array of label names.
To improve wallet privacy, the frequency of wallet rebroadcast attempts is reduced from approximately once every 15 minutes to once every 12-36 hours. To maintain a similar level of guarantee for initial broadcast of wallet transactions, the mempool tracks these transactions as a part of the newly introduced unbroadcast set. See the "P2P and network changes" section for more information on the unbroadcast set.
The sendtoaddress and sendmany RPCs accept an optional verbose=True argument to also return the fee reason about the sent tx.
The wallet can create a transaction without change even when the keypool is empty. Previously it failed.
The -salvagewallet startup option has been removed. A new salvage command has been added to the bitcoin-wallet tool which performs the salvage operations that -salvagewallet did.
A new configuration flag -maxapsfee has been added, which sets the max allowed avoid partial spends (APS) fee. It defaults to 0 (i.e. fee is the same with and without APS). Setting it to -1 will disable APS, unless -avoidpartialspends is set.
The wallet will now avoid partial spends (APS) by default, if this does not result in a difference in fees compared to the non-APS variant. The allowed fee threshold can be adjusted using the new -maxapsfee configuration option.
The createwallet, loadwallet, and unloadwallet RPCs now accept load_on_startup options to modify the settings list. Unless these options are explicitly set to true or false, the list is not modified, so the RPC methods remain backwards compatible.
A new send RPC with similar syntax to walletcreatefundedpsbt, including support for coin selection and a custom fee rate, is added. The send RPC is experimental and may change in subsequent releases.
The estimate_mode parameter is now case-insensitive in the bumpfee, fundrawtransaction, sendmany, sendtoaddress, send and walletcreatefundedpsbt RPCs.
The bumpfee RPC now uses conf_target rather than confTarget in the options.
fundrawtransaction and walletcreatefundedpsbt when used with the lockUnspents argument now lock manually selected coins, in addition to automatically selected coins. Note that locked coins are never used in automatic coin selection, but can still be manually selected.
The -zapwallettxes startup option has been removed and its functionality removed from the wallet. This option was originally intended to allow for rescuing wallets which were affected by a malleability attack. More recently, it has been used in the fee bumping of transactions that did not signal RBF. This functionality has been superseded with the abandon transaction feature.
The error code when no wallet is loaded, but a wallet RPC is called, has been changed from -32601 (method not found) to -18 (wallet not found).
bitcoin: updated to 0.18.1 0.18.1 P2P protocol and network code - Add tests and documentation for blocksonly - Avoid logging transaction decode errors to stderr - fix: tor: Call `event_base_loopbreak` from the event's callback - Make poll in InterruptibleRecv only filter for POLLIN events Wallet - Add -ignorepartialspends to list of ignored wallet options RPC and other APIs - Bugfix: fix pruneblockchain returned prune height - Document iswitness flag and fix bug in converttopsbt - Ensure that uncompressed public keys in a multisig always returns a legacy address - Disallow extended encoding for non-witness transactions - add 2nd arg to signrawtransactionwithkey examples - signrawtransactionwithkey: report error when missing redeemScript/witnessScript GUI - fix the bug of OPEN CONFIGURATION FILE on Mac - Show "No wallets available" in open menu instead of nothing - Enable open wallet menu on setWalletController - Set progressDialog to nullptr - Fix open wallet menu initialization order - Set `AA_EnableHighDpiScaling` attribute early - Enable console line edit on setClientModel - Assert QMetaObject::invokeMethod result Build system - Add test for GCC bug 90348 - Install bitcoin-wallet manpage - build with -fstack-reuse=none Tests and QA - Pure python EC - Add test for superfluous witness record in deserialization - Bugfix: test/functional/rpc_psbt: Remove check for specific error message that depends on uncertain assumptions - Add test that addmultisigaddress fails for watchonly addresses Documentation - Remove text about txes always relayed from -whitelist Miscellaneous - Catch by reference not value in wallettool - Replace fprintf with tfm::format
Import bitcoin 0.16.1 as finance/bitcoin Bitcoin is a decentralized P2P electronic cash system without a central server or trusted parties. Users hold the crypto keys to their own money and transact directly with each other, with the help of the network to check for double-spending.