from:"W. J. van der Laan via bitcoin\-core\-dev"

Re: [bitcoin-core-dev] Revoking "Bitcoin Core binary release signing key"

2023-02-11 Thread W. J. van der Laan via bitcoin-core-dev



-BEGIN PGP PUBLIC KEY BLOCK-
Comment: This is a revocation certificate

iQLoBCABCgDSFiEEAepUht4YqILUwmhFkMgBnjbC6WQFAmPnkfe0HQNUaGlzIGtl
eSB3YXMgdXNlZCB0byBzaWduIEJpdGNvaW4gQ29yZSByZWxlYXNlcyAwLjIxIGFu
ZCBiZWZvcmUuIFRoZSBsYXN0IHN1Y2ggcmVsZWFzZXMgd2VyZSAwLjIwLjIgYW5k
IDAuMjEuMiByZXNwZWN0aXZlbHkgaW4gMjAyMS4gRG8gbm90IHRydXN0IHRoZSBr
ZXkgZm9yIHJlbGVhc2VzIGFmdGVyIDIwMjIuAAoJEJDIAZ42wulkujkP/28igLT2
m90zhX53xDAVeE2P+WyORyf/eR+Sez7SMqpofuABvZRxuF2UHaRKTzoJUuzopNdE
RO1W2KGXb1DIbDCm+lpyRMXMIZ7dLy7BbwDfFwhTEplyKq7UeXH51FibFynfwX3y
Uiwi5hMXhv5EpTTjbyYUuo/tqm5EAXZuvx4vNcX9Kdhy7UP1SKvpvE1Ex5DNcctW
0nzex5xecba13JAFX6y5YQUvKPil6cVtj434ba3GP6oN4GgI3rqSYM9m/YFQuRik
W11ZLoSdoIfw33609qh71T8s7SmW7h57kaa3y7p2u6XbPcbinDT4uuamfG+Q9YRc
AlPYEBSCWej/fW7BExB2+U4VWzbNQEJnu9Upz86gCzQ91d4wzzSxiQQj8RlqXTsD
aOI0VoXrVF9eG9kL/qJD7+ne3V8fFb3YsBMA8ZeQDu6ImHipThUqzkcAhrZsZZaH
LJKXN1Lyvia7ZVJebAJ0uMy4HvkmWTVgnPmuY2jXVjyL+5oBENPcqXSMFNJQ+cgC
feVc1yKDBSWZVd4GvhZ3lVdb21/bltJ1jqHPQVg55zi5JKB9BFdu6NunS9SXoNDR
xFfbb+ezL2+Fm3FBlpv46I/g49kS3ySbNdKifcG3aC41D3vKTInU7w1BBagOcXQV
jM4AzbOhveMklNyc8VcB30XiqO3vGWGWcC7e
=jIFT
-END PGP PUBLIC KEY BLOCK-

$ gpg --list-packets --verbose < revoke-laanwj-releases.asc 
gpg: armor header: Comment: This is a revocation certificate
# off=0 ctb=89 tag=2 hlen=3 plen=744
:signature packet: algo 1, keyid 90C8019E36C2E964
version 4, created 1676120567, md5len 0, sigclass 0x20
digest algo 10, begin of digest ba 39
hashed subpkt 33 len 21 (issuer fpr v4 
01EA5486DE18A882D4C2684590C8019E36C2E964)
hashed subpkt 2 len 4 (sig created 2023-02-11)
hashed subpkt 29 len 179 (revocation reason 0x03 (This key was used to 
sign Bitcoin Core releases 0.21 and before. The last such releases were 0.20.2 
and 0.21.2 respectively in 2021. Do not trust the key for releases after 2022.)




--- Original Message ---
On Thursday, February 9th, 2023 at 2:59 PM, W. J. van der Laan 
 wrote:


> 
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hello,
> 
> Just a heads-up that I'm revoking the "Bitcoin Core binary release signing 
> key" PGP key (fingerprint 01EA5486DE18A882D4C2684590C8019E36C2E964).
> 
> It was the sole key used to sign the binary distributions of 0.21.x and 
> before. Releases 22.0 and later are signed by every builder, and are not 
> affected.
> 
> To be clear: the key was not compromised. However, I cannot warrant its 
> safety. It is a single point of failure, after all.
> 
> Please remove it from verification pipelines.
> 
> See also https://github.com/bitcoin-core/bitcoincore.org/pull/951
> 
> W.
> -BEGIN PGP SIGNATURE-
> 
> iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAmPk/AoACgkQHkrtYphs
> 0l3svwf+Nc1w2fCO7dI80E5WmiuKDrOCP2V91FzuwTBnjCZUPmvg1dWPw4f76ray
> Cra2LqUIvW2fSfjq4fR+ca/KdfhEoGvZ17drHray1x21kmXRQ5V5I+c4RSVHelgG
> 6iLXykbpJR68rdudVjVQswQG5u+/eSg7x4qe0V3ED3gdCzNoNcYEFoF0wuz5bnbo
> E0hco6piCdEkwf6/6/NWWqpKsYigvuwacwl1hCqAj9Y5vMzPhAvmVj90lT8jqhFf
> 610eXJqeg021sK7JhcYW9yG0lMHNQ/sz16A/NzkneGGKVU5AvQAPRnKVXR3dqWxS
> o7Uqe2A/rXRgWAE1UG3qEswyHGg1Gw==
> =0bDa
> -END PGP SIGNATURE-
___
bitcoin-core-dev mailing list
bitcoin-core-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev

[bitcoin-core-dev] Revoking "Bitcoin Core binary release signing key"

2023-02-09 Thread W. J. van der Laan via bitcoin-core-dev

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

Just a heads-up that I'm revoking the "Bitcoin Core binary release signing key" 
PGP key (fingerprint 01EA5486DE18A882D4C2684590C8019E36C2E964).

It was the sole key used to sign the binary distributions of 0.21.x and before. 
Releases 22.0 and later are signed by every builder, and are not affected.

To be clear: the key was not compromised. However, I cannot warrant its safety. 
It is a single point of failure, after all.

Please remove it from verification pipelines.

See also https://github.com/bitcoin-core/bitcoincore.org/pull/951

W.
-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAmPk/AoACgkQHkrtYphs
0l3svwf+Nc1w2fCO7dI80E5WmiuKDrOCP2V91FzuwTBnjCZUPmvg1dWPw4f76ray
Cra2LqUIvW2fSfjq4fR+ca/KdfhEoGvZ17drHray1x21kmXRQ5V5I+c4RSVHelgG
6iLXykbpJR68rdudVjVQswQG5u+/eSg7x4qe0V3ED3gdCzNoNcYEFoF0wuz5bnbo
E0hco6piCdEkwf6/6/NWWqpKsYigvuwacwl1hCqAj9Y5vMzPhAvmVj90lT8jqhFf
610eXJqeg021sK7JhcYW9yG0lMHNQ/sz16A/NzkneGGKVU5AvQAPRnKVXR3dqWxS
o7Uqe2A/rXRgWAE1UG3qEswyHGg1Gw==
=0bDa
-END PGP SIGNATURE-
___
bitcoin-core-dev mailing list
bitcoin-core-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev

[bitcoin-core-dev] Bitcoin Core 23.0 released

2022-04-25 Thread W. J. van der Laan via bitcoin-core-dev

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Bitcoin Core version 23.0 is now available from:

Or through BitTorrent:

magnet:?xt=urn:btih:32bc317cce76b966a26bdb53d42f64d66d595954=bitcoin-core-23.0=udp%3A%2F%2Ftracker.openbittorrent.com%3A80=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969%2Fannounce=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969%2Fannounce=udp%3A%2F%2Fexplodie.org%3A6969%2Fannounce=udp%3A%2F%2Ftracker.torrent.eu.org%3A451%2Fannounce=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:

To receive security and update notifications, please subscribe to:

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 Mac)
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
- ---

- - 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. (#21528)

- - 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. (#23542)

- - Full support has been added for the CJDNS network. See the new option
`-cjdnsreachable` and
[doc/cjdns.md](https://github.com/bitcoin/bitcoin/tree/23.x/doc/cjdns.md)
(#23077)

Fee estimation changes
- --

- - Fee estimation now takes the feerate of replacement (RBF) transactions into
account. (#22539)

Rescan startup parameter removed
-

The `-rescan` startup parameter has been removed. Wallets which require
rescanning due to corruption will still be rescanned on startup.
Otherwise, please use the `rescanblockchain` RPC to trigger a rescan. (#23123)

Tracepoints and Userspace, Statically Defined Tracing support
- -

Bitcoin Core release binaries for Linux now include experimental tracepoints
which
act as an interface for process-internal events. These can be used for review,
debugging, monitoring, and more. The tracepoint API is semi-stable. While the
API
is tested, process internals might change between releases requiring changes to
the
tracepoints. Information about the existing tracepoints can be found under
[doc/tracing.md](https://github.com/bitcoin/bitcoin/blob/23.x/doc/tracing.md)
and
usage examples are provided in
[contrib/tracing/](https://github.com/bitcoin/bitcoin/tree/23.x/contrib/tracing).

Updated RPCs
-

- - The `validateaddress` RPC now returns an `error_locations` array for invalid
addresses, with the indices of invalid character locations in the address (if
known). For example, this will attempt to locate up to two Bech32 errors, and
return their locations if successful. Success and correctness are only
guaranteed
if fewer than two substitution errors have been made.
The error message returned in the `error` field now also returns more specific
errors when decoding fails. (#16807)

- - The `-deprecatedrpc=addresses` configuration option has been removed. RPCs
`gettxout`, `getrawtransaction`, `decoderawtransaction`, `decodescript`,
`gettransaction verbose=true` and REST endpoints `/rest/tx`, `/rest/getutxos`,
`/rest/block` no longer return the `addresses` and `reqSigs` fields, which
were previously deprecated in 22.0. (#22650)
- - The `getblock` RPC command now supports verbosity level 3 containing
transaction inputs'
`prevout` information. The existing `/rest/block/` REST endpoint is modified
to contain
this information too. Every `vin` field will contain an additional `prevout`
subfield
describing the spent output. `prevout` contains the following keys:
- `generated` - true

[bitcoin-core-dev] Bitcoin Core 23.0 release candidate 5 available

2022-04-18 Thread W. J. van der Laan via bitcoin-core-dev

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Binaries for bitcoin Core version 23.0rc5 are available from:

https://bitcoincore.org/bin/bitcoin-core-23.0/test.rc5/

The source code can be found in git under the signed tag

https://github.com/bitcoin/bitcoin/tree/v23.0rc5

This is a release candidate for a new major version release.

Preliminary release notes for the release can be found here:


https://github.com/bitcoin-core/bitcoin-devwiki/wiki/23.0-Release-Notes-draft

Release candidates are test versions for releases. If no critical problems
are found, this release candidate will be tagged as 23.0.

For testing guidance see:

https://github.com/bitcoin/bitcoin/issues/24501

Note: rc5 only contains a change for Windows, if you are testing on any other
platform, there is no need to update from rc4.
-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAmJdPycACgkQHkrtYphs
0l3/4Qf8CQMQ1kFLzmputQtC5mNjpb1sH7pG7w/XJH2J+hPAtCWRVcjTWoPOM0V3
ORgaHA+bBLWNs4WV0hXqTAwoZqdTMMuh7E/oElLYLiFr1laGOCvbaFsEhwPkKRcV
aQf1IlrFIhZ0YE3kmEkiWjkHWvuAqre5g0v9EpGufvCamAqTtU4s3wxrUyszDQgC
ZI8eUScVw0+xO+PeYf+BDj72iigV6xikGXNtbNN61YWnzRQHSVCMkADLpNXWRhVy
hJgSl61UDY4pYj0M4zV0mR1ONn/pmsLWqxOIM5c3BP3kx0JYwqLv8IVsyYg5oisS
THdiHFSO5issYU2OzfIwiRvC/qF4vg==
=VQMc
-END PGP SIGNATURE-

___
bitcoin-core-dev mailing list
bitcoin-core-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev

[bitcoin-core-dev] Bitcoin Core 23.0 release candidate 4 available

2022-04-11 Thread W. J. van der Laan via bitcoin-core-dev

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Binaries for bitcoin Core version 23.0rc4 are available from:

https://bitcoincore.org/bin/bitcoin-core-23.0/test.rc4/

The source code can be found in git under the signed tag

https://github.com/bitcoin/bitcoin/tree/v23.0rc4

This is a release candidate for a new major version release.

Preliminary release notes for the release can be found here:


https://github.com/bitcoin-core/bitcoin-devwiki/wiki/23.0-Release-Notes-draft

Release candidates are test versions for releases. If no critical problems
are found, this release candidate will be tagged as 23.0.

For testing guidance see:

https://github.com/bitcoin/bitcoin/issues/24501
-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAmJUAkwACgkQHkrtYphs
0l11NAf8DcRDKDrbu+7sQCgjSqCbk+9A+T2A7ir1GFK1Sk7in1XYiAaOyM3lP3xf
nFO3UYZTv82XSQImQwUgxzZvy75b8X7lLsoFA1I13b3/S2CzY56g9Rlq+SKnWva7
RfoDFGu0rQE4e5c92j29hWSw1parx+AZyOWJZg5IuF6Unq9IYx289/4KGpTLj5vJ
UJM3Nh6DxRUmDh8onX2nTcT13jfCm+NsyLFf1gg3fizgbXuBFVPR3Sd++ctI1WIQ
/Vf8iRZq2vsCOZlB903Pe+gRUHKCaG4AfdlxTf2Sd2Vhf+etGaazmMWpXYPCUCop
JqzIz+EfLw0/2de1BdGQzLhmPMqObA==
=XaW1
-END PGP SIGNATURE-

___
bitcoin-core-dev mailing list
bitcoin-core-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev

[bitcoin-core-dev] Bitcoin Core 23.0 release candidate 2 available

2022-03-17 Thread W. J. van der Laan via bitcoin-core-dev

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Binaries for bitcoin Core version 23.0rc2 are available from:

https://bitcoincore.org/bin/bitcoin-core-23.0/test.rc2/

The source code can be found in git under the signed tag

https://github.com/bitcoin/bitcoin/tree/v23.0rc2

This is a release candidate for a new major version release.

Preliminary release notes for the release can be found here:


https://github.com/bitcoin-core/bitcoin-devwiki/wiki/23.0-Release-Notes-draft

Release candidates are test versions for releases. If no critical problems
are found, this release candidate will be tagged as 23.0.

For testing and up-to-date verification instructions refer to:

https://github.com/bitcoin/bitcoin/issues/24501
-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAmIzOu8ACgkQHkrtYphs
0l10yQgAl/5utdmUDMcuW1Nc/cwGrESW/vnP/Q5yebGRDm5alCIfp+9x7Y11ZVA7
i+wYKXLql6opUL20vEHJU167I3L+XRAdlCh0UqVPk6PjW8OEEIR8/rX7lVXgKzW0
5dd4PCHFoS51U1ifT6IsHeQVZa3swdLnXdiQiGiYR24sJnrZ3y3e4N8F8P0vLNRF
Ndc2TnooyPtVWCx1PF3UNQAMPmCHkKsl08WvXcaRs+gbX97Pa84cHJXiL5FQ7EL3
YxlEORf0pKZWk62/pEkwTxeUYr9KGf2cKncbr6dO6tHS+OH0yj+5fIpUgqmhA+LB
YwHwy1dR/Wjew+ykUCgYNdX0xHXB6A==
=FDY/
-END PGP SIGNATURE-
___
bitcoin-core-dev mailing list
bitcoin-core-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev

[bitcoin-core-dev] Translation for Bitcoin Core 23.0 has started

2022-02-04 Thread W. J. van der Laan via bitcoin-core-dev

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Messages for the upcoming 23.x release can now be translated on the Transifex 
project, https://www.transifex.com/bitcoin/bitcoin/qt-translation-023x/ .

Translations for 0.21.x have been locked.

Please note that developer notes are available for some strings. If you wish 
that developer notes to be added to particular strings, don't hesitate to open 
an issue in https://github.com/bitcoin-core/gui/issues.

For more information about the phases of the release refer to the release 
schedule: https://github.com/bitcoin/bitcoin/issues/22969

laanwj
-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAmH86sMACgkQHkrtYphs
0l1/zAf/UmScGPFmj3jrWTtyB3iDTQLPa/Het9+pW1EgIC/jmbnbP1lrtokI1CvB
nPe9U+e6Ga9W7ZEuboxITWTV6VqjuDVu0y1qFN/Nf7XADLuOrnNibL72LjQyhn/3
xeePcXj6YPr/pbNSgrqKV5JO4lLCU15E/2NIbqcZwiTIMWLHfpL/MD4SEzR1tfWO
UQaJsEnwYU9d6t9MJBgkGuzDTVzF1SwRUWGYttCNf6VMwmNW5KlqPcsXHuaqHbpD
iaRFOv40lMIuH71L4oAcmmpCmbe52FBZzsim3QhqLwh25FPWYCzh/OpP96ycr4rG
EBKfoH6YJyc+1wvINhCPR6F/0xsbXA==
=dktV
-END PGP SIGNATURE-
___
bitcoin-core-dev mailing list
bitcoin-core-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev

[bitcoin-core-dev] Bitcoin Core 22.0 release candidate 3 available

2021-08-30 Thread W. J. van der Laan via bitcoin-core-dev

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Binaries for bitcoin Core version 22.0rc3 are available from:

https://bitcoincore.org/bin/bitcoin-core-22.0/test.rc3/

Source code can be found in git under the signed tag

https://github.com/bitcoin/bitcoin/tree/v22.0rc3

This is a release candidate for a new major version release.

Preliminary release notes for the release can be found here:


https://github.com/bitcoin-core/bitcoin-devwiki/wiki/22.0-Release-Notes-draft

Release candidates are test versions for releases. When no critical problems
are found, this release candidate will be tagged as 22.0.

For testing and up-to-date verification instructions see this issue:

https://github.com/bitcoin/bitcoin/issues/22634
-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAmEso64ACgkQHkrtYphs
0l1L6AgAx/KKZ9J6XTe+1uLK+UboeXEWbYxyO7D6kcVB7upIfFsaD6397J3D6rEI
cQ98hsgYLhoBWruDZka4aShDaN7gja5sYQ8jSgsPHFHcii7PDA3zrofR4UNPdDXa
mFJaPIoR66b8fJWVPitMPe0u3Y51Js/sdPkiQgaUcmL4dCc/gfJBKK0WBEHQpItp
V1IwGwzpBJNG0Gkoi5Y/4qmV0rJFcm9MYSk/WWKqA0Oub8dZc6vtBXcX6dYtdIY5
RUOjYAlGdYnay5cFjzRpQ5kJvBFRZCVfT23WSOYdR9h7x4FvsarpmNMTG8szOWSt
IoEETTf6twJb3k5kD3OfgbKbWKll6g==
=XDT5
-END PGP SIGNATURE-

___
bitcoin-core-dev mailing list
bitcoin-core-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev

[bitcoin-core-dev] Bitcoin Core 22.0 release candidate 2 available

2021-08-05 Thread W. J. van der Laan via bitcoin-core-dev

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Binaries for bitcoin Core version 22.0rc2 are available from:

https://bitcoincore.org/bin/bitcoin-core-22.0/test.rc2/

Source code can be found in git under the signed tag

https://github.com/bitcoin/bitcoin/tree/v22.0rc2

This is a release candidate for a new major version release.

Preliminary release notes for the release can be found here:


https://github.com/bitcoin-core/bitcoin-devwiki/wiki/22.0-Release-Notes-draft

Release candidates are test versions for releases. When no critical problems
are found, this release candidate will be tagged as 22.0.

For testing and up-to-date verification instructions see this issue:

https://github.com/bitcoin/bitcoin/issues/22634
-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAmEL9AQACgkQHkrtYphs
0l03ZggAiswIbX/S5RPfkJPTbYD3djjAUm7KfhxNrobRPaNHU8GQIipJImQrk3mr
cIYTxTF3y5BxFll721y5pi5kOSH2XO//IHD2RMVnAJrOEfETD/pS9LBVNUUzq2pW
EQnQeASLIKVV+vL4/90XkpnXQOlgLIZcfGBJw7BIMsmd+Wb9+0Czhz4VO7CSvm8t
ip67v/9UPXw8PrH4Cg3TX0fkTOAdR65JS4ZdE5oJxwRFYZDkgg7yq9WClK6G2lpX
T+88vIHYJfDygF8ycZ039H8AiqlTCBfnFHirkyg/prcoyqy/gohYLOxDCmj6irSv
ktHaBR7NTeFxDHIixFr+fjjJTOmlQw==
=cVFK
-END PGP SIGNATURE-

___
bitcoin-core-dev mailing list
bitcoin-core-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev

[bitcoin-core-dev] Bitcoin Core 0.21.1 released

2021-05-02 Thread W. J. van der Laan via bitcoin-core-dev

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

0.21.1 Release Notes

Bitcoin Core version 0.21.1 is now available from:

Or through Bittorrent:

magnet:?xt=urn:btih:205b0189271c50a02fe966491e15737a01f94e08=bitcoin-core-0.21.1=udp%3A%2F%2Ftracker.openbittorrent.com%3A80=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969%2Fannounce=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969%2Fannounce=udp%3A%2F%2Fexplodie.org%3A6969%2Fannounce=udp%3A%2F%2Ftracker.torrent.eu.org%3A451%2Fannounce=udp%3A%2F%2Ftracker.bitcoin.sprovoost.nl%3A6969

This minor release includes various bug fixes and performance
improvements, as well as updated translations.

Please report bugs using the issue tracker at GitHub:

To receive security and update notifications, please subscribe to:

How to Upgrade
==

Compatibility
==

Bitcoin Core is supported and extensively tested on operating systems
using the Linux kernel, macOS 10.12+, 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.

- From Bitcoin Core 0.20.0 onwards, macOS versions earlier than 10.12 are no
longer supported. Additionally, Bitcoin Core does not yet change appearance
when macOS "dark mode" is activated.

Notable changes
===

## Taproot Soft Fork

Included in this release are the mainnet and testnet activation
parameters for the taproot soft fork (BIP341) which also adds support
for schnorr signatures (BIP340) and tapscript (BIP342).

If activated, these improvements will allow users of single-signature
scripts, multisignature scripts, and complex contracts to all use
identical-appearing commitments that enhance their privacy and the
fungibility of all bitcoins. Spenders will enjoy lower fees and the
ability to resolve many multisig scripts and complex contracts with the
same efficiency, low fees, and large anonymity set as single-sig users.
Taproot and schnorr also include efficiency improvements for full nodes
such as the ability to batch signature verification. Together, the
improvements lay the groundwork for future potential
upgrades that may improve efficiency, privacy, and fungibility further.

Activation for taproot is being managed using a variation of BIP9
versionbits called Speedy Trial (described in BIP341). Taproot's
versionbit is bit 2, and nodes will begin tracking which blocks signal
support for taproot at the beginning of the first retarget period after
taproot’s start date of 24 April 2021. If 90% of blocks within a
2,016-block retarget period (about two weeks) signal support for taproot
prior to the first retarget period beginning after the time of 11 August
2021, the soft fork will be locked in, and taproot will then be active
as of block 709632 (expected in early or mid November).

Should taproot not be locked in via Speedy Trial activation, it is
expected that a follow-up activation mechanism will be deployed, with
changes to address the reasons the Speedy Trial method failed.

This release includes the ability to pay taproot addresses, although
payments to such addresses are not secure until taproot activates.
It also includes the ability to relay and mine taproot transactions
after activation. Beyond those two basic capabilities, this release
does not include any code that allows anyone to directly use taproot.
The addition of taproot-related features to Bitcoin Core's wallet is
expected in later releases once taproot activation is assured.

All users, businesses, and miners are encouraged to upgrade to this
release (or a subsequent compatible release) unless they object to
activation of taproot. If taproot is locked in, then upgrading before
block 709632 is highly recommended to help enforce taproot's new rules
and to avoid the unlikely case of seeing falsely confirmed transactions.

Miners who want to activate Taproot should preferably use this release
to control their signaling. The `getblocktemplate` RPC results will
automatically be updated to signal once the appropriate start has been
reached and continue signaling until the timeout occurs or taproot
activates. Alternatively, miners may manually start signaling on bit 2
at any time; if taproot

[bitcoin-core-dev] Bitcoin Core 0.21.1 release candidate 1 available

2021-04-18 Thread W. J. van der Laan via bitcoin-core-dev

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Binaries for bitcoin Core version 0.21.1rc1 are available from:

https://bitcoincore.org/bin/bitcoin-core-0.21.1/test.rc1/

Source code can be found in git under the signed tag

https://github.com/bitcoin/bitcoin/tree/v0.21.1rc1

This is a release candidate for a new major version release.

Preliminary release notes for the release can be found here:

https://github.com/bitcoin/bitcoin/blob/0.21/doc/release-notes.md

Release candidates are test versions for releases. When no critical problems
are found, this release candidate will be tagged as 0.21.1.

Please report bugs using the issue tracker at github:

https://github.com/bitcoin/bitcoin/issues

Change log since 0.21.0:

### Consensus
- - #21377 Speedy trial support for versionbits (ajtowns)
- - #21686 Speedy trial activation parameters for Taproot (achow101)

### P2P protocol and network code
- - #20852 allow CSubNet of non-IP networks (vasild)
- - #21043 Avoid UBSan warning in ProcessMessage(…) (practicalswift)

### Wallet
- - #21166 Introduce DeferredSignatureChecker and have SignatureExtractorClass 
subclass it (achow101)
- - #21083 Avoid requesting fee rates multiple times during coin selection 
(achow101)

### RPC and other APIs
- - #21201 Disallow sendtoaddress and sendmany when private keys disabled 
(achow101)

### Build system
- - #21486 link against -lsocket if required for `*ifaddrs` (fanquake)
- - #20983 Fix MSVC build after gui#176 (hebasto)

### Tests and QA
- - #21380 Add fuzzing harness for versionbits (ajtowns)
- - #20812 fuzz: Bump FuzzedDataProvider.h (MarcoFalke)
- - #20740 fuzz: Update FuzzedDataProvider.h from upstream (LLVM) 
(practicalswift)
- - #21446 Update vcpkg checkout commit (sipsorcery)
- - #21397 fuzz: Bump FuzzedDataProvider.h (MarcoFalke)
- - #21081 Fix the unreachable code at `feature_taproot` (brunoerg)
- - #20562 Test that a fully signed tx given to signrawtx is unchanged 
(achow101)
- - #21571 Make sure non-IP peers get discouraged and disconnected (vasild, 
MarcoFalke)
- - #21489 fuzz: cleanups for versionbits fuzzer (ajtowns)

### Miscellaneous
- - #20861 BIP 350: Implement Bech32m and use it for v1+ segwit addresses (sipa)

### Documentation
- - #21384 add signet to bitcoin.conf documentation (jonatack)
- - #21342 Remove outdated comment (hebasto)
-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAmB9C+4ACgkQHkrtYphs
0l37kAf/e+u2+JPkiBsqrRZdyn78be2FAGeOoZvYmiYRK9rlp+PR33+XVGL2hONr
HgHEIxs/mYRX0dBuVL62cSltznhJrbkwUewCGfjT7YYHETrZGauLd7qnHpV1F2r1
m/UUh5F6klyaA0fXp6ZqETJzrknmMDzRV1/KcdnCDs3aoqHXANwwlbzM4wfNXLfi
LjA9U53wTka9wRcMNFqDqFET3Bt1gztKu6Mg+nIQe3O1sDls1npizEHkGhrxAilD
FmXuzgVw6FoZhDHmS/9yL55SMPKGz5u4Z8GW5RkQ5qjlBmqBgb2s4ZQ6IqrNeUbS
CXelKM0Mp2Vw0VUZAyPlfQH55tsVuQ==
=qk4A
-END PGP SIGNATURE-

___
bitcoin-core-dev mailing list
bitcoin-core-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev