Sep 1, 2026

I've been working my way through the bitcoind endpoint surface. It's sprawling, but our frameworks have been accommodating it nicely. Last week I added a high performance scan to produce unspent and unspendable totals at a given block height. That was the only thing that the utxo accumulator model provided that we don't already index for. But since this is really only an administrative function (satisfying curiosity), there's no reason to cache it. We won't be supporting any wallet methods that require the presence of the bitcoind wallet, or that require submission of a private key to the server. There is actually a set of RPC functions for performing pure computation for PSBT, and I've added those. But have rejected the two of those that performing signing and therefore require private key transmission. All of these can be one locally by a client/wallet - in no way requiring a node.