Michael Ford [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2022-12-13 to 2023-05-26
💬 Posted a total of 4 messages
📚 Participated in the following categories: bitcoin-dev
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-07 23:22:03

- reply

📅 Original date posted:2023-05-26
🗒️ Summary of this message: Bitcoin Core version v25.0 is now available, featuring new features, bug fixes, and performance improvements, including allowing transactions of non-witness size 65 bytes and above.
📝 Original message:Bitcoin Core version v25.0 is now available from:
https://bitcoincore.org/bin/bitcoin-core-25.0/
Or through BitTorrent:
magnet:?xt=urn:btih:092358777175c4306602f9b1b523738df4b4610b&dn=bitcoin-core-25.0&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969%2Fannounce&tr=udp%3A%2F%2Fexplodie.org%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.torrent.eu.org%3A451%2Fannounce&tr=udp%3A%2F%2Ftracker.bitcoin.sprovoost.nl%3A6969&ws=http%3A%2F%2Fbitcoincore.org%2Fbin%2F
This release includes new features, various bug fixes and performance
improvements, as well as updated translations.
Please report bugs using the issue tracker at GitHub:
<https://github.com/bitcoin/bitcoin/issues>
To receive security and update notifications, please subscribe to:
<https://bitcoincore.org/en/list/announcements/join/>
How to Upgrade
==============
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes in some cases), then run the
installer (on Windows) or just copy over `/Applications/Bitcoin-Qt` (on macOS)
or `bitcoind`/`bitcoin-qt` (on Linux).
Upgrading directly from a version of Bitcoin Core that has reached its EOL is
possible, but it might take some time if the data directory needs to
be migrated. Old
wallet versions of Bitcoin Core are generally supported.
Compatibility
==============
Bitcoin Core is supported and extensively tested on operating systems
using the Linux kernel, macOS 10.15+, and Windows 7 and newer. Bitcoin
Core should also work on most other Unix-like systems but is not as
frequently tested on them. It is not recommended to use Bitcoin Core on
unsupported systems.
Notable changes
===============
P2P and network changes
-----------------------
- Transactions of non-witness size 65 bytes and above are now allowed by mempool
and relay policy. This is to better reflect the actual afforded protections
against CVE-2017-12842 and open up additional use-cases of smaller
transaction sizes. (#26265)
New RPCs
--------
- The scanblocks RPC returns the relevant blockhashes from a set of
descriptors by
scanning all blockfilters in the given range. It can be used in
combination with
the getblockheader and rescanblockchain RPCs to achieve fast wallet
rescans. Note
that this functionality can only be used if a compact block filter index
(-blockfilterindex=1) has been constructed by the node. (#23549)
Updated RPCs
------------
- All JSON-RPC methods accept a new [named
parameter](https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md#parameter-passing)
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:
```sh
bitcoin-cli -named createwallet wallet_name=mywallet load_on_startup=1
```
Can now be shortened to:
```sh
bitcoin-cli -named createwallet mywallet load_on_startup=1
```
- The `verifychain` RPC will now return `false` if the checks didn't fail,
but couldn't be completed at the desired depth and level. This could be due
to missing data while pruning, due to an insufficient dbcache or due to
the node being shutdown before the call could finish. (#25574)
- `sendrawtransaction` has a new, optional argument, `maxburnamount`
with a default value of `0`.
Any transaction containing an unspendable output with a value
greater than `maxburnamount` will
not be submitted. At present, the outputs deemed unspendable are
those with scripts that begin
with an `OP_RETURN` code (known as 'datacarriers'), scripts that
exceed the maximum script size,
and scripts that contain invalid opcodes.
- 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 wtxids of transactions whose
modified fees and sizes were used
in the effective-feerate (#26646).
- `decodescript` may now infer a Miniscript descriptor under P2WSH
context if it is not lacking
information. (#27037)
- `finalizepsbt` is now able to finalize a transaction with inputs
spending Miniscript-compatible
P2WSH scripts. (#24149)
Changes to wallet related RPCs can be found in the Wallet section below.
Build System
------------
- The `--enable-upnp-default` and `--enable-natpmp-default` options
have been removed. If you want to use port mapping, you can
configure it using a .conf file, or by passing the relevant
options at runtime. (#26896)
Updated settings
----------------
- If the `-checkblocks` or `-checklevel` options are explicitly provided by the
user, but the verification checks cannot be completed due to an insufficient
dbcache, Bitcoin Core will now return an error at startup. (#25574)
- Ports specified in `-port` and `-rpcport` options are now validated
at startup.
Values that previously worked and were considered valid can now
result in errors. (#22087)
- Setting `-blocksonly` will now reduce the maximum mempool memory
to 5MB (users may still use `-maxmempool` to override). Previously,
the default 300MB would be used, leading to unexpected memory usage
for users running with `-blocksonly` expecting it to eliminate
mempool memory usage.
As unused mempool memory is shared with dbcache, this also reduces
the dbcache size for users running with `-blocksonly`, potentially
impacting performance.
- Setting `-maxconnections=0` will now disable `-dnsseed`
and `-listen` (users may still set them to override).
Changes to GUI or wallet related settings can be found in the GUI or
Wallet section below.
New settings
------------
- The `shutdownnotify` option is used to specify a command to execute
synchronously
before Bitcoin Core has begun its shutdown sequence. (#23395)
Wallet
------
- The `minconf` option, which allows a user to specify the minimum number
of confirmations a UTXO being spent has, and the `maxconf` option,
which allows specifying the maximum number of confirmations, have been
added to the following RPCs in #25375:
- `fundrawtransaction`
- `send`
- `walletcreatefundedpsbt`
- `sendall`
- Added a new `next_index` field in the response in `listdescriptors` to
have the same format as `importdescriptors` (#26194)
- RPC `listunspent` now has a new argument `include_immature_coinbase`
to include coinbase UTXOs that don't meet the minimum spendability
depth requirement (which before were silently skipped). (#25730)
- Rescans for descriptor wallets are now significantly faster if compact
block filters (BIP158) are available. Since those are not constructed
by default, the configuration option "-blockfilterindex=1" has to be
provided to take advantage of the optimization. This improves the
performance of the RPC calls `rescanblockchain`, `importdescriptors`
and `restorewallet`. (#25957)
- RPC `unloadwallet` now fails if a rescan is in progress. (#26618)
- Wallet passphrases may now contain null characters.
Prior to this change, only characters up to the first
null character were recognized and accepted. (#27068)
- Address Purposes strings are now restricted to the currently known
values of "send",
"receive", and "refund". Wallets that have unrecognized purpose
strings will have
loading warnings, and the `listlabels` RPC will raise an error if an
unrecognized purpose
is requested. (#27217)
- In the `createwallet`, `loadwallet`, `unloadwallet`, and
`restorewallet` RPCs, the
"warning" string field is deprecated in favor of a "warnings" field that
returns a JSON array of strings to better handle multiple warning messages and
for consistency with other wallet RPCs. The "warning" field will be fully
removed from these RPCs in v26. It can be temporarily re-enabled during the
deprecation period by launching bitcoind with the configuration option
`-deprecatedrpc=walletwarningfield`. (#27279)
- Descriptor wallets can now spend coins sent to P2WSH Miniscript
descriptors. (#24149)
GUI changes
-----------
- The "Mask values" is a persistent option now. (gui#701)
- The "Mask values" option affects the "Transaction" view now, in
addition to the
"Overview" one. (gui#708)
REST
----
- A new `/rest/deploymentinfo` endpoint has been added for fetching various
state info regarding deployments of consensus changes. (#25412)
Binary verification
----
- The binary verification script has been updated. In previous releases it
would verify that the binaries had been signed with a single "release key".
In this release and moving forward it will verify that the binaries are
signed by a _threshold of trusted keys_. For more details and
examples, see:
https://github.com/bitcoin/bitcoin/blob/master/contrib/verify-binaries/README.md
(#27358)
Low-level changes
=================
RPC
---
- 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. (#26628)
- RPC `listsinceblock` now accepts an optional `label` argument
to fetch incoming transactions having the specified label. (#25934)
- Previously `setban`, `addpeeraddress`, `walletcreatefundedpsbt`, methods
allowed non-boolean and non-null values to be passed as boolean parameters.
Any string, number, array, or object value that was passed would be treated
as false. After this change, passing any value except `true`, `false`, or
`null` now triggers a JSON value is not of expected type error. (#26213)
Credits
=======
Thanks to everyone who directly contributed to this release:
- 0xb10c
- 721217.xyz
- @RandyMcMillan
- amadeuszpawlik
- Amiti Uttarwar
- Andrew Chow
- Andrew Toth
- Anthony Towns
- Antoine Poinsot
- Aurèle Oulès
- Ben Woosley
- Bitcoin Hodler
- brunoerg
- Bushstar
- Carl Dong
- Chris Geihsler
- Cory Fields
- David Gumberg
- dergoegge
- Dhruv Mehta
- Dimitris Tsapakidis
- dougEfish
- Douglas Chimento
- ekzyis
- Elichai Turkel
- Ethan Heilman
- Fabian Jahr
- FractalEncrypt
- furszy
- Gleb Naumenko
- glozow
- Greg Sanders
- Hennadii Stepanov
- hernanmarino
- ishaanam
- ismaelsadeeq
- James O'Beirne
- jdjkelly at gmail.com
- Jeff Ruane
- Jeffrey Czyz
- Jeremy Rubin
- Jesse Barton
- João Barbosa
- JoaoAJMatos
- John Moffett
- Jon Atack
- Jonas Schnelli
- jonatack
- Joshua Kelly
- josibake
- Juan Pablo Civile
- kdmukai
- klementtan
- Kolby ML
- kouloumos
- Kristaps Kaupe
- laanwj
- Larry Ruane
- Leonardo Araujo
- Leonardo Lazzaro
- Luke Dashjr
- MacroFake
- MarcoFalke
- Martin Leitner-Ankerl
- Martin Zumsande
- Matt Whitlock
- Matthew Zipkin
- Michael Ford
- Miles Liu
- mruddy
- Murray Nesbitt
- muxator
- omahs
- pablomartin4btc
- Pasta
- Pieter Wuille
- Pttn
- Randall Naar
- Riahiamirreza
- roconnor-blockstream
- Russell O'Connor
- Ryan Ofsky
- S3RK
- Sebastian Falbesoner
- Seibart Nedor
- sinetek
- Sjors Provoost
- Skuli Dulfari
- SomberNight
- Stacie Waleyko
- stickies-v
- stratospher
- Suhas Daftuar
- Suriyaa Sundararuban
- TheCharlatan
- Vasil Dimov
- Vasil Stoyanov
- virtu
- w0xlt
- willcl-ark
- yancy
- Yusuf Sahin HAMZA
As well as to everyone that helped with translations on
[Transifex](https://www.transifex.com/bitcoin/bitcoin/).

2023-06-07 23:22:03

- reply

2023-06-07 23:21:51

- reply

📅 Original date posted:2023-05-19
🗒️ Summary of this message: Bitcoin Core version 23.2 is now available, featuring bug fixes, performance improvements, and updated translations for better user experience.
📝 Original message:Bitcoin Core version 23.2 is now available from:
<https://bitcoincore.org/bin/bitcoin-core-23.2/>
Or through BitTorrent:
magnet:?xt=urn:btih:e672796b257f0d3d3043d9022c4df57b2c9f6ede&dn=bitcoin-core-23.2&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969%2Fannounce&tr=udp%3A%2F%2Fexplodie.org%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.torrent.eu.org%3A451%2Fannounce&tr=udp%3A%2F%2Ftrakcer.bitcoin.sprovoost.nl%3A6969
This release includes various bug fixes and performance
improvements, as well as updated translations.
Please report bugs using the issue tracker at GitHub:
<https://github.com/bitcoin/bitcoin/issues>
To receive security and update notifications, please subscribe to:
<https://bitcoincore.org/en/list/announcements/join/>
How to Upgrade
==============
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes in some cases), then run the
installer (on Windows) or just copy over `/Applications/Bitcoin-Qt` (on macOS)
or `bitcoind`/`bitcoin-qt` (on Linux).
Upgrading directly from a version of Bitcoin Core that has reached its EOL is
possible, but it might take some time if the data directory needs to
be migrated. Old
wallet versions of Bitcoin Core are generally supported.
Compatibility
==============
Bitcoin Core is supported and extensively tested on operating systems
using the Linux kernel, macOS 10.15+, and Windows 7 and newer. Bitcoin
Core should also work on most other Unix-like systems but is not as
frequently tested on them. It is not recommended to use Bitcoin Core on
unsupported systems.
### P2P
- #26909 net: prevent peers.dat corruptions by only serializing once
- #27608 p2p: Avoid prematurely clearing download state for other peers
- #27610 Improve performance of p2p inv to send queues
### Build system
- #25436 build: suppress array-bounds errors in libxkbcommon
- #25763 bdb: disable Werror for format-security
- #26944 depends: fix systemtap download URL
- #27462 depends: fix compiling bdb with clang-16 on aarch64
### Miscellaneous
- #25444 ci: macOS task imrovements
- #26388 ci: Use macos-ventura-xcode:14.1 image for "macOS native" task
- #26924 refactor: Add missing includes to fix gcc-13 compile error
Credits
=======
Thanks to everyone who directly contributed to this release:
- Anthony Towns
- Hennadii Stepanov
- MacroFake
- Martin Zumsande
- Michael Ford
- Suhas Daftuar
As well as to everyone that helped with translations on
[Transifex](https://www.transifex.com/bitcoin/bitcoin/).

2023-06-07 23:21:51

- reply

2023-06-07 23:21:50

- reply

📅 Original date posted:2023-05-19
🗒️ Summary of this message: Bitcoin Core version 24.1 is now available with bug fixes, performance improvements, and updated translations. Users are advised to upgrade for security and stability.
📝 Original message:Bitcoin Core version 24.1 is now available from:
<https://bitcoincore.org/bin/bitcoin-core-24.1/>
Or through BitTorrent:
magnet:?xt=urn:btih:ebb58d7495a8aaed2f20ec4ce3e5ae27aff69529&dn=bitcoin-core-24.1&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969%2Fannounce&tr=udp%3A%2F%2Fexplodie.org%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.torrent.eu.org%3A451%2Fannounce&tr=udp%3A%2F%2Ftrakcer.bitcoin.sprovoost.nl%3A6969
This release includes various bug fixes and performance
improvements, as well as updated translations.
Please report bugs using the issue tracker at GitHub:
<https://github.com/bitcoin/bitcoin/issues>
To receive security and update notifications, please subscribe to:
<https://bitcoincore.org/en/list/announcements/join/>
How to Upgrade
==============
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes in some cases), then run the
installer (on Windows) or just copy over `/Applications/Bitcoin-Qt` (on macOS)
or `bitcoind`/`bitcoin-qt` (on Linux).
Upgrading directly from a version of Bitcoin Core that has reached its EOL is
possible, but it might take some time if the data directory needs to
be migrated. Old
wallet versions of Bitcoin Core are generally supported.
Compatibility
==============
Bitcoin Core is supported and extensively tested on operating systems
using the Linux kernel, macOS 10.15+, and Windows 7 and newer. Bitcoin
Core should also work on most other Unix-like systems but is not as
frequently tested on them. It is not recommended to use Bitcoin Core on
unsupported systems.
### P2P
- #26878 I2P network optimizations
- #26909 net: prevent peers.dat corruptions by only serializing once
- #27608 p2p: Avoid prematurely clearing download state for other peers
- #27610 Improve performance of p2p inv to send queues
### RPC and other APIs
- #26515 rpc: Require NodeStateStats object in getpeerinfo
- #27279 doc: fix/improve warning helps in {create,load,unload,restore}wallet
- #27468 rest: avoid segfault for invalid URI
### Build System
- #26944 depends: fix systemtap download URL
- #27462 depends: fix compiling bdb with clang-16 on aarch64
### Wallet
- #26595 wallet: be able to specify a wallet name and passphrase to
migratewallet
- #26675 wallet: For feebump, ignore abandoned descendant spends
- #26679 wallet: Skip rescanning if wallet is more recent than tip
- #26761 wallet: fully migrate address book entries for
watchonly/solvable wallets
- #27053 wallet: reuse change dest when re-creating TX with avoidpartialspends
- #27080 wallet: Zero out wallet master key upon locking so it doesn't
persist in memory
- #27473 wallet: Properly handle "unknown" Address Type
### GUI changes
- gui#687 Load PSBTs using istreambuf_iterator rather than istream_iterator
- gui#704 Correctly limit overview transaction list
### Miscellaneous
- #26880 ci: replace Intel macOS CI job
- #26924 refactor: Add missing includes to fix gcc-13 compile error
Credits
=======
Thanks to everyone who directly contributed to this release:
- Andrew Chow
- Anthony Towns
- Hennadii Stepanov
- John Moffett
- Jon Atack
- Marco Falke
- Martin Zumsande
- Matthew Zipkin
- Michael Ford
- pablomartin4btc
- Sebastian Falbesoner
- Suhas Daftuar
- Thomas Nguyen
- Vasil Dimov
As well as to everyone that helped with translations on
[Transifex](https://www.transifex.com/bitcoin/bitcoin/).

2023-06-07 23:21:50

- reply

2023-06-07 23:17:50

- reply

📅 Original date posted:2022-12-13
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Due to last-minute issues (https://github.com/bitcoin/bitcoin/pull/26616),
24.0, although tagged, was never fully announced or released.
Bitcoin Core version 24.0.1 is now available from:
https://bitcoincore.org/bin/bitcoin-core-24.0.1/
Or through BitTorrent:
magnet:?xt=urn:btih:d7604a67c8ed6e3b35da15138f8ac81d7618788c&dn=bitcoin-core-24.0.1&tr=udp%3A%2F%
2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.opentrackr.org
%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.coppersurfer.tk
%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.leechers-paradise.org
%3A6969%2Fannounce&tr=udp%3A%2F%2Fexplodie.org%3A6969%2Fannounce&tr=udp%3A%2F%
2Ftracker.torrent.eu.org%3A451%2Fannounce&tr=udp%3A%2F%
2Ftracker.bitcoin.sprovoost.nl%3A6969
This release includes new features, various bug fixes and performance
improvements, as well as updated translations.
Please report bugs using the issue tracker at GitHub:
<https://github.com/bitcoin/bitcoin/issues>
To receive security and update notifications, please subscribe to:
<https://bitcoincore.org/en/list/announcements/join/>
How to Upgrade
==============
If you are running an older version, shut it down. Wait until it has
completely
shut down (which might take a few minutes in some cases), then run the
installer (on Windows) or just copy over `/Applications/Bitcoin-Qt` (on
macOS)
or `bitcoind`/`bitcoin-qt` (on Linux).
Upgrading directly from a version of Bitcoin Core that has reached its EOL
is
possible, but it might take some time if the data directory needs to be
migrated. Old
wallet versions of Bitcoin Core are generally supported.
Compatibility
==============
Bitcoin Core is supported and extensively tested on operating systems
using the Linux kernel, macOS 10.15+, and Windows 7 and newer. Bitcoin
Core should also work on most other Unix-like systems but is not as
frequently tested on them. It is not recommended to use Bitcoin Core on
unsupported systems.
Notice of new option for transaction replacement policies
=========================================================
This version of Bitcoin Core adds a new `mempoolfullrbf` configuration
option which allows users to change the policy their individual node
will use for relaying and mining unconfirmed transactions. The option
defaults to the same policy that was used in previous releases and no
changes to node policy will occur if everyone uses the default.
Some Bitcoin services today expect that the first version of an
unconfirmed transaction that they see will be the version of the
transaction that ultimately gets confirmed---a transaction acceptance
policy sometimes called "first-seen".
The Bitcoin Protocol does not, and cannot, provide any assurance that
the first version of an unconfirmed transaction seen by a particular
node will be the version that gets confirmed. If there are multiple
versions of the same unconfirmed transaction available, only the miner
who includes one of those transactions in a block gets to decide which
version of the transaction gets confirmed.
Despite this lack of assurance, multiple merchants and services today
still make this assumption.
There are several benefits to users from removing this *first-seen*
simplification. One key benefit, the ability for the sender of a
transaction to replace it with an alternative version paying higher
fees, was realized in [Bitcoin Core 0.12.0][] (February 2016) with the
introduction of [BIP125][] opt-in Replace By Fee (RBF).
Since then, there has been discussion about completely removing the
first-seen simplification and allowing users to replace any of their
older unconfirmed transactions with newer transactions, a feature called
*full-RBF*. This release includes a `mempoolfullrbf` configuration
option that allows enabling full-RBF, although it defaults to off
(allowing only opt-in RBF).
Several alternative node implementations have already enabled full-RBF by
default for years, and several contributors to Bitcoin Core are
advocating for enabling full-RBF by default in a future version of
Bitcoin Core.
As more nodes that participate in relay and mining begin enabling
full-RBF, replacement of unconfirmed transactions by ones offering higher
fees may rapidly become more reliable.
Contributors to this project strongly recommend that merchants and services
not accept unconfirmed transactions as final, and if they insist on doing
so,
to take the appropriate steps to ensure they have some recourse or plan for
when their assumptions do not hold.
[Bitcoin Core 0.12.0]:
https://bitcoincore.org/en/releases/0.12.0/#opt-in-replace-by-fee-transactions
[bip125]: https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki
Notable changes
===============
P2P and network changes
- - -----------------------
- - - To address a potential denial-of-service, the logic to download
headers
from peers
has been reworked. This is particularly relevant for nodes starting up
for the
first time (or for nodes which are starting up after being offline for a
long time).
Whenever headers are received from a peer that have a total chainwork
that is either
less than the node's `-minimumchainwork` value or is sufficiently below
the work at
the node's tip, a "presync" phase will begin, in which the node will
download the
peer's headers and verify the cumulative work on the peer's chain, prior
to storing
those headers permanently. Once that cumulative work is verified to be
sufficiently high,
the headers will be redownloaded from that peer and fully validated and
stored.
This may result in initial headers sync taking longer for new nodes
starting up for
the first time, both because the headers will be downloaded twice, and
because the effect
of a peer disconnecting during the presync phase (or while the node's
best headers chain has less
than `-minimumchainwork`), will result in the node needing to use the
headers presync mechanism
with the next peer as well (downloading the headers twice, again).
(#25717)
- - - With I2P connections, a new, transient address is used for each
outbound
connection if `-i2pacceptincoming=0`. (#25355)
Updated RPCs
- - ------------
- - - The `-deprecatedrpc=softforks` configuration option has been removed.
The
RPC `getblockchaininfo` no longer returns the `softforks` field, which was
previously deprecated in 23.0. (#23508) Information on soft fork status is
now only available via the `getdeploymentinfo` RPC.
- - - The `deprecatedrpc=exclude_coinbase` configuration option has been
removed.
The `receivedby` RPCs (`listreceivedbyaddress`, `listreceivedbylabel`,
`getreceivedbyaddress` and `getreceivedbylabel`) now always return results
accounting for received coins from coinbase outputs, without an option to
change that behaviour. Excluding coinbases was previously deprecated in
23.0.
(#25171)
- - - The `deprecatedrpc=fees` configuration option has been removed. The
top-level
fee fields `fee`, `modifiedfee`, `ancestorfees` and `descendantfees` are
no
longer returned by RPCs `getmempoolentry`, `getrawmempool(verbose=true)`,
`getmempoolancestors(verbose=true)` and
`getmempooldescendants(verbose=true)`.
The same fee fields can be accessed through the `fees` object in the
result.
The top-level fee fields were previously deprecated in 23.0. (#25204)
- - - The `getpeerinfo` RPC has been updated with a new `presynced_headers`
field,
indicating the progress on the presync phase mentioned in the
"P2P and network changes" section above.
Changes to wallet related RPCs can be found in the Wallet section below.
New RPCs
- - --------
- - - The `sendall` RPC spends specific UTXOs to one or more recipients
without creating change. By default, the `sendall` RPC will spend
every UTXO in the wallet. `sendall` is useful to empty wallets or to
create a changeless payment from select UTXOs. When creating a payment
from a specific amount for which the recipient incurs the transaction
fee, continue to use the `subtractfeefromamount` option via the
`send`, `sendtoaddress`, or `sendmany` RPCs. (#24118)
- - - A new `gettxspendingprevout` RPC has been added, which scans the
mempool to find
transactions spending any of the given outpoints. (#24408)
- - - The `simulaterawtransaction` RPC iterates over the inputs and outputs
of the given
transactions, and tallies up the balance change for the given wallet.
This can be
useful e.g. when verifying that a coin join like transaction doesn't
contain unexpected
inputs that the wallet will then sign for unintentionally. (#22751)
Updated REST APIs
- - -----------------
- - - The `/headers/` and `/blockfilterheaders/` endpoints have been updated
to use
a query parameter instead of path parameter to specify the result count.
The
count parameter is now optional, and defaults to 5 for both endpoints.
The old
endpoints are still functional, and have no documented behaviour change.
For `/headers`, use
`GET /rest/headers/<BLOCK-HASH>.<bin|hex|json>?count=<COUNT=5>`
instead of
`GET /rest/headers/<COUNT>/<BLOCK-HASH>.<bin|hex|json>` (deprecated)
For `/blockfilterheaders/`, use
`GET
/rest/blockfilterheaders/<FILTERTYPE>/<BLOCK-HASH>.<bin|hex|json>?count=<COUNT=5>`
instead of
`GET
/rest/blockfilterheaders/<FILTERTYPE>/<COUNT>/<BLOCK-HASH>.<bin|hex|json>`
(deprecated)
(#24098)
Build System
- - ------------
- - - Guix builds are now reproducible across architectures (x86_64 &
aarch64). (#21194)
New settings
- - ------------
- - - A new `mempoolfullrbf` option has been added, which enables the
mempool
to
accept transaction replacement without enforcing BIP125 replaceability
signaling. (#25353)
Wallet
- - ------
- - - The `-walletrbf` startup option will now default to `true`. The
wallet will now default to opt-in RBF on transactions that it creates.
(#25610)
- - - The `replaceable` option for the `createrawtransaction` and
`createpsbt` RPCs will now default to `true`. Transactions created
with these RPCs will default to having opt-in RBF enabled. (#25610)
- - - The `wsh()` output descriptor was extended with Miniscript support.
You
can import Miniscript
descriptors for P2WSH in a watchonly wallet to track coins, but you can't
spend from them using
the Bitcoin Core wallet yet.
You can find more about Miniscript on the [reference website](
https://bitcoin.sipa.be/miniscript/). (#24148)
- - - The `tr()` output descriptor now supports multisig scripts through the
`multi_a()` and
`sortedmulti_a()` functions. (#24043)
- - - To help prevent fingerprinting transactions created by the Bitcoin
Core
wallet, change output
amounts are now randomized. (#24494)
- - - The `listtransactions`, `gettransaction`, and `listsinceblock`
RPC methods now include a wtxid field (hash of serialized transaction,
including witness data) for each transaction. (#24198)
- - - The `listsinceblock`, `listtransactions` and `gettransaction` output
now contain a new
`parent_descs` field for every "receive" entry. (#25504)
- - - A new optional `include_change` parameter was added to the
`listsinceblock` command.
- - - RPC `getreceivedbylabel` now returns an error, "Label not found
in wallet" (-4), if the label is not in the address book. (#25122)
Migrating Legacy Wallets to Descriptor Wallets
- - ---------------------------------------------
An experimental RPC `migratewallet` has been added to migrate Legacy
(non-descriptor) wallets to
Descriptor wallets. More information about the migration process is
available in the
[documentation](
https://github.com/bitcoin/bitcoin/blob/master/doc/managing-wallets.md#migrating-legacy-wallets-to-descriptor-wallets
).
GUI changes
- - -----------
- - - A new menu item to restore a wallet from a backup file has been added
(gui#471).
- - - Configuration changes made in the bitcoin GUI (such as the pruning
setting,
proxy settings, UPNP preferences) are now saved to `<datadir>/settings.json`
file rather than to the Qt settings backend (windows registry or unix
desktop
config files), so these settings will now apply to bitcoind, instead of
being
ignored. (#15936, gui#602)
- - - Also, the interaction between GUI settings and `bitcoin.conf` settings
is
simplified. Settings from `bitcoin.conf` are now displayed normally in the
GUI
settings dialog, instead of in a separate warning message ("Options set in
this
dialog are overridden by the configuration file: -setting=value"). And these
settings can now be edited because `settings.json` values take precedence
over
`bitcoin.conf` values. (#15936)
Low-level changes
=================
RPC
- - ---
- - - The `deriveaddresses`, `getdescriptorinfo`, `importdescriptors` and
`scantxoutset` commands now
accept Miniscript expression within a `wsh()` descriptor. (#24148)
- - - The `getaddressinfo`, `decodescript`, `listdescriptors` and
`listunspent` commands may now output
a Miniscript descriptor inside a `wsh()` where a `wsh(raw())` descriptor
was previously returned. (#24148)
Credits
=======
Thanks to everyone who directly contributed to this release:
- - - /dev/fd0
- - - 0xb10c
- - - Adam Jonas
- - - akankshakashyap
- - - Ali Sherief
- - - amadeuszpawlik
- - - Andreas Kouloumos
- - - Andrew Chow
- - - Anthony Towns
- - - Antoine Poinsot
- - - Antoine Riard
- - - Aurèle Oulès
- - - avirgovi
- - - Ayush Sharma
- - - Baas
- - - Ben Woosley
- - - BrokenProgrammer
- - - brunoerg
- - - brydinh
- - - Bushstar
- - - Calvin Kim
- - - CAnon
- - - Carl Dong
- - - chinggg
- - - Cory Fields
- - - Daniel Kraft
- - - Daniela Brozzoni
- - - darosior
- - - Dave Scotese
- - - David Bakin
- - - dergoegge
- - - dhruv
- - - Dimitri
- - - dontbyte
- - - Duncan Dean
- - - eugene
- - - Eunoia
- - - Fabian Jahr
- - - furszy
- - - Gleb Naumenko
- - - glozow
- - - Greg Weber
- - - Gregory Sanders
- - - gruve-p
- - - Hennadii Stepanov
- - - hiago
- - - Igor Bubelov
- - - ishaanam
- - - Jacob P.
- - - Jadi
- - - James O'Beirne
- - - Janna
- - - Jarol Rodriguez
- - - Jeremy Rand
- - - Jeremy Rubin
- - - jessebarton
- - - João Barbosa
- - - John Newbery
- - - Jon Atack
- - - Josiah Baker
- - - Karl-Johan Alm
- - - KevinMusgrave
- - - Kiminuo
- - - klementtan
- - - Kolby Moroz
- - - kouloumos
- - - Kristaps Kaupe
- - - Larry Ruane
- - - Luke Dashjr
- - - MarcoFalke
- - - Marnix
- - - Martin Leitner-Ankerl
- - - Martin Zumsande
- - - Michael Dietz
- - - Michael Folkson
- - - Michael Ford
- - - Murch
- - - mutatrum
- - - muxator
- - - Oskar Mendel
- - - Pablo Greco
- - - pasta
- - - Patrick Strateman
- - - Pavol Rusnak
- - - Peter Bushnell
- - - phyBrackets
- - - Pieter Wuille
- - - practicalswift
- - - randymcmillan
- - - Robert Spigler
- - - Russell Yanofsky
- - - S3RK
- - - Samer Afach
- - - Sebastian Falbesoner
- - - Seibart Nedor
- - - Shashwat
- - - Sjors Provoost
- - - Smlep
- - - sogoagain
- - - Stacie
- - - Stéphan Vuylsteke
- - - Suhail Saqan
- - - Suhas Daftuar
- - - t-bast
- - - TakeshiMusgrave
- - - Vasil Dimov
- - - W. J. van der Laan
- - - w0xlt
- - - whiteh0rse
- - - willcl-ark
- - - William Casarin
- - - Yancy Ribbens
As well as to everyone that helped with translations on
[Transifex](https://www.transifex.com/bitcoin/bitcoin/).
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEz7FuIclQ9n+pXlWPLuufXMCVJsEFAmOYaq4ACgkQLuufXMCV
JsH8DQ/+PFPSLM3lOL2yZAHMlXuEKbG8at/H+pXDjwDcZsKs+cuF1Z3JfR6VmAX9
OB8tOvBbqJklZd6GlCeDs4XsBAdXppy50fdZSQ6Dqh7N/+nERUT8GEwTtU11sL7W
vAVWhOmUn5fgCqOI/J2r4jjpZYMDys/NaCUYxmUF5Vm4JaJcs1JIfSUyHtQHdS6t
VIdqb8D2+9mXM7qXbJ6OzF9KzrKFcujRHGPzcTnDvF3kOYKlpjT8w6bfFiBeuSeo
G56X5CR61iXNU5W9HmHIKXBZv6Vnblc9cust7/5ESdgn6OMEnYghnaFSuMsWWAFd
OKAGbuzunh+G9wMl1JWWG4sVVWLDtz6jNwwUu+1a0wrFryYPaPnq/JK09VL32xJr
WKx6iNYqsEcno6kXfjSxLsQTIKzJw2T7iYaQCe8KTpYkaGitNzYMpEtFD68PU/gj
0LEf1sV+BgCuBR7hSBv31pse195Fd/wR71Yk4VVYx26u+82fIhK3ssyWxiiL6ycB
K7FK9Q4QCt0QlO30oD/y/YQMuyVoVCf71qgp5ZB4TehwP+U4qYTp8wiCej7ta0rY
vwjHbFZCYhzw05pIGE7bkbpGjdrnWK5ulaQztGAH6IXw0IPfsh9UJIr42VuXh1Nt
AH6dVC+VwKsr/FjPHuFaj7lwyGw831bKiePptaQYPN9MEELqZqI=
=5tAr
-----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20221213/956ca15f/attachment-0001.html>

2023-06-07 23:17:50

- reply