<lightlike>
eugenesiegel: I would say yes to opening an issue, just "tracking issue" is the wrong term at this stage. An issue (or alternatively a draft PR) where you detail your proposal for conceptual discussion would be the way to go. Individual PRs and and possibly a separate issue tracking them would naturally come after conceptual buy-in from others.
<ekzyis>
how much interest is there still in adding honggfuzz: https://github.com/bitcoin-core/qa-assets/issues/267? the ticket is 2 years old, and I'm thinking, "maybe it's more important to review fuzzing PRs?"
twistedline has quit [Remote host closed the connection]
twistedline has joined #bitcoin-core-dev
<nkaretnikov>
ekzyis: what is the current state of fuzzing efforts? what tools are being used and what is being fuzzed?
l0rinc has quit [Quit: l0rinc]
brunoerg has quit [Ping timeout: 244 seconds]
aleggg has joined #bitcoin-core-dev
jonatack has joined #bitcoin-core-dev
jon_atack has quit [Ping timeout: 256 seconds]
cotsuka has quit [Read error: Connection reset by peer]
brunoerg has joined #bitcoin-core-dev
cotsuka has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 265 seconds]
kevkevin has quit [Ping timeout: 244 seconds]
Guyver2 has joined #bitcoin-core-dev
cotsuka has quit [Read error: Connection reset by peer]
cotsuka has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] Sjors closed pull request #34970: init: add -test=pause_load_mempool, test mempool save before loaded (master...2026/03/pause-mempool-load) https://github.com/bitcoin/bitcoin/pull/34970
brunoerg has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 276 seconds]
BrandonOdiwuor has joined #bitcoin-core-dev
Guyver2 has left #bitcoin-core-dev [Closing Window]
<bitcoin-git>
[bitcoin] maflcko opened pull request #35391: test: Use operator for time_points instead of manual TickSinceEpoch (master...2605-test-iwyu-op-less-less) https://github.com/bitcoin/bitcoin/pull/35391
sliv3r__ has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
sliv3r__ has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] maflcko closed pull request #34839: doc: remove unshipped doc references from help and warning text (master...doc/unshipped-doc-links-helptext) https://github.com/bitcoin/bitcoin/pull/34839
brunoerg has joined #bitcoin-core-dev
<maflcko>
ekzyis: I'd say it can be considered, if it has meaningfully different coverage instrumentation. (Haven't looked into it at all)
brunoerg has quit [Ping timeout: 248 seconds]
kevkevin has quit [Ping timeout: 272 seconds]
brunoerg has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] Sjors opened pull request #35392: test: add v31.0 and basic IPC backward compatibility check (master...2026/05/backward-v31-ipc) https://github.com/bitcoin/bitcoin/pull/35392
kevkevin has joined #bitcoin-core-dev
cotsuka has quit [Read error: Connection reset by peer]
brunoerg has quit [Ping timeout: 256 seconds]
cotsuka has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 264 seconds]
eugenesiegel has joined #bitcoin-core-dev
<eugenesiegel>
lightlike: ok thanks, I will open an issue for discussion
sliv3r__ has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
<bitcoin-git>
bitcoin/master a815e3e Hodlinator: rpc: Correct type for tx_sigops
<bitcoin-git>
bitcoin/master 0774eaa Hodlinator: util: Require integers for SaturatingAdd() and AdditionOverflow()
<bitcoin-git>
bitcoin/master 0687438 merge-script: Merge bitcoin/bitcoin#35372: refactor: Enhance type safety in overflow ope...
<bitcoin-git>
[bitcoin] sedited merged pull request #35372: refactor: Enhance type safety in overflow operations (master...2026/05/overflow_ints) https://github.com/bitcoin/bitcoin/pull/35372
brunoerg has quit [Ping timeout: 244 seconds]
brunoerg has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 267 seconds]
<ekzyis>
nkaretnikov: libfuzzer and afl++ is used, see linked qa-assets repo. can't tell you much more, i am new to fuzzing myself. you can start at doc/fuzzing.md i guess
<ekzyis>
maflcko: ok thx
<eugenesiegel>
honggfuzz once found an integer issue that libfuzzer / afl did not, but I think that may have just been bias in the fuzzing harnesses
<nkaretnikov>
ekzyis: I remembered there’s also this project from dergoegge https://github.com/dergoegge/fuzzamoto but I’m not sure how the fuzzing effort is organized here. is there a dedicated fuzzing group or is it random people? IIRC brink donates infra to core, are fuzzers running 24/7? who is configuring them and triaging crashes?
cotsuka has quit [Read error: Connection reset by peer]
cotsuka has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 264 seconds]
<nkaretnikov>
In general fuzzing is both tooling and researcher’s time/creativity. So setting them up and forgetting doesn’t make sense to me. It needs to be a constant process of improving coverage and looking at crashes. As well as doing something to increase speed of fuzz tooling etc.
<nkaretnikov>
One related issue that I’ve started to work on is making standard test coverage more visible. It needs to be on CI to increase the baseline of what’s being tested normally. Not directly related to fuzzing but has implications.
<dergoegge>
Hi Nikita! We have ~250 harnesses in the main repo (bitcoin/bitcoin), there's fuzzamoto, and there's also https://github.com/bitcoinfuzz/bitcoinfuzz. All of these are fuzzing 24/7. The harnesses in the main repo get fuzzed on oss-fuzz and also on machines of various contributors.
brunoerg has joined #bitcoin-core-dev
<dergoegge>
There are people (e.g. me) that spend a lot of their time on fuzzing. There is an irc channel (#bitcoin-core-fuzzing) for the fuzzing working group, although that chat is pretty quiet
<dergoegge>
Let me know if you have any other questions
brunoerg has quit [Ping timeout: 265 seconds]
cfields has quit [Ping timeout: 252 seconds]
cfields has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] willcl-ark opened pull request #35394: test: remove unnecessary rpc calls from feature_dbcrash (master...faster-dbcrash) https://github.com/bitcoin/bitcoin/pull/35394
<ekzyis>
cool, didn't know about that irc channel. would you prefer we ask questions there?
kevkevin has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
<nkaretnikov>
dergoegge: yeah, I’ll follow up on the fuzzing channel.
cotsuka has quit [Read error: Connection reset by peer]
<bitcoin-git>
[bitcoin] hebasto opened pull request #35395: doc: Improve test suite dependencies documentation (master...260527-ft-needed) https://github.com/bitcoin/bitcoin/pull/35395
<b10c>
got matching hashes between a Nix-built bitcoind and the v31.0 bitcoind for x86_64-pc-linux-gnu built with Guix 😎 wen cross toolchain reproducible bulids? https://b10c.me/projects/027-bitcoind-gunix-match/
<nkaretnikov>
I mean that’s not very surprising since they are based on the same idea. Guix also uses the nix daemon. So if you provide the same input you get the same output in both. The difference is the layer of scheme on top compared to nix
<b10c>
and a few other, minor, differences between the two
cotsuka has quit [Read error: Connection reset by peer]
cotsuka has joined #bitcoin-core-dev
<sipa>
nkaretnikov: guix uses the nix daemon?
<darosior>
that sounds surprising. The guix daemon is written in GNU Guile
<nkaretnikov>
sipa: at least it used to when i worked on it a long time ago. maybe they rewrote it since then, so i guess i should not have said it so confidently. a historical note: ludovic created guix because he was a nixos user, but wanted nix with only free software, and he was a guile developer, so he wanted the flexibility of scheme instead of nix. i was the first contributor to guix and worked with ludovic the first two
<nkaretnikov>
years of the project and at the time it definitely used the nix daemon.
<nkaretnikov>
darosior: yeah, ignore it then. they must have ported it in the meantime.
jonatack has joined #bitcoin-core-dev
robszarka has joined #bitcoin-core-dev
<nkaretnikov>
speaking of nix, can we reach some decision here? https://github.com/bitcoin/bitcoin/pull/35375 i feel like i responded to a lot of concerns, made compromises, and i honestly don’t understand what the big deal is with getting this merged. there’s more discussion on that PR compared to the text in the PR itself. right now it sits at 1 ack and 1 nack and people are also discussing what to do with installation docs in
<nkaretnikov>
general. what do you do in cases like this? just let it sit opened until acks or nacks outbalance each other? will it get closed automatically at some point. when i started this, i thought “hey, let me do a 30 min PR since i already did all that work” and now it’s been two days of discussion with no action.
szarka has quit [Ping timeout: 248 seconds]
<ekzyis>
nkaretnikov: i think you need to have more patience
<nkaretnikov>
ekzyis: i’m happy to wait, it’s the first pr i’ve opened so i’m not familiar with the process. i also don’t like indeterminate states with no action or decision maker. i want to open more prs in the future, but if a doc change is taking so long, i don’t know what i should expect for code changes.
memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 244 seconds]
bomb-on has joined #bitcoin-core-dev
<pinheadmz>
nkaretnikov this project is overwhelmed with work and underpowered by contributors. expect everything, even doc changes, to take a long time. I authored a doc update a month ago that just got merged today
<pinheadmz>
show everyone you are patient and have other work to do while you wait, and your reputation will increase