Sep 19, 2026

All of the various network management methods are now implemented in bitcoind and btcd. I only rejected one, and none are partial. The rejection is getblockfrompeer, as I can find no scenario where it makes sense. It implies we have a header, and want a block, and aren't getting it so it's holding us up, and there's a given peer that we are already connected to that we know has it so we'll make that request and stuff it into the store if it succeeds (otherwise nothing). We already make requests to all the peers we are connected to (and can get connected to) to find a block that isn't being found. This seems to be some kind of test hack and maybe an assumeutxo hack and maybe a hack to unstick a stalled sync (even though it will eventually move to other nodes). One of the dumbest I've found, but in this case there's also no way to make sense of it given our architecture.