<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] 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 df9ebbf fanquake: depends: use "mkdir -p" when installing xproto
<bitcoin-git>
bitcoin/master a980918 merge-script: Merge bitcoin/bitcoin#32568: 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>
gui-qml/main 7c8a68c goqusan: qml: Fix layout in activity view
<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 b933813 merge-script: Merge bitcoin/bitcoin#32619: wallet, rpc, gui: List legacy wallets with a ...
<bitcoin-git>
bitcoin/master f3a444c Ava Chow: gui: Disallow loading legacy wallets
<bitcoin-git>
bitcoin/master 0995517 Ava Chow: wallet, rpc: Give warning in listwalletdir for legacy wallets
<bitcoin-git>
bitcoin/master 5471e29 Ava Chow: Merge bitcoin/bitcoin#32304: test: test MAX_SCRIPT_SIZE for block validity
<_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>
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.
<johnny9dev>
I also undrafted the multiple recipients PR as the core functionality is working now (bitcoin-core/gui-qml#450)
<bitcoin-git>
[bitcoin] l0rinc opened pull request #32638: blocks: force hash validations of blocks read from disk explicit (master...l0rinc/read-block-hash-check) https://github.com/bitcoin/bitcoin/pull/32638
<bitcoin-git>
[bitcoin] fanquake merged pull request #32634: build: Add resource file and manifest to `bitcoin.exe` (master...250528-bitcoin-rc) https://github.com/bitcoin/bitcoin/pull/32634
<bitcoin-git>
[bitcoin] davidgumberg opened pull request #32636: Split `CWallet::Create()` into `CreateNew` and `LoadExisting` (master...5-27-2025-create-refactor) https://github.com/bitcoin/bitcoin/pull/32636
<bitcoin-git>
[bitcoin] hebasto opened pull request #32634: build: Add resource file and manifest to `bitcoin.exe` (master...250528-bitcoin-rc) https://github.com/bitcoin/bitcoin/pull/32634
<bitcoin-git>
[bitcoin] hebasto opened pull request #32633: windows: Use predefined `RC_INVOKED` macro instead of custom one (master...250528-rc-invoked) https://github.com/bitcoin/bitcoin/pull/32633
<bitcoin-git>
[bitcoin] brunoerg opened 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] marcofleon opened pull request #32631: refactor: Convert GenTxid to `std::variant` (master...2025/05/gentxid-variant) https://github.com/bitcoin/bitcoin/pull/32631
<bitcoin-git>
[bitcoin] theStack opened pull request #32621: contrib: utxo_to_sqlite.py: add option to store txid/spk as BLOBs (master...202505-utxo-to-sqlite_blobs) https://github.com/bitcoin/bitcoin/pull/32621
2025-05-26
<gmaxwell>
I'm pretty sure I lost a few bitcoin a decade ago by BDB just deciding to strip everything out of some corrupted file.
<phantomcircuit>
gmaxwell: bdb will write log files into the ~/.bitcoin directory, if you happen to copy the .dat file when it's doing that you'll get corruption that's fixable with db_dump -R, but which iirc basically deletes records until the database is consistent
<bitcoin-git>
[gui] achow101 opened pull request #877: gui: Add a menu action to restore then migrate a legacy wallet (master...gui-migrate-path) https://github.com/bitcoin-core/gui/pull/877
<gmaxwell>
I'm finding now that good brand sata/nvme SSDs that sat in a closet for 5 years are full of errors, so I assume this also means a lot of earlier bitcoin users might be finding their older wallets harder to recover.
<bitcoin-git>
[bitcoin] achow101 opened pull request #32620: wallet: Fix wallet interface detection of encrypted wallets (master...fix-gui-migrate-encrypted) https://github.com/bitcoin/bitcoin/pull/32620
<gmaxwell>
but it also only outputs a legacy wallet, which doesn't directly work with bitcoin core anymore.
<bitcoin-git>
[bitcoin] achow101 opened 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] achow101 opened pull request #32618: wallet: Remove ISMINE_WATCHONLY and watchonly from RPCs (master...delete-ismine-watchonly) https://github.com/bitcoin/bitcoin/pull/32618
<bitcoin-git>
[bitcoin] w0xlt opened pull request #32617: [Draft/POC] Add secp256k1-based HPKE (Hybrid Public Key Encryption) For Payjoin v2 (master...secp256k1_hpke) https://github.com/bitcoin/bitcoin/pull/32617
2025-05-25
<bitcoin-git>
[bitcoin] tnndbtc opened pull request #32615: fee estimate test: fix #31944 by handling a legitimate scenario that … (master...fix-fee-estimation-test) https://github.com/bitcoin/bitcoin/pull/32615
<Krellan>
smart, that makes more sense then, settings.json dynamically written, bitcoin.conf static as written by user
<dzxzg>
*user configuration in bitcoin.conf
<dzxzg>
settings.json is a file that is read from and written into at runtime by bitcoin Core, and is modified by using the GUI and some RPC's, overwriting user configuration files in bitcoin.conf would not have been a good solution, you can read more about the tradeoffs behind the design of settings.json here: https://github.com/bitcoin/bitcoin/pull/15935#issuecomment-490641194
<Krellan>
i will try that, removing it from settings.json (why is there a settings.json anyway when there's a bitcoin.conf)
<Krellan>
I tried making a directory and copying the wallet.dat file in manually. That just gave me an error upon starting bitcoin again: the wallet was in legacy format which is no longer allowed, then it exited before giving me the chance to migrate it.
<Krellan>
Thanks. How does "Migrate wallet" populate the list? I thought it was just subdirectories in the bitcoin datadir. It doesn't appear in "Open wallet" either, it's a loose file I have.
<bitcoin-git>
[bitcoin] benthecarman opened pull request #32607: rpc: Note in fundrawtransaction doc, fee rate is for package (master...fundawtx-pkg-doc) https://github.com/bitcoin/bitcoin/pull/32607
<bitcoin-git>
[bitcoin] davidgumberg opened pull request #32606: p2p: Drop unsolicited CMPCTBLOCK from non-HB peer (master...5-23-25-ignore-unsolicited) https://github.com/bitcoin/bitcoin/pull/32606
<bitcoin-git>
[bitcoin] Crypt-iQ opened pull request #32604: log: Mitigate disk filling attacks by rate limiting LogPrintf, LogInfo, LogWarning, LogError (master...log_ratelimiting_05192025) https://github.com/bitcoin/bitcoin/pull/32604
<bitcoin-git>
[bitcoin] achow101 merged pull request #32596: wallet, rpc, doc: various legacy wallet removal cleanups in RPCs (master...2025-wallet-rpc-related_legacy_wallet_cleanups) https://github.com/bitcoin/bitcoin/pull/32596
<bitcoin-git>
bitcoin/master db465a5 Sebastian Falbesoner: wallet, rpc: remove obsolete "keypoololdest" result field/code
<bitcoin-git>
bitcoin/master e5cbea4 Sebastian Falbesoner: rpc: doc: remove redundant "descriptors" parameter in `createwallet` examp...
<bitcoin-git>
bitcoin/master 7a05f94 Sebastian Falbesoner: rpc: doc: drop descriptor wallet mentions in fast wallet rescan related RP...
<bitcoin-git>
[bitcoin] mzumsande closed pull request #31714: validation: Do less work in NeedsRedownload (master...202501_simpler_segwit_check) https://github.com/bitcoin/bitcoin/pull/31714
<bitcoin-git>
[bitcoin] hebasto reopened pull request #32577: subprocess: Let shell parse command on non-Windows systems (master...250521-subprocess-split) https://github.com/bitcoin/bitcoin/pull/32577