<bitcoin-git>
[bitcoin] maflcko opened pull request #32697: test: Turn util/test_runner into functional test (master...2506-test-move) https://github.com/bitcoin/bitcoin/pull/32697
<bitcoin-git>
[bitcoin] luisschwab opened pull request #32696: doc: make `-DWITH_ZMQ=ON` explicit on `build-unix.md` (master...doc/add-zmq-flag-requirement) https://github.com/bitcoin/bitcoin/pull/32696
<bitcoin-git>
[bitcoin] achow101 merged pull request #32539: init: Configure reachable networks before we start the RPC server (master...rpcallowip-rfc4193) https://github.com/bitcoin/bitcoin/pull/32539
<bitcoin-git>
bitcoin/master 12ff4be Matthew Zipkin: test: ensure -rpcallowip is compatible with RFC4193
<bitcoin-git>
bitcoin/master c02bd3c Matthew Zipkin: config: Explain RFC4193 and CJDNS interaction in help and init error
<bitcoin-git>
bitcoin/master f728b6b Matthew Zipkin: init: Configure reachable networks before we start the RPC server
<bitcoin-git>
[bitcoin] furszy opened pull request #32694: index: move disk read lookups to base class (master...2025_indexes_remove_CBlockIndex_access) https://github.com/bitcoin/bitcoin/pull/32694
<bitcoin-git>
[bitcoin] josibake opened pull request #32693: depends: fix cmake compatibility error for freetype (master...depends-specify-cmake-min-version-for-freetype) https://github.com/bitcoin/bitcoin/pull/32693
<bitcoin-git>
[gui-qml] hebasto merged pull request #466: Visual tweaks to the fee selector in the send form (main...feature/fee-selection-visual-tweaks) https://github.com/bitcoin-core/gui-qml/pull/466
<bitcoin-git>
gui-qml/main c767837 Hennadii Stepanov: Merge bitcoin-core/gui-qml#466: Visual tweaks to the fee selector in the s...
<bitcoin-git>
gui-qml/main e06c32a GBKS: Visual tweaks to the fee selector in the send form
<hacker4web3bitco>
Hi, ask a question, why does bitcoin core limit MAX_SCRIPTCHECK_THREADS to 15, shouldn't it be something like nr_cpu_cores-1?
<bitcoin-git>
[gui-qml] hebasto merged pull request #465: Show "Select Wallet" or "Add Wallet" in the Wallet selector if a wallet isn't loaded (main...no-wallets-loaded) https://github.com/bitcoin-core/gui-qml/pull/465
<bitcoin-git>
gui-qml/main 03b568d johnny9: qml: Add Context to CreateWalletWizard
<bitcoin-git>
gui-qml/main 5b9b484 johnny9: qml: Show Add Wallet in WalletBadge if none are found
<bitcoin-git>
gui-qml/main 7af55d5 johnny9: qml: Hide tabs and show Select Wallet if no wallet is loaded
<bitcoin-git>
[bitcoin] PeterWrighten opened pull request #32685: wallet: Allow read-only database access for info and dump commands (master...wallet-readonly-access) https://github.com/bitcoin/bitcoin/pull/32685
<bitcoin-git>
qa-assets/main ef94b3a maflcko: Merge pull request #226 from marcofleon/coins-view-db-inputs
<corebot>
https://github.com/bitcoin-core/gui-qml/issues/465 | Show "Select Wallet" or "Add Wallet" in the Wallet selector if a wallet isn't loaded by johnny9 · Pull Request #465 · bitcoin-core/gui-qml · GitHub
<johnny9dev>
RequestPayment page has finally been hooked up to our wallet model to generate and commit actual payment requests and addresses. bitcoin-core/gui-qml#464
<johnny9dev>
First set of form input validation for Send has been PR'd. This will also be used for payment requests. bitcoin-core/gui-qml#462
<johnny9dev>
Standard fee selection control was added to Send to set very basic (low/default/high) block-based fees. This has been merged bitcoin-core/gui-qml#461
<johnny9dev>
Multiple Recipients in the Send form has been PR'd and close to being merged bitcoin-core/gui-qml#450
<johnny9dev>
Some cleanup to our layouts are being done by goqusan bitcoin-core/gui-qml#463. He's been working through what we have and fixing up messy anchors and layouts and his reviews have helped give clarity on getting the layouts where they need to be
<johnny9dev>
Addtional init loading animations were merged in bitcoin-core/gui-qml#460
<bitcoin-git>
[bitcoin] fanquake merged pull request #32679: doc: update tor docs to use bitcoind binary from path (master...06-2025-fix-tor-docs) https://github.com/bitcoin/bitcoin/pull/32679
<bitcoin-git>
bitcoin/master 6a2ff67 merge-script: Merge bitcoin/bitcoin#32679: doc: update tor docs to use bitcoind binary f...
<bitcoin-git>
bitcoin/master 4ce5349 ismaelsadeeq: doc: update tor docs to use bitcoind binary from path
<bitcoin-git>
[gui-qml] GBKS opened pull request #466: Visual tweaks to the fee selector in the send form (main...feature/fee-selection-visual-tweaks) https://github.com/bitcoin-core/gui-qml/pull/466
<bitcoin-git>
[bitcoin] maflcko opened pull request #32680: ci: Rewrite test-each-commit as rust script (master...2506-ci-rust-script) https://github.com/bitcoin/bitcoin/pull/32680
<bitcoin-git>
[gui-qml] johnny9 opened pull request #465: Show "Select Wallet" or "Add Wallet" in the Wallet selector if a wallet isn't loaded (main...no-wallets-loaded) https://github.com/bitcoin-core/gui-qml/pull/465
2025-06-04
<bitcoin-git>
[bitcoin] achow101 merged pull request #32676: test: apply microsecond precision to test framework logging (master...202506_test_log_micros) https://github.com/bitcoin/bitcoin/pull/32676
<bitcoin-git>
bitcoin/master ed179e0 Martin Zumsande: test: apply microsecond precision to test framework logging
<bitcoin-git>
bitcoin/master f941675 Ava Chow: Merge bitcoin/bitcoin#32676: test: apply microsecond precision to test fra...
<bitcoin-git>
[bitcoin] brunoerg closed pull request #32632: wallet: sqlite: there is no need to have exclusive locking when mocking (master...2025-05-wallet-sqlite) https://github.com/bitcoin/bitcoin/pull/32632
<bitcoin-git>
[bitcoin] ismaelsadeeq opened pull request #32679: doc: update tor docs to use correct bitcoind binary path (master...06-2025-fix-tor-docs) https://github.com/bitcoin/bitcoin/pull/32679
<bitcoin-git>
[bitcoin] willcl-ark opened pull request #32678: guix: warn and abort when SOURCE_DATE_EPOCH is set (master...source-date-epoch) https://github.com/bitcoin/bitcoin/pull/32678
<PaperSword>
_aj_: Seems like it's good for same network, but what I need is to run a bitcoin node on mainnet, run address decoding checks, then do the same for a test network
<PaperSword>
How would one switch the networks of a Bitcoin node in the function testing framework? Example I need some test vectors that are network specific.
2025-06-03
<bitcoin-git>
[bitcoin] fanquake merged pull request #32568: depends: use "mkdir -p" when installing xproto (master...alpine_MKDIRPROG) https://github.com/bitcoin/bitcoin/pull/32568
<bitcoin-git>
bitcoin/master a980918 merge-script: Merge bitcoin/bitcoin#32568: depends: use "mkdir -p" when installing xproto
<bitcoin-git>
bitcoin/master df9ebbf fanquake: depends: use "mkdir -p" when installing xproto
<bitcoin-git>
[bitcoin] m3dwards opened 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] fanquake closed pull request #30434: depends: bump boost to 1.87.0 and use new CMake buildsystem (master...cmake-boost-depends) https://github.com/bitcoin/bitcoin/pull/30434
<bitcoin-git>
[bitcoin] fanquake opened pull request #32665: depends: Bump boost to 1.88.0 and use new CMake buildsystem (master...boost_shrink) https://github.com/bitcoin/bitcoin/pull/32665
<dviola>
11GB, that's not a lot, I guess the chainstate gets rebuilt every time bitcoin core finishes syncing?
<dviola>
I was pretty impressed when I synced bitcoin core for the first time on a dual core PC (E5500 CPU + 2GB RAM)... I'm still not sure whether the slowdown I experienced was disk related or filesystem related but I did notice some slowdown when having the chainstate on SATA SSD
<Earnestly>
dviola: Fwiw, it'd all just live in a micro form factor pc of some description. bitcoin core doesn't really need much in the ways of specs. I have even sync'd the block chain on an rpi 2b not so long ago, it just takes awhile. (My internet isn't that fast anyway)
<bitcoin-git>
[bitcoin] theStack opened pull request #32645: fs: use `ftruncate` in `AllocateFileRange` on OpenBSD (master...202505-fs-use_ftruncate_on_openbsd) https://github.com/bitcoin/bitcoin/pull/32645
<bitcoin-git>
[bitcoin] fanquake merged pull request #32619: wallet, rpc, gui: List legacy wallets with a message about migration (master...dont-list-legacy-wallets) https://github.com/bitcoin/bitcoin/pull/32619
<bitcoin-git>
bitcoin/master f3a444c Ava Chow: gui: Disallow loading legacy wallets
<bitcoin-git>
bitcoin/master b933813 merge-script: Merge bitcoin/bitcoin#32619: wallet, rpc, gui: List legacy wallets with a ...
<bitcoin-git>
bitcoin/master 0995517 Ava Chow: wallet, rpc: Give warning in listwalletdir for legacy wallets
<_aj_>
sipa: i thought we were going for X is the year of a bitcoin full node on your phone?
<sipa>
2025 will the year of Bitcoin on the desktop
<gmaxwell>
Earnestly: It should just be wiped with a "go over here" pointer on it, I think. Bitcoin isn't the kind of obscure project dying for the last possible user that it matters if someone gets lost on the way.
<gmaxwell>
I hope bitcoin core gets off of it some day.
<gmaxwell>
When people in those PRs who *might* have been otherwise seen as brigading actually argued their points, they got reasoned replies. E.g. https://github.com/bitcoin/bitcoin/pull/32406#issuecomment-2874791860 in my comment on instagibbs PR I took the time to specifically respond to points of k98kurz, who is someone I've never seen before, and might have guessed was there only due to being
<gmaxwell>
If someone reads the realy policy thing, understands it, and disagrees with it-- well then thats a fine reason for them to just not us bitcoin core as it's being designed/maintained with values in mind that they don't agree with.
<bitcoin-git>
[bitcoin] ryanofsky opened pull request #32641: Update libmultiprocess subtree to fix clang-tidy errors (master...pr/subtree-2) https://github.com/bitcoin/bitcoin/pull/32641
<gmaxwell>
dzxzg: it's also a big time and energy saver ultimately, like no need to have a quarterly useless debate PR by PR over questions that are answered by the policy doc. Which makes it easier to actually set a forward direction. E.g. project collectively has a vision for the kind of bitcoin its building for. I mean I think it always has, but it's not always well communicated.
<dzxzg>
Why does every last person need to be convinced? At the extreme end, the brigadiers are not hearing any one out in good faith, and the majority in the middle are probably just gawking at the spectacle. I think it would be more productive to spend resources/time communicating a positive vision(s) of the future of Bitcoin Core (Kernel, Erlay, Multiprocess, Cluster mempool, Stratum V2, Package Relay, etc. etc.) instead of trying to put out fires started
<dzxzg>
Why does every last person need to be convinced? At the extreme end, the brigadiers are not sincerely interested in changing their minds, and the majority in the middle are probably just gawking at the spectacle. I think it would be more productive to spend resources/time communicating a positive vision of the future of Bitcoin Core instead of trying to put out fires by people that are started by people that just want to throw sand into gears
<johnny9dev>
I also undrafted the multiple recipients PR as the core functionality is working now (bitcoin-core/gui-qml#450)
<johnny9dev>
Since last meeting, The QR code component was merged in bitcoin-core/gui-qml#454, Initial loading animations were merged in (bitcoin-core/gui-qml#455 and bitcoin-core/gui-qml#459), and a minor compile error fixed bitcoin-core/gui-qml#458.