<bitcoin-git>
[bitcoin] theStack opened pull request #32415: scripted-diff: adapt script error constant names in feature_taproot.py (master...202505-test-adapt_consensus_error_constants) https://github.com/bitcoin/bitcoin/pull/32415
<bitcoin-git>
[bitcoin] andrewtoth opened pull request #32414: validation: periodically flush dbcache during reindex-chainstate (master...reindex-flush) https://github.com/bitcoin/bitcoin/pull/32414
<bitcoin-git>
[bitcoin] rkrux opened pull request #32413: test: test that descriptorprocesspsbt removes non witness utxos in PSBT (master...descriptorprocesspsbt) https://github.com/bitcoin/bitcoin/pull/32413
<vasild>
yeah, I was just thinking about that - if Bitcoin Core is a typical software project, then its developers are dictators and do as they see fit. Disagreeing people are free to fork it and change it according to their taste.
<bitcoin-git>
[bitcoin] davidgumberg opened pull request #32400: random: Use modern Windows randomness functions (master...5-1-25-winbcrypt) https://github.com/bitcoin/bitcoin/pull/32400
2025-05-01
<badkat>
can anybody guide me to get into bitcoin network again? my last interaction to this blockchain was in 2013
<bitcoin-git>
[bitcoin] Brotcrunsher opened pull request #32397: doc: Add hint about avoiding spaces in paths when building on Windows (master...HintNoSpace) https://github.com/bitcoin/bitcoin/pull/32397
<BlueMatt[m]>
Murch[m]: sure, if you want someone who doenst work on bitcoin core i can :)
<BlueMatt[m]>
yea, letting this slip into the next release is really not okay, there's very nontrivial cost to the bitcoin system
<Sjors[m]>
And more practically, it means several rounds of bitcoin podcasts can go through the issue and hopefully convince more people.
<jonatack>
lightlike: i think the process hasn't helped in this case, as willcl-ark wrote in bitcoin/meta a couple hours ago
<Murch[m]>
pinheadmz: okay sure, but there do seem to be some people here that don’t seem to support dropping the limit, so I’m not sure Bitcoin Core can put out a blog post. Where would this be posted and by whom?
<jonatack>
perhaps consider spending time exlaining the issues involved to the outer community, if perception of bitcoin core is a criteria
<darosior>
Storm in a tea pot. I don't think we should give in to bullies and do what we believe is good for actual Bitcoin Core and Bitcoin network users, ie the silent majority. I think we should merge Todd's PR and call it a day.
<vasild>
I guess the most liberal is to have this configurable in Bitcoin Core so users can set whatever mempool policy they wish. This way Bitcoin Core developers will not be perceived as imposing their views on the node operators.
<jonatack>
I think the BIPs case is separate from the bitcoin core one.
<Murch[m]>
glozow: Yeah, I think the ownership being retained by Bitcoin Core maintainers is understood
<TheCharlatan>
yeah, but you end up with either bitcoin or bitcoin-core on your machine.
<jonatack>
I agree the project owners in bitcoin/ would not need to be changed.
<TheCharlatan>
I'd like to keep /bitcoin. It would also make easier to maintain any existing cloning documentation, i.e. no need to handle the renamed dir.
<laanwj>
bitcoin-core/bitcoin-core sgtm
<achow101>
cfields: I think the general sentiment is that the current owners of bitcoin/ will remain so, and no new ones will be added, regardless of any moves
<stickies-v>
Murch[m]: but the bip editor's can't get ban permissions in the bitcoin org?
<Murch[m]>
Some BIP Editors appear to think that the bitcoin org is the correct place for BIPs while Bitcoin Core should move out. Others seem fine with the move.
<achow101>
TheCharlatan: we can bikeshed that.. I like bitcoin-core/bitcoin-core
<TheCharlatan>
what will be the name of the repo in the bitcoin-core org?
<vasild>
did anything happen with the bip repo in the meantime, e.g. did bip people decide to move it away from bitcoin/bips?
<_aj_>
fanquake: find .bitcoin/blocks/index -printf "%s\n" | (x=0; while read a; do x=$(($x+$a)); done; echo $((x/1024/1024)) )
<bitcoin-git>
[bitcoin] hebasto opened pull request #32396: cmake: Add application manifests when cross-compiling for Windows (master...250501-app-manifest) https://github.com/bitcoin/bitcoin/pull/32396
<bitcoin-git>
[bitcoin] ismaelsadeeq opened pull request #32395: fees: rpc: `estimatesmartfee` now returns a fee rate estimate during low network activity (master...04-2025-fee-estimate-with-low-network-activity) https://github.com/bitcoin/bitcoin/pull/32395
<fjahr>
pinheadmz: Not sure if the ML is the right place for that bitcoin core meta discussion, so writing it here instead: Agree that it would be good to split conceptual and technical review but also skeptical the discussion post would get traction. And even if it did, people could still copy+paste their messages into the PR later.
<bitcoin-git>
[bitcoin] darosior closed pull request #32381: policy: allow more than one OP_RETURN outputs per tx (master...2504_fixthefiltersyo) https://github.com/bitcoin/bitcoin/pull/32381
<bitcoin-git>
[bitcoin] stratospher opened pull request #32385: test: add test for malleated transaction with valid witness (master...2025_04_tx_malleate) https://github.com/bitcoin/bitcoin/pull/32385
<bitcoin-git>
[bitcoin] achow101 merged pull request #32355: Bugfix: Miner: Don't reuse block_reserved_weight for "block is full enough to give up" weight delta (master...fix_block_full_enough) https://github.com/bitcoin/bitcoin/pull/32355
<bitcoin-git>
bitcoin/master 524f981 Luke Dashjr: Bugfix: Miner: Don't reuse block_reserved_weight for "block is full enough...
<bitcoin-git>
[bitcoin] achow101 merged pull request #31014: net: Use GetAdaptersAddresses to get local addresses on Windows (master...2024-10-windows-address-discovery) https://github.com/bitcoin/bitcoin/pull/31014
<bitcoin-git>
bitcoin/master b9d4d5f laanwj: net: Use GetAdaptersAddresses to get local addresses on Windows
<bitcoin-git>
bitcoin/master 0ed5f37 Ava Chow: Merge bitcoin/bitcoin#31014: net: Use GetAdaptersAddresses to get local ad...
<bitcoin-git>
[bitcoin] achow101 merged pull request #27826: validation: log which peer sent us a header (master...2023/05/saw-header) https://github.com/bitcoin/bitcoin/pull/27826
<bitcoin-git>
bitcoin/master bad7c91 Sjors Provoost: Log which peer sent us a header
<bitcoin-git>
bitcoin/master f9fa287 Sjors Provoost: Use LogBlockHeader for compact blocks
<bitcoin-git>
[bitcoin] darosior opened pull request #32381: policy: allow more than one OP_RETURN outputs per tx (master...2504_fixthefiltersyo) https://github.com/bitcoin/bitcoin/pull/32381
<bitcoin-git>
[bitcoin] hebasto opened pull request #32380: [PoC] Modernize use of UTF-8 in Windows code (master...250429-windows-utf8) https://github.com/bitcoin/bitcoin/pull/32380
<bitcoin-git>
[bitcoin] fanquake merged pull request #32369: test: Use the correct node for doubled keypath test (master...fix-double-keypath-test) https://github.com/bitcoin/bitcoin/pull/32369
<bitcoin-git>
[bitcoincore.org] azuchi opened pull request #1128: Add japanese translation for security advisory for remaining CVE-2024-52919 issue (master...ja-translate-cve-2024-52919) https://github.com/bitcoin-core/bitcoincore.org/pull/1128
<bitcoin-git>
[bitcoin] achow101 opened pull request #32369: test: Use the correct node for doubled keypath test (master...fix-double-keypath-test) https://github.com/bitcoin/bitcoin/pull/32369
<bitcoin-git>
[bitcoin] achow101 merged pull request #32327: test: Add missing check for empty stderr in util tester (master...2504-test-util-empty-err) https://github.com/bitcoin/bitcoin/pull/32327
<bitcoin-git>
bitcoin/master fadf12a MarcoFalke: test: Add missing check for empty stderr in util tester
<bitcoin-git>
bitcoin/master 65714c1 Ava Chow: Merge bitcoin/bitcoin#32327: test: Add missing check for empty stderr in u...
<bitcoin-git>
[bitcoin] stickies-v opened pull request #32364: refactor: validation: mark CheckBlockIndex as const (master...2025-04/const-checkblockindex) https://github.com/bitcoin/bitcoin/pull/32364
<corebot>
https://github.com/bitcoin/bitcoin/issues/29124 | test: Test that migration automatically repairs corrupted metadata with doubled derivation path by achow101 · Pull Request #29124 · bitcoin/bitcoin · GitHub
<bitcoin-git>
[bitcoin] maflcko opened pull request #32360: test: Force named args in RPCOverloadWrapper optional args (master...2504-named-args) https://github.com/bitcoin/bitcoin/pull/32360
2025-04-27
<bitcoin-git>
[bitcoin] petertodd opened pull request #32359: Remove arbitrary limits on OP_Return (datacarrier) outputs (master...2025-op-return) https://github.com/bitcoin/bitcoin/pull/32359
<bitcoin-git>
[bitcoin] hebasto closed pull request #32349: test: Increase stack size for "Debug" builds with MSVC (master...250425-msvc-stack) https://github.com/bitcoin/bitcoin/pull/32349
2025-04-26
<bitcoin-git>
[bitcoin] hebasto opened pull request #32357: depends: Fix cross-compiling `qt` package from macOS to Windows (master...250426-macos-to-windows) https://github.com/bitcoin/bitcoin/pull/32357
<bitcoin-git>
[gui] hebasto merged pull request #864: Crash fix, disconnect numBlocksChanged() signal during shutdown (master...2025_gui_fix_crash_numBlocksChanged) https://github.com/bitcoin-core/gui/pull/864
<bitcoin-git>
[bitcoin] hebasto opened pull request #32356: cmake: Do not override flags set by the user when replacing them (master...250426-var-override) https://github.com/bitcoin/bitcoin/pull/32356
<bitcoin-git>
[bitcoin] luke-jr opened pull request #32355: Bugfix: Miner: Don't reuse block_reserved_weight for "block is full enough to give up" weight delta (master...fix_block_full_enough) https://github.com/bitcoin/bitcoin/pull/32355
<bitcoin-git>
[gui] hebasto merged pull request #868: Replace stray tfm::format to cerr with qWarning (master...2025-05-qt-stray-format) https://github.com/bitcoin-core/gui/pull/868
<bitcoin-git>
[bitcoin] Eunovo opened pull request #32344: Bug/Wallet: Non-Ranged Descriptors with Range [0,0] Trigger Unexpected Wallet Errors in AddWalletDescriptor (master...bug-fix-wallet-add-non-ranged-descriptors) https://github.com/bitcoin/bitcoin/pull/32344
<bitcoin-git>
[bitcoin] laanwj closed pull request #30756: run_command: Close non-std fds when execing slave processes (master...subproc_closefds) https://github.com/bitcoin/bitcoin/pull/30756
<bitcoin-git>
[bitcoin] laanwj opened pull request #32343: common: Close non-std fds before exec in RunCommandJSON (master...2025-04-closefds) https://github.com/bitcoin/bitcoin/pull/32343
<bitcoin-git>
[bitcoin] tomasandroil opened pull request #32342: Fix missing error check in `set_clo_on_exec` for FD_CLOEXEC handling (master...fix/update) https://github.com/bitcoin/bitcoin/pull/32342
<laanwj>
dzxzg: oh i see your point now, yes it's less of an issue if we rename the repo to bitcoin-core too
<sipa>
glozow: i think that's much more applicable to bitcoin.org vs bitcoincore.org than github.com/bitcoin vs github.com/bitcoin-core, but yeah
<glozow>
yeah I definitely don't think Bitcoin and Bitcoin Core are the same thing. Really no single piece of software could be == Bitcoin. But most users don't know that, they will search for something called 'bitcoin,' run it, and manage their money with it...
<dzxzg>
I'm not asking whether they'll give it up, just wondering if it's an issue that there's an aural collision with this other org "bitcoincore/bitcoin" (but I'm overall +1 on moving to bitcoin-core)
<sr_gi[m]>
I personally think that the risk of github breaking redirects is higher than someone in the bitcoin org creating a bips repo, and what the implications may be
<sipa>
we like the project to be easy to find, and be prominent, but it isn't Bitcoin
<darosior>
glozow: i think this is again a good point to bring up bitcoin.org
<sipa>
glozow: i hear you - but it also just feels inappropriate that Bitcoin Core ended with the bitcoin/ org name, for historical reasons
<vasild>
so the only solution seems to be to move bitcoin/bips to another org and leave the rest as it is?
<achow101>
(should bitcoin exist that long)
<glozow>
What if github stops doing redirects or kicks us for squatting? Not to be a doomer but what if some random money-stealing or just poorly maintained client takes over bitcoin/bitcoin? bitcoin.org not keeping up with software updates already causes people on the network to run unmaintained software.
<sr_gi[m]>
As opposed to keeping either bitcoin or bips on it