public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: fanquake <fanquake@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Bitcoin Core v31.1 Released
Date: Wed, 8 Jul 2026 07:49:43 -0700 (PDT)	[thread overview]
Message-ID: <84e1ccd0-9a43-4600-b8b3-a0605bb4cac6n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4280 bytes --]

Bitcoin Core version 31.1 is now available from:

  <https://bitcoincore.org/bin/bitcoin-core-31.1/>

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 tested on the following operating systems or
newer: Linux Kernel 3.17, macOS 14, and Windows 10 (version 1903). 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
===============

This release fixes an issue where the chainstate database would repeatedly
rewrite large portions of itself, causing excessive disk reads and writes
during normal operation.

### PrivateBroadcast

This release fixes an ip address leak when using the -privatebroadcast 
feature.
Under certain circumstances connections were being made over clearnet 
rather than
the enabled privacy network.


### Validation

- #35209 validation: correct lifetime of precomputed tx data
- #35465 coins: compact chainstate regularly

### Leveldb

- #61(bitcoin-core/leveldb): Disable seek compaction

### P2P

- #35032 net_processing: don't modify addrman for private broadcast 
connections
- #35410 net: use the proxy if overriden when doing v2->v1 reconnections

### Wallet

- #35227 wallet: check the final BDB page LSN during migration
- #35228 wallet: use outpoint when estimating input size

### Musig

- #35316 musig: Reject empty pubkey list in GetMuSig2KeyAggCache

### Build

- #34228 depends: Unset SOURCE_DATE_EPOCH in gen_id script

### Test

- #34425 test: Fix all races after a socket is closed gracefully
- #34863 test: Clean shutdown in Socks5Server
- #34991 test: fix feature_index_prune.py bug when using --usecli
- #35080 test: Add missing self.options.timeout_factor scale in 
tool_bitcoin_chainstate.py
- #35218 test: fix P2SH script in coins cache fuzz target
- #35279 psbt, test: remove address type restrictions in test

### Fuzz

- #35289 fuzz: Fix timeout in txorphan

### Util

- #35384 util: Check write failures before renaming settings.json

### Docs

- #35283 doc: mention -DWITH_ZMQ=ON in BSD build guides

### CI

- #35202 ci: restore sockets in i686, no IPC job
- #35230 ci: Move --usecli --extended from i386 task to alpine task
- #35348 ci: switch to GitHub cache for all runners
- #35378 ci: switch runners from cirrus to warpbuild
- #35408 ci: 35378 followups
- #35430 ci: use warp caching on warp runners
- #35447 ci: use warpbuild cache for docker buildkit cache

### Misc

- #35044 contrib: Fix NameError in signet miner gbt()
- #35175 multi_index: fix compilation failure with boost >= 1.91
- #34953 crypto: disable ASan instrumentation of SSE4 SHA256 for GCC

Credits
=======

Thanks to everyone who directly contributed to this release:

- andrewtoth
- Cory Fields
- Crypt-iQ
- darosior
- deadmanoz
- fanquake
- Greg Sanders
- Hennadii Stepanov
- junbyjun1238
- Lőrinc
- MarcoFalke
- marcofleon

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/84e1ccd0-9a43-4600-b8b3-a0605bb4cac6n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 5062 bytes --]

                 reply	other threads:[~2026-07-08 14:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84e1ccd0-9a43-4600-b8b3-a0605bb4cac6n@googlegroups.com \
    --to=fanquake@gmail.com \
    --cc=bitcoindev@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox