💬 cdecker commented on issue "DNS seed "seed.bitcoinstats.com" doesn't support filtering while the comments says it does":
(https://github.com/bitcoin/bitcoin/issues/29911#issuecomment-2172871011)
I spoke with @emzy and I decided to revive this seed, and migrate to a more standard deployment as well. The overhead of the custom solution did not add enough quality, and caused the seeder to rot and break. Using sipa's seeder will solve that, and reduce the burden of maintenance.

No timeline yet, but I'll dedicate a couple of weekends

👍 hebasto approved a pull request: "ci: parse TEST_RUNNER_EXTRA into an array"
(https://github.com/bitcoin/bitcoin/pull/30244#pullrequestreview-2122406132)
ACK 8131bf7483c0ea10d3573c9f2e977d19d8569b7f, tested on Ubuntu 23.10 and Windows 11.

In the command prompt on Windows, the following commands work as expected:
```
>set EXTRA=--exclude "rpc_bind.py --ipv6, feature_proxy.py"
>py -3 test\functional\test_runner.py %EXTRA%
```

which is sufficient for our CI if needed.

⚠️ Fonta1n3 opened an issue: "Setting `bip32derivs` to `false` with `walletprocesspsbt` includes `bip32_derivs` for outputs."
(https://github.com/bitcoin/bitcoin/issues/30294)
### Please describe the feature you'd like to see added.

I'd like an option to remove the `bip32derivs` from outputs as well as inputs when calling `walletprocesspsbt`.

### Is your feature related to a problem, if so please describe it.

I am using Bitcoin Core to create psbt's which are meant to be passed around to multiple users for collaborative transactions. I want to leak as little data as possible. When I set `bip32derivs` to `false` with `walletprocesspsbt` it does not remove the `bip32
...

💬 marcofleon commented on pull request "fuzz: FuzzedSock::Recv() don't lose bytes from MSG_PEEK read":
(https://github.com/bitcoin/bitcoin/pull/30273#discussion_r1642560055)
You can add it to the end of the command. So `FUZZ=i2p ./src/test/fuzz/fuzz -dict=DICTFILE`. The dictionary (`i2p.dict`) is in the qa-assets repo: https://github.com/bitcoin-core/qa-assets/tree/main/fuzz_dicts. I'm running it now on the most recent commit.

👍 dergoegge approved a pull request: "test: Add Compact Block Encoding test `ReceiveWithExtraTransactions` covering non-empty `extra_txn`"
(https://github.com/bitcoin/bitcoin/pull/30237#pullrequestreview-2122540242)
tACK 09b90c69bc17ce43dce3881a208d9066a729c67d

💬 maflcko commented on pull request "test: write functional test results to csv":
(https://github.com/bitcoin/bitcoin/pull/30291#issuecomment-2173079380)
re-ACK ad06e68399da71c615db0dbf5304d0cd46bc1f40

👍 hebasto approved a pull request: "ci: move ASan job to GitHub Actions from Cirrus CI"
(https://github.com/bitcoin/bitcoin/pull/30193#pullrequestreview-2122625080)
ACK 9eea51d9058ad638861aa4b94c1c6e71caeb8765.

💬 Sjors commented on pull request "Introduce Mining interface":
(https://github.com/bitcoin/bitcoin/pull/30200#issuecomment-2173170961)
Oops, `'TestBlockValidity failed: bad-txns-inputs-missingorspent'`...

💬 glozow commented on pull request "test: Add Compact Block Encoding test `ReceiveWithExtraTransactions` covering non-empty `extra_txn`":
(https://github.com/bitcoin/bitcoin/pull/30237#discussion_r1642697581)
really not a fan of these magic numbers, would prefer `rand_ctx.rand64()`

💬 glozow commented on pull request "test: Add Compact Block Encoding test `ReceiveWithExtraTransactions` covering non-empty `extra_txn`":
(https://github.com/bitcoin/bitcoin/pull/30237#discussion_r1642694693)
What about always requiring a `FastRandomContext` and getting a `rand64()` for the nonce that way? peerman would pass in its own `m_rng. Making the rng a param feels preferable to adding a test-only version of the ctor.

💬 rkrux commented on pull request "test: expand LimitOrphan and EraseForPeer coverage":
(https://github.com/bitcoin/bitcoin/pull/30082#discussion_r1642703544)
Can you please share how exactly is this being done `check timeout logic` here?

I see from the `AddTx` code that if the tx size is more than the standard weight, then it will not be added in the orphanage. Is the timeout logic here that the size of this tx is less than the standard weight and therefore it's inserted?

👍 rkrux approved a pull request: "test: expand LimitOrphan and EraseForPeer coverage"
(https://github.com/bitcoin/bitcoin/pull/30082#pullrequestreview-2122597073)
tACK [eaf4de0](https://github.com/bitcoin/bitcoin/pull/30082/commits/eaf4de028de8fa13227b6089785889f1c6c15b4d)

Make successful, so are all the unit tests and functional test. Asked couple questions for my understanding.

💬 rkrux commented on pull request "test: expand LimitOrphan and EraseForPeer coverage":
(https://github.com/bitcoin/bitcoin/pull/30082#discussion_r1642629997)
Nit: Tying it to `expected_num_orphans` like `expected_num_orphans -3` in the `LimitOrphans` call would make it more explicit (but not necessarily in the `BOOST_CHECK`), otherwise it made me wonder whether the current count is more than 40 or not.

💬 rkrux commented on pull request "test: expand LimitOrphan and EraseForPeer coverage":
(https://github.com/bitcoin/bitcoin/pull/30082#discussion_r1642703875)
+1 on moving these to the header file!

💬 rkrux commented on pull request "test: expand LimitOrphan and EraseForPeer coverage":
(https://github.com/bitcoin/bitcoin/pull/30082#discussion_r1642625331)
Took me a while to understand why only the first 3 peers announced 2 txs each, but it's infact the first 10 peers as per the above 3 loops that announced 2 txs each - the third tx for each of them being ignored because of its large size.

💬 glozow commented on pull request "test: expand LimitOrphan and EraseForPeer coverage":
(https://github.com/bitcoin/bitcoin/pull/30082#discussion_r1642717383)
orphans are expired in the first part of `LimitOrphans`

✅ Sjors closed an issue: "Add bitcoind and bitcoin-cli to macOS release"
(https://github.com/bitcoin/bitcoin/issues/30262)

💬 Sjors commented on issue "Add bitcoind and bitcoin-cli to macOS release":
(https://github.com/bitcoin/bitcoin/issues/30262#issuecomment-2173236827)
> the `bitcoin-cli` utility is included in the macOS tar

Oh, it's in the tar but not in the zip. That's confusing, but a matter of improving documentation.

In that case I'll close this and will defer to #29749 (assuming we also sign x86 binaries).

💬 Sjors commented on issue "release: ship codesigned MacOS arm64 binaries":
(https://github.com/bitcoin/bitcoin/issues/29749#issuecomment-2173242397)
If we code-sign in the tar file, let's also sign them for x86. Otherwise the user has to right-click -> option & open them once.

💬 brunoerg commented on pull request "test: write functional test results to csv":
(https://github.com/bitcoin/bitcoin/pull/30291#discussion_r1642762119)
It creates the file if it doesn't exist, right?