<bitcoin-git>
[bitcoin] furszy opened pull request #28574: wallet: optimize migration process, batch db transactions (master...2023_wallet_batch_migration) https://github.com/bitcoin/bitcoin/pull/28574
<bitcoin-git>
[bitcoin] ryanofsky opened pull request #28573: github actions: Fix test-one-commit when parent of head is merge commit (master...pr/onecommit) https://github.com/bitcoin/bitcoin/pull/28573
<bitcoin-git>
[gui] hebasto merged pull request #751: macOS, do not process actions during shutdown (master...2023_gui_fix_appbar_crash) https://github.com/bitcoin-core/gui/pull/751
<bitcoin-git>
bitcoin/master e14cc8f furszy: gui: macOS, do not process dock icon actions during shutdown
<bitcoin-git>
bitcoin/master 88e5a02 Hennadii Stepanov: Merge bitcoin-core/gui#751: macOS, do not process actions during shutdown
<bitcoin-git>
bitcoin/master bae209e furszy: gui: macOS, make appMenuBar part of the main app window
<bitcoin-git>
[bitcoin] fanquake opened pull request #28571: depends: fix unusable memory_resource in macos qt build (master...qt_fix_more_macos_broken) https://github.com/bitcoin/bitcoin/pull/28571
<bitcoin-git>
[bitcoin] fjahr opened pull request #28569: Don't log cache rebalancing in absense of a snapshot chainstate (master...2023-10-au-cache-log) https://github.com/bitcoin/bitcoin/pull/28569
<bitcoin-git>
[bitcoin] fjahr opened pull request #28567: ci: Only run functional tests on windows in master (master...2023-10-gha-win) https://github.com/bitcoin/bitcoin/pull/28567
<bitcoin-git>
[bitcoin] fanquake merged pull request #28543: build, macos: Fix `qt` package build with new Xcode 15 linker (master...230927-qt-sonoma) https://github.com/bitcoin/bitcoin/pull/28543
<bitcoin-git>
[bitcoin] luke-jr opened pull request #28564: Bugfix: configure: Correct check for fuzz binary needing a main function (master...fix_conf_fuzzbin_main) https://github.com/bitcoin/bitcoin/pull/28564
<fanquake>
This is one of the last blockers for 25.1, and I'd rather not drop it, as it's been enough of an issue for downstreams to prevent them from upgrading to 25.0. i.e https://github.com/fort-nix/nix-bitcoin/issues/611
<gribble`>
https://github.com/bitcoin/bitcoin/issues/28551 | http: bugfix: allow server shutdown in case of remote client disconnection by stickies-v · Pull Request #28551 · bitcoin/bitcoin · GitHub
<bitcoin-git>
[bitcoin] fanquake merged pull request #28542: wallet: Check for uninitialized last processed and conflicting heights in MarkConflicted (master...migrate-with-conflicted-txs) https://github.com/bitcoin/bitcoin/pull/28542
<bitcoin-git>
bitcoin/master 50f250a fanquake: Merge bitcoin/bitcoin#28542: wallet: Check for uninitialized last processe...
<bitcoin-git>
bitcoin/master 782701c Andrew Chow: test: Test loading wallets with conflicts without a chain
<bitcoin-git>
bitcoin/master 4660fc8 Andrew Chow: wallet: Check last block and conflict height are valid in MarkConflicted
<bitcoin-git>
[bitcoin] hebasto closed pull request #28509: qa: Fix intermittent "Unable to connect to bitcoind" errors on Windows (master...230919-subprocess) https://github.com/bitcoin/bitcoin/pull/28509
<bitcoin-git>
[bitcoin] fanquake merged pull request #28556: doc: fix link to developer-notes.md file in multiprocess.md (master...master) https://github.com/bitcoin/bitcoin/pull/28556
<bitcoin-git>
bitcoin/master d9b172c David Álvarez Rosa: doc: fix link to developer-notes.md file in multiprocess.md
<bitcoin-git>
bitcoin/master dcf6230 fanquake: Merge bitcoin/bitcoin#28556: doc: fix link to developer-notes.md file in m...
<bitcoin-git>
[bitcoin] david-alvarez-rosa opened pull request #28556: doc: fix link to developer-notes.md file in multiprocess.md (master...master) https://github.com/bitcoin/bitcoin/pull/28556
<bitcoin-git>
[bitcoin] fanquake merged pull request #28227: test: check for specific bip157 disconnect reasons, add test coverage (master...202308-test-p2p_blockfilters_improvements) https://github.com/bitcoin/bitcoin/pull/28227
<bitcoin-git>
bitcoin/master 63e90e1 Sebastian Falbesoner: test: check for specific disconnect reasons in p2p_blockfilters.py
<bitcoin-git>
bitcoin/master 2ab7952 Sebastian Falbesoner: test: add bip157 coverage for (start height > stop height) disconnect
<bitcoin-git>
bitcoin/master e3b0528 fanquake: Merge bitcoin/bitcoin#28227: test: check for specific bip157 disconnect re...
<bitcoin-git>
[bitcoin] fanquake merged pull request #28545: test: Avoid test failure on Linux root without cap-add LINUX_IMMUTABLE (master...2309-test-fix-root-cap-) https://github.com/bitcoin/bitcoin/pull/28545
<bitcoin-git>
bitcoin/master f66af92 fanquake: Merge bitcoin/bitcoin#28545: test: Avoid test failure on Linux root withou...
<bitcoin-git>
bitcoin/master fa40b3e MarcoFalke: test: Avoid test failure on Linux root without cap-add LINUX_IMMUTABLE
<josie>
achow101: sounds good, but I do think its important to limit voting to people who are actively contributing/reviewing in the project. this isnt a vote of "what would you like to see in bitcoin core" and more signaling "i will prioritise working on and reviewing x"
<D33r-Gee>
Testing PR #27596 (AssumeUTXO) and the pruning (prune=3000) doesn't work, still getting a 'blocks' folder size of 37 GB even after the progress has reached 1 (progress=1.000000), am I missing something perhaps in the bitcoin.conf file?
<BlueMattTest>
Sadly because this room is registered-only this requires actually signing in with @libera_irc_NickServ:bitcoin.ninja and then storing a password through a bridge I operate. I do promise I'm too lazy to look up your password, but no promises, of course.
<BlueMatt[m]>
I added this channel to my matrix bridge for those who want to access via matrix after the all-of-libera bridge was shutdown - #libera_bitcoin-core-dev:bitcoin.ninja.
<dergoegge>
actually no i don't think that explains it because the timeouts reproduce locally using `python infra/helper.py run_fuzzer --engine afl bitcoin-core process_messages`
2023-09-12
<PaperSword>
Is there method in CScript that will print the op codes in the same way bitcoin-cli decodescript does?
<PaperSword>
I created pull https://github.com/bitcoin/bitcoin/pull/28447, becuase I thought it was what was causing the linter errors. It was not. I closed it. None the less it might be good to consider to remove linter warnings for those 2 words.
<fjahr>
some probably read the previous conversation here, pinheadmz made a new github bot that currently lives in #bitcoin-core-github and now emulates the behavior of the matrix bridge/gh-bot. If people like it could be pointed on this channel as well. But I guess it’s also fine to have a separate channel, at least that also works for me. Just wanted to put it out there as an option.
<sipa>
the bot is working fine, except it's posting to the #bitcoin-core-dev:libera.chat matrix channel, and the bridge between that channel and here is suspended indefinitely
<PaperSword>
What are you interested in working on in Bitcoin?
2023-08-18
<sipa>
Bz0: try bitcoin.stackexchange.com
<Bz0>
const bitcoin = new BitcoinCore(config);"
<Bz0>
host: '127.0.0.1', // Your Bitcoin Core node's IP address
<Bz0>
Can anyone help me out connecting my NodeJS script to my bitcoin core node? No matter what i try it constantly tells me "ThreadRPCServer incorrect password attempt". ive tried with rpcuser+rpcpassword first, then tried the rpcauth method and finally tried the __cookie__ method, nothing works... Using windows 10. i have this at the top of my JS file
<fjahr>
This channel is particularly for development of bitcoin core, an alternative implementation of the protocol is out of scope. I would recommend you post your question on bitcoin stack exchange. And fwiw, you should also check if you can achieve your goal by just using bitcoin core's zmq interface, then you won't need to think about version messages etc.
<ne0h>
i am trying to make a program that connects to the bitcoin network to collect new transactions in the mempool and new blocks in real time, but I am having trouble getting it going. My version message doesn't get a response... I suspect it's something to do with the formatting or something, but i have tried a few things and nothing has worked so far, if anybody could help me get this running it would be quite appreciated
<MacroFake>
cfields: There may be a chance we can use native C++20 instead of the bitcoin-unterminated-logprintf tidy rule
<cfields>
jamesob: fyi, those /* Continued */ are gone because clang-tidy is smarter than our python scripts. We now opt-out with // NOLINT(bitcoin-unterminated-logprintf)
<sipa>
and yes, we could prune some more unspendable outputs, but that's an implementation detail inside bitcoin core, which imho shouldn't really interact with questions about relay policy
<sipa>
bitcoin-dev
<_aj_>
provoostenator: "why would they not mine them" -- because they have a long term investment in bitcoin, and they believe mining those txs is bad for that investment, same as the reason why people would want to remove the spam in the first place
<luke-jr>
provoostenator: it's malicious to setup private relay networks to mine attacks on Bitcoin that the community is actively trying to mitigate