timbo_xyz has quit [Remote host closed the connection]
w0xlt has quit [Ping timeout: 245 seconds]
timbo_xyz has joined #bitcoin-core-dev
timbo_xyz has quit [Remote host closed the connection]
timbo_xyz has joined #bitcoin-core-dev
Guest19 has joined #bitcoin-core-dev
Guest19 has quit [Client Quit]
tarotfied has quit [Quit: WeeChat 4.1.1]
timbo_xyz has quit [Ping timeout: 258 seconds]
ghost43 has quit [Ping timeout: 258 seconds]
ghost43 has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
w0xlt has joined #bitcoin-core-dev
w0xlt has quit [Ping timeout: 244 seconds]
adil has quit [Ping timeout: 264 seconds]
timbo_xyz has joined #bitcoin-core-dev
tarotfied has joined #bitcoin-core-dev
adil has joined #bitcoin-core-dev
Guyver2 has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] stickies-v opened pull request #34775: kernel: make logging callback global (master...2026-02/kernel-logging-global) https://github.com/bitcoin/bitcoin/pull/34775
l0rinc has joined #bitcoin-core-dev
enochazariah has joined #bitcoin-core-dev
loungerry_ has quit [Remote host closed the connection]
w0xlt has joined #bitcoin-core-dev
w0xlt has quit [Ping timeout: 264 seconds]
tarotfied has quit [Quit: WeeChat 4.1.1]
tarotfied has joined #bitcoin-core-dev
dviola has quit [Ping timeout: 256 seconds]
diego has joined #bitcoin-core-dev
diego is now known as Guest1302
Guest1302 has left #bitcoin-core-dev [#bitcoin-core-dev]
<bitcoin-git>
[bitcoin] fanquake merged pull request #34037: wallet, doc: clarify the coin selection filters that enforce cluster count (master...2025-12-ancestry) https://github.com/bitcoin/bitcoin/pull/34037
<bitcoin-git>
[bitcoin] hodlinator opened pull request #34776: guix: Make guix-clean less destructive (master...2026/03/guix_clean_destructive) https://github.com/bitcoin/bitcoin/pull/34776
<ryanofsky>
dergoegge, that looks basically perfect and answers the question I had about if this is supposed to be able to deterministically reproduce bugs, why does there seem to be no way to do that
<ryanofsky>
only other information i could think of adding is information about how other people can run antithesesis to find new bugs, if not reproduce existing ones
<ryanofsky>
like if you have configuration, scripts, those could just be interesting to see, even if not directly useful for fixing reported bugs
<dergoegge>
ryanofsky: I'll eventually open source the tests, so anyone can have a look and suggest improvements. Launching a run requires permissions that give access to the whole platform. We probably want to keep that access limited (like we do for e.g. oss-fuzz as well)
<dergoegge>
Ideally a couple people have access eventually, so I am not a bottleneck
w0xlt has joined #bitcoin-core-dev
w0xlt has quit [Ping timeout: 276 seconds]
<ryanofsky>
dergoegge, nice. I'm mostly just asking because the platform seems very cool and I'm impressed with the bugs it found so curious what the setup looks like
<bitcoin-git>
[bitcoin] darosior opened pull request #34779: BIP xxx: reserve version bits 5-28 as extra nonce space (master...2602_more_version_bits_rolling) https://github.com/bitcoin/bitcoin/pull/34779
<darosior>
_aj_: why have the dummy deployment out of the bounds of the deployment we support?
<_aj_>
darosior: avoids changing all the constants, and avoids using up a real deployment slot for a test case
<darosior>
downside is: we don't test deployment activation using a real deployment slot
<darosior>
Also the constant `VERSIONBITS_NUM_BITS` would still have to change, so this would only save updating the test constant in mining_basic.py and the hardcoded bit in rpc_blockchain.py. Not clear to me it's worth it
nymius has joined #bitcoin-core-dev
memset has quit [Remote host closed the connection]