💬 andrewtoth commented on pull request "index: initial sync speedup, parallelize process":
(https://github.com/bitcoin/bitcoin/pull/26966#discussion_r1817847707)
This would make sense if we wanted to reuse this for CCheckQueue. Then, we could just loop and `ProcessTask` on the main thread once when we call `Wait`.

🤔 glozow reviewed a pull request: "functional test: Additional package evaluation coverage"
(https://github.com/bitcoin/bitcoin/pull/31152#pullrequestreview-2397255278)
reACK f32c34d0c3d4041a301822b27e88d6db4cbf631e

👍 instagibbs approved a pull request: "test: added test to assert TX decode rpc error on submitpackage rpc"
(https://github.com/bitcoin/bitcoin/pull/31139#pullrequestreview-2397254972)
ACK 1fab1d601e40edc7296cf3d60a7e917b0e6493b3

with minor suggestion

💬 instagibbs commented on pull request "test: added test to assert TX decode rpc error on submitpackage rpc":
(https://github.com/bitcoin/bitcoin/pull/31139#discussion_r1817851813)
```suggestion
assert txid_list[0] not in node.getrawmempool()
assert txid_list[1] not in node.getrawmempool()
```

🚀 glozow merged a pull request: "functional test: Additional package evaluation coverage"
(https://github.com/bitcoin/bitcoin/pull/31152)

💬 TheCharlatan commented on pull request "build, ci: Fix linking `bitcoin-chainstate.exe` to `bitcoinkernel.dll` on Windows":
(https://github.com/bitcoin/bitcoin/pull/31158#discussion_r1817854236)
I checked if this could also be a problem for other extern symbols that are currently not used in `bitcoin-chainstate`, but still part of the kernel library. For example in `src/validation.h` we have `extern const std::vector<std::string> CHECKLEVEL_DOC;`, and it looks like using it is indeed problematic too if it were used externally: https://github.com/TheCharlatan/bitcoin/actions/runs/11531552497/job/32102377337#step:10:425.
There are a bunch of other such cases, where I'm not entirely sure
...

📝 hebasto opened a pull request: "cmake: Set top-level target output locations"
(https://github.com/bitcoin/bitcoin/pull/31161)
This PR sets the target output locations to the `bin` and `lib` subdirectories within the build tree, creating a directory structure that mirrors that of the installed targets.

This approach is widely adopted by the large projects, such as [LLVM](https://github.com/llvm/llvm-project/blob/e146c1867e8decfd423034f63a3a863733e03f04/lldb/cmake/modules/LLDBStandalone.cmake#L128-L130):
```cmake
set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)
set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_
...

⚠️ carnhofdaki opened an issue: "Stop at header"
(https://github.com/bitcoin/bitcoin/issues/31162)
### Please describe the feature you'd like to see added.

While preparing the little ter.gz file for https://github.com/fjahr/test_chain_init/issues/1 I stumbled upon the fact that one is unable to download just a couple of blocks in the beginning without synchronizing the full header chain.

I would be happy if the `stopatheight` option was respected also header-wise. This is a feature request.

Using 28.0 x86_64 Linux release binaries from bitcoincore.org

```
$ bitcoind -help -help-deb
...

👍 tdb3 approved a pull request: "rpc: add getdescriptoractivity"
(https://github.com/bitcoin/bitcoin/pull/30708#pullrequestreview-2397262411)
re ACK f383db76ec3aaa9391509c1d9cca763d11b6fe00

Changes include updating `scriptpubkey_hex` result type to `STR_HEX`, cleaner `Coin` usage, and adding a test for unconfirmed tx.

<details>
<summary>git range-diff d79ea809d28197b1b4e3748aa1715272b53601d0..1365ee8e9c7a20aa63bcddb1a6d5843c05ff9330 25dacae9c7feb31308271e2fd5a127c1fc230c2f..f383db76ec3aaa9391509c1d9cca763d11b6fe00</summary>

```diff
1: 1365ee8e9c7 ! 1: f383db76ec3 rpc: add getdescriptoractivity
@@ src/rpc/blockchain.c
...

💬 TheCharlatan commented on pull request "cmake: Set top-level target output locations":
(https://github.com/bitcoin/bitcoin/pull/31161#issuecomment-2439601361)
Concept ACK

💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1817860890)
I haven't looked lately but these harnesses should trigger package RBF behavior. I added the package mempool results checking to check the related invariants.

💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1817860896)
updated

💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1817860901)
yeah that's confusing, reworded

💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1817860919)
correct, updated comment

💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1817860922)
done

💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1817860928)
out of date logging, updated

💬 jadijadi commented on issue "か":
(https://github.com/bitcoin/bitcoin/issues/29609#issuecomment-2439602668)
Is this spam / scam? I believe this can be closed.

✅ fanquake closed an issue: "か"
(https://github.com/bitcoin/bitcoin/issues/29609)

:lock: fanquake locked an issue: "か"
(https://github.com/bitcoin/bitcoin/issues/29609)

🤔 hodlinator reviewed a pull request: "test: cover base32/base58/base64 with symmetric roundtrip fuzz (and padding) tests"
(https://github.com/bitcoin/bitcoin/pull/30746#pullrequestreview-2397249971)
Concept ACK ad917fb105b68fb369455ec7c42292a7673db1ad

- Extra tests/coverage, does not modify files containing the functionality being tested.
- Does remove `base58_random_encode_decode` unit test, but everything seems to be carried over to the modified fuzz test (except for testing for a variable count of insufficient result buffer sizes).