From 1dbc2cc5ea28e815b580334fe1fd77cc4f73fe3d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?L=C5=91rinc?= Date: Thu, 2 Jul 2026 15:41:16 -0700 Subject: [PATCH] doc: update Bitcoin Core RPC scaling note The bitcoind_clients sample config described a stale global-lock bottleneck for parallel block downloads. Replace the stale warning with a versioned note that Bitcoin Core v25 improved RPC getblock scaling. Co-authored-by: Andrew Toth --- doc/fulcrum-example-config.conf | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/doc/fulcrum-example-config.conf b/doc/fulcrum-example-config.conf index 088b82be..a3223f84 100644 --- a/doc/fulcrum-example-config.conf +++ b/doc/fulcrum-example-config.conf @@ -577,10 +577,8 @@ rpcpassword = hunter1 # -rpcthreads option in bitcoind) may yield better parallelism during initial DB # synch as well as better performance for your clients. This number should not # exceed the number of cores in your system, however, as performance may suffer -# in that case. Note that Bitcoin Core doesn't parallelize very well on its -# `getblocks` call due to the way it holds a global lock throughout the entire -# call, so if you are on BTC, your mileage may vary with how much extra -# performance you can get from more simultaneous clients specified here. +# in that case. Note that Bitcoin Core didn't parallelize RPC `getblock` calls +# very well before v25. # #bitcoind_clients = 3