<bitcoin-git>
bitcoin/master 24f93c9 Pol Espinasa: release note
2026-02-18
<bitcoin-git>
[bitcoin] achow101 opened pull request #34619: sqlite: Delete wallet.dat-journal on database close (master...restorewallet-rm-journal) https://github.com/bitcoin/bitcoin/pull/34619
<bitcoin-git>
[bitcoin] sipa closed pull request #34138: Cluster mempool: more accurate cost model for SFL (master...202512_sfl_costs) https://github.com/bitcoin/bitcoin/pull/34138
<bitcoin-git>
[bitcoin] achow101 opened pull request #34603: wallet: Fix detection of symlinks on Windows (master...fix-listwallet-recursion-detect-symlinks) https://github.com/bitcoin/bitcoin/pull/34603
2026-02-16
<bitcoin-git>
[bitcoin] brunoerg opened pull request #34602: test: addrman: successive failures in the last week for IsTerrible (master...2026-02-test-addrman-isterrible) https://github.com/bitcoin/bitcoin/pull/34602
<bitcoin-git>
[bitcoin] embetrix opened pull request #34600: security: Replace memset with memory_cleanse for sensitive data clearing (master...feature/secure-erase-keys) https://github.com/bitcoin/bitcoin/pull/34600
<bitcoin-git>
[bitcoin] hebasto merged pull request #34570: doc: update Windows MSVC build guide to utilize winget to install build requirements (master...windows-msvc-update) https://github.com/bitcoin/bitcoin/pull/34570
<bitcoin-git>
[bitcoin] b-l-u-e opened pull request #34593: fuzz: expand script verification flag testing to segwit v0 and tapscript (master...fuzz-script-flags-segwit-tapscript) https://github.com/bitcoin/bitcoin/pull/34593
<Satoshi-2008-10->
{Repetition from #bitcoin channel, just in case the odds somebody reads this are increased.}
<Satoshi-2008-10->
Would it be possible to provide in the "Download" section of Bitcoin Core website, a secure version of bfgminer for download?
<bitcoin-git>
[bitcoin] andrewtoth reopened pull request #34165: coins: don't mutate main cache when connecting block (master...dont-mutate-cache) https://github.com/bitcoin/bitcoin/pull/34165
<bitcoin-git>
[bitcoin] andrewtoth closed pull request #34165: coins: don't mutate main cache when connecting block (master...dont-mutate-cache) https://github.com/bitcoin/bitcoin/pull/34165
<bitcoin-git>
[bitcoin] polespinasa opened pull request #34580: build: Add a compiler minimum version check (master...clang_min_version_check) https://github.com/bitcoin/bitcoin/pull/34580
<bitcoin-git>
[bitcoin] fanquake merged pull request #34511: test: fully reset the state of CConnman in tests (master...test_reset_connman_pb) https://github.com/bitcoin/bitcoin/pull/34511
<bitcoin-git>
bitcoin/master 2cb7e99 Vasil Dimov: test: also reset CConnman::m_private_broadcast in tests
<bitcoin-git>
bitcoin/master 84e826d merge-script: Merge bitcoin/bitcoin#34511: test: fully reset the state of CConnman in te...
<sedited>
it was brought up in the meeting, but might bear repeating since the meeting was quite busy: Feature freeze is in seven days per the release schedule: https://github.com/bitcoin/bitcoin/issues/33607
<_aj_>
(a) don't run your wallet on a mixed-use system; (b) bundle a dedicated broweser engine with the app; (c) use a dedicated browser for interfacing with bitcoin; (d) use a dedicated wallet gui like sparrow for the wallet, and use the bitcoin gui for managing the node; (e) rely on XSS/etc protections -- if your system as a whole is compromised, you're screwed no matter what anyway
<darosior4>
Given who we'd care about supporting (afaiu) are users with private key enabled Bitcoin Core wallets, on the contrary that seems to be an unnecessary increase in the attack surface compared to a standalone software?
<bitcoin-git>
[bitcoin] furszy opened pull request #34577: http: fix submission during shutdown race (master...2026_http_submission_error) https://github.com/bitcoin/bitcoin/pull/34577
<hodlinator>
Sjors[m]1 & fjahr: I can really see the appeal to devs of doing the official GUI in Rust. Again, I'm concerned about duplicating effort with BDK or using the actual BDK / rust bitcoin and running into a bunch of inconsistencies. But it might be worth the mess in order to get real traction. Time to fork Liana. ;)
<sipa>
If the goal is not that, but "providing non-technical users with a GUI to manage their BTC backed by Bitcoin Core", just use Sparrow?
<darosior4>
It is indeed a separate discussion, because the argument of keeping the Bitcoin Core GUI as the sole accessible way of using the Bitcoin network has not much to it, and now the real remaining question is: quid of existing users of the Bitcoin Core wallet?
<sipa>
My concern w.r.t. deprecating the GUI is that it leaves people who _want to use the Bitcoin Core wallet_, for whatever reason - without a migration path.
<darosior4>
sipa: i don't think this is irrelevant to the discussion, because one way people have discussed this topic in the past is the intention behind the Bitcoin Core GUI is to "make Bitcoin accessible to non-technical users". You go to bitcoincore.org, download bitcoin, run bitcoin and it just works without moving parts. However i don't think this
<darosior4>
position is really compelling anymore in 2026, and i think what you point to is the real important part of the discussion. But the fact that there exists other simple ways (really, superior ways) of using Bitcoin (as in having a wallet) backed by a Bitcoin Core full node is not irrelevant to this discussion.
<sipa>
it's a separate wallet, not a GUI for the Bitcoin Core wallet
<darosior4>
Some migration paths were discussed, but i don't think there is anything that could be reasonably considered a "recommended migration path out of Bitcoin Core"
<sipa>
and it's not something a bitcoin core wallet.dat file could be converted/migrated to
<sipa>
it's not something you can use to manage an existing bitcoin core wallet.dat file, i believe?
<sipa>
darosior4: i'm not very familiar with sparrow, but from what i understand, i would call it a separatey wallet - which happens to delegate some tasks to a bitcoin core wallet which it uses in a limited manner
<sipa>
i feel like we're missing a distinction between "a GUI that is a wallet" and "a GUI to control the Bitcoin Core wallet"
<darosior4>
sipa: To eliminate those cases of people merely using watchonly wallet, would you think it's fair to reduce the scope to "being able to use/manage a Bitcoin Core hot wallet"?
<darosior4>
I think the line is blurry because common other wallet software use a Bitcoin Core watchonly wallet in the background, but i agree backward-compatibility with the Bitcoin Core wallet format is the actual torny issue here.
<sipa>
darosior4: being able to use/manage a Bitcoin Core wallet
<darosior4>
sipa: what is the expectation for a Bitcoin Core GUI other than being able to use Bitcoin through a graphical user interface?
<darosior4>
Liana is an example using the Bitcoin Core wallet, Sparrow is an example using a separate wallet but a direct RPC connection, virtually any other wallet in common use today is an example using an Electrum server as middleware (sometimes even locally, see for instance BWT).
<sipa>
if you're referring to other *wallets* that use RPC to communicate with Bitcoin Core, which include their own GUI, that's not a fair comparison i think
<sipa>
(or any non-Bitcoin-Core GUIs at all, for that matter)
<sipa>
darosior4: i wasn't aware that any RPC-based GUIs for the Bitcoin Core wallet existed?
<darosior4>
how Bitcoin is actually being used today. Better, less laggy, GUIs than the Bitcoin Core GUI exist today that use RPC! This is incredibly disingenuous to try and claim otherwise.
<bitcoin-git>
[qa-assets] murchandamus opened pull request #255: Add initial corpus for bnb_finds_min_waste (main...2026-02-initial-bnb_finds_min_waste) https://github.com/bitcoin-core/qa-assets/pull/255
<fjahr>
hodlinator: it was tongue in cheek of course but it would attract contributors. That doesn't mean it would give up the goal of the bitcoin core project to keep dependencies to a minimum if that were to be seriously considered.
<hodlinator>
(not sure if it was a serious suggestion, but starting to mix in Rust for the GUI would risk eventually leading to a Frankenstein monster with BDK and Bitcoin Core Kernel dependencies both pulled in and duplicating functionality in incompatible ways, or building/maintaining our own Rust-Bitcoin-Core lib).
<achow101>
as long as others are okay with us shipping it under the bitcoin core banner
<pinheadmz_>
the qml ui looks slick and modern, i think it is something bitcoin should have
<achow101>
of the 387 people who responded to the question "how did you previously use Bitcoin Core?", 246 responded "the GUI"
<achow101>
of the 342 people who responded to the question "How do you currently use Bitcoin Core?", 176 of them said "the GUI"
<achow101>
pinheadmz_: here's data from the survey I ran 5 years ago, never really processed it to the point that something could be written up, but there were questiosn about how users use Bitcoin Core https://github.com/achow101/2021-core-survey/
<sipa>
agreed, achow101; and importantly: there is no way to convert/import/load Bitcoin Core wallets into them - they have an entirely different idea of what a wallet is, so that's no viable migration path for current GUI wallet users
<pinheadmz_>
boy it sure would be great is we knew any users wanted a bitcoin core gui
<johnny9dev>
To the point of bitcoin-core/gui being not create. I still don't actually know the relationship between bitcoin-core/gui and bitcoin/bitcoin. I've been on the edge but I think it probably be obvious to someone like me by now.
<dergoegge>
achow101 fjahr: they've managed to download and run bitcoin-qt I think they'll be fine. Seems like very paternalistic thinking. They might also (more likely) find a better alternative
<pinheadmz_>
i just wanted to stop core codebase changes in the qml repo, so forcing bitcoin as a subtree
<sipa>
hebasto: i don't think the dependencies problem is core to the issue here; we can move towards a more-static-linked binary for bitcoind, and simultaneously toward a more runtime-dependency rich bitcoin-qt binary... because GUI users naturally depend on more dependencies (no pun intended)
<BlueMatt[m]>
if bitcoin core is gonna ship a wallet, it seems reasonable that it should also ship a gui to access that wallet
<BlueMatt[m]>
@libera_irc_pinheadmz_:bitcoin.ninja i mean, i think the gui is great to have, but also i dont really have an opinion that counts here cause I don't work on core
<bitcoin-git>
[bitcoin] maflcko opened pull request #34575: test: Avoid empty errmsg in JSONRPCException (master...2602-test-proper-JSONRPCException-error) https://github.com/bitcoin/bitcoin/pull/34575
<pinheadmz_>
furszy i suggested that before, no one wants to track bitcoin users tho
<hebasto>
the problem with Bitcoin Core GUI has been known for quite a long time, and this attempt to find a solution isn't the first.
<bitcoin-git>
[bitcoin] m3dwards closed pull request #32672: ci: update pwsh to use custom shell that fails-fast (master...250603-pwsh-fail-fast) https://github.com/bitcoin/bitcoin/pull/32672
<bitcoin-git>
[bitcoin] hebasto opened pull request #34572: cmake: Fix NetBSD-specific workaround for Boost (master...260212-netbsd-boost) https://github.com/bitcoin/bitcoin/pull/34572
<bitcoin-git>
[bitcoin] DrahtBot reopened pull request #27052: test: rpc: add last block announcement time to getpeerinfo result (master...2023-02-getpeerinfo) https://github.com/bitcoin/bitcoin/pull/27052
<bitcoin-git>
[bitcoin] DrahtBot reopened pull request #34075: fees: Introduce Mempool Based Fee Estimation to reduce overestimation (master...12-2025-fee-estimation-improvement) https://github.com/bitcoin/bitcoin/pull/34075
<bitcoin-git>
[bitcoin] DrahtBot closed pull request #27052: test: rpc: add last block announcement time to getpeerinfo result (master...2023-02-getpeerinfo) https://github.com/bitcoin/bitcoin/pull/27052
<bitcoin-git>
[bitcoin] DrahtBot closed pull request #34075: fees: Introduce Mempool Based Fee Estimation to reduce overestimation (master...12-2025-fee-estimation-improvement) https://github.com/bitcoin/bitcoin/pull/34075
<bitcoin-git>
[bitcoin] maflcko reopened pull request #34544: wallet: Disallow wallet names that are paths including `..` and `.` elements (master...wallet-no-relative-paths) https://github.com/bitcoin/bitcoin/pull/34544
<bitcoin-git>
[bitcoin] maflcko closed pull request #34544: wallet: Disallow wallet names that are paths including `..` and `.` elements (master...wallet-no-relative-paths) https://github.com/bitcoin/bitcoin/pull/34544
<bitcoin-git>
[bitcoin] maflcko opened pull request #34571: test: Fix intermittent issues in feature_assumevalid.py (master...2602-test-av-int-fail) https://github.com/bitcoin/bitcoin/pull/34571
<bitcoin-git>
[bitcoin] janb84 opened pull request #34570: doc: update Windows MSVC build guide to utilize winget to install build requirements (master...windows-msvc-update) https://github.com/bitcoin/bitcoin/pull/34570
<bitcoin-git>
[bitcoin] w0xlt opened pull request #34565: refactor: extract BlockDownloadManager from PeerManagerImpl (master...refactor/extract-block-download-manager) https://github.com/bitcoin/bitcoin/pull/34565
<bitcoin-git>
[bitcoin] melvincarvalho opened pull request #34564: COPYING: Correct start date for "The Bitcoin Core developers" copyright line (master...fix-copyright-date) https://github.com/bitcoin/bitcoin/pull/34564
<bitcoin-git>
[bitcoin] furszy opened pull request #34562: ThreadPool follow-ups, proactive shutdown and HasReason dependency cleanup (master...2026_threadpool_follow_ups) https://github.com/bitcoin/bitcoin/pull/34562
<bitcoin-git>
[bitcoin] fanquake merged pull request #34143: build: Prevent system header fallback and include path pollution (master...251223-boost-layout) https://github.com/bitcoin/bitcoin/pull/34143
<bitcoin-git>
bitcoin/master b5375c4 Hennadii Stepanov: depends: Prefix include path for headers-only `boost` package