💬 patrik090315-beep commented on issue "Release Schedule for 31.0":
(https://github.com/bitcoin/bitcoin/issues/33607#issuecomment-3418826895)
RTL online élő

💬 Christewart commented on pull request "refactor: optimize block index comparisons (1.4-6.8x faster)":
(https://github.com/bitcoin/bitcoin/pull/33637#issuecomment-3418835243)
I attempted to run the script, not really sure what these results indicate. Just pasting what the results were

```
Darwin Chriss-MacBook-Pro.local 24.6.0 Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:55 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6031 arm64
```

```
Apple clang version 17.0.0 (clang-1700.3.19.1)
Target: arm64-apple-darwin24.6.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
```


```
| ns/cmp | cmp/s
...

✅ furszy closed a pull request: "p2p: avoid traversing blocks (twice) during IBD"
(https://github.com/bitcoin/bitcoin/pull/32730)

💬 l0rinc commented on pull request "refactor: optimize block index comparisons (1.4-6.8x faster)":
(https://github.com/bitcoin/bitcoin/pull/33637#issuecomment-3419090521)
Thanks for the measurements @Christewart, this is how your measurements compare to mine (but most importantly how it compares to `master`):
<img width="2385" height="883" alt="image" src="https://github.com/user-attachments/assets/96a59d25-292e-4e11-bd2c-3fb11a5b13cb" />

💬 lucifermmmenriquejr commented on pull request "p2p: avoid traversing blocks (twice) during IBD":
(https://github.com/bitcoin/bitcoin/pull/32730#issuecomment-3419147516)
Enrique Ramirez

On Sat, Oct 18, 2025, 5:29 PM Matias Furszyfer ***@***.***>
wrote:

> Closed #32730 <https://github.com/bitcoin/bitcoin/pull/32730>.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bitcoin/bitcoin/pull/32730#event-20362922986>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BSKJHMJLQ2ZPL3ELNRNAYOT3YLEPFAVCNFSM6AAAAAB7DDPV5SVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRQGM3DEOJSGI4TQNQ>
> .
> You are
...

⚠️ Braga17 opened an issue: "PR: Developer Experience & CI Enhancements (Devcontainer, CMake Presets, Docs)"
(https://github.com/bitcoin/bitcoin/issues/33656)
### Please describe the feature you'd like to see added.



Summary

This PR introduces small, additive improvements focused on developer experience (DX), CI clarity, and contributor onboarding for Bitcoin Core. It does not modify Guix, depends, or existing build/release workflows.


---

What’s included

1. Devcontainer

Adds a .devcontainer/ folder with:

devcontainer.json and post-create.sh for local or Codespaces builds.

Preconfigured environment with toolchains, Python deps, and ccache.

S
...

✅ fanquake closed an issue: "PR: Developer Experience & CI Enhancements (Devcontainer, CMake Presets, Docs)"
(https://github.com/bitcoin/bitcoin/issues/33656)

📝 romanz opened a pull request: "rest: allow reading partial block data from storage"
(https://github.com/bitcoin/bitcoin/pull/33657)
It will allow fetching specific transactions using an external index, following https://github.com/bitcoin/bitcoin/pull/32541#issuecomment-3267485313.

Currently, electrs and other indexers map between an address/scripthash to the list of the relevant transactions.

However, in order to fetch those transactions from bitcoind, electrs relies on reading the whole block and post-filtering for a specific transaction[^1]. Other indexers use a `txindex` to fetch a transaction using its txid [^2][^
...

📝 ubbabeck opened a pull request: "test: multisig verify spend from 100 of 999 taproot multisig wallet"
(https://github.com/bitcoin/bitcoin/pull/33658)
- **miniscript: fixes #29098 by only use first k valid signatures #31719**
- ** test: verify spend from 999-of-999 taproot multisig wallet #28212**

Testing of https://github.com/bitcoin/bitcoin/pull/31719 to test if it is a proper candidate ref https://github.com/bitcoin/bitcoin/pull/28212#issuecomment-2608930756.

Seems to help on my computer the test takes `build/test/functional/wallet_taproot.py 33.31s user 1.08s system 97% cpu 35.114 total`
to complete.

feel free to close the pr
...

💬 sdaftuar commented on pull request "Cluster mempool":
(https://github.com/bitcoin/bitcoin/pull/33629#discussion_r2443315198)
This test is further updated in a later commit in this PR -- please let me know what you think of the state it ends up in and if it could use further improvements.

💬 sdaftuar commented on pull request "Cluster mempool":
(https://github.com/bitcoin/bitcoin/pull/33629#discussion_r2443316513)
Seems redundant, given that we have an `EXCLUSIVE_LOCKS_REQUIRED` annotation on `GetChangeSet()` already? Will leave this as-is.

💬 sdaftuar commented on pull request "Cluster mempool":
(https://github.com/bitcoin/bitcoin/pull/33629#discussion_r2443318588)
`clear()` doesn't change the capacity of the vector, so there's no need to `reserve()` again.

💬 sdaftuar commented on pull request "Cluster mempool":
(https://github.com/bitcoin/bitcoin/pull/33629#discussion_r2443321045)
This is a reference to Rule #5 in `doc/policy/mempool-replacements.md`.

💬 sdaftuar commented on pull request "Cluster mempool":
(https://github.com/bitcoin/bitcoin/pull/33629#discussion_r2443329464)
I think "spent" would be confusing, as the purpose of this object is to store the data needed to undo the removal of a utxo from the unspent_prevouts list, in the event that a transaction spending the prevout fails to get into the mempool.

💬 Raimo33 commented on pull request "bench: replace embedded raw block with configurable block generator":
(https://github.com/bitcoin/bitcoin/pull/32554#issuecomment-3419716580)
Concept ACK for more realistic benchmarks

💬 sdaftuar commented on pull request "Cluster mempool":
(https://github.com/bitcoin/bitcoin/pull/33629#discussion_r2443345859)
Not sure I follow the reasoning here -- an RBF that fails due to cluster size limits might succeed if a child is added that adds additional conflicts, thereby making space in the affected cluster.

🚀 fanquake merged a pull request: "Update secp256k1 subtree to latest master"
(https://github.com/bitcoin/bitcoin/pull/33625)

✅ romanz closed a pull request: "index: store per-block transaction locations for efficient lookups"
(https://github.com/bitcoin/bitcoin/pull/32541)

💬 romanz commented on pull request "index: store per-block transaction locations for efficient lookups":
(https://github.com/bitcoin/bitcoin/pull/32541#issuecomment-3419729543)
Closing this PR, the "index-less" approach will be implemented in https://github.com/bitcoin/bitcoin/pull/33657.

💬 andrewtoth commented on pull request "validation: fetch block inputs on parallel threads >10% faster IBD":
(https://github.com/bitcoin/bitcoin/pull/31132#issuecomment-3419748327)
Updated to use `std::barrier` for the completion synchronization instead of acquiring a semaphore for each thread, as suggested by @l0rinc .