With the validation chaser working I'm moving on to the confirmation chaser. That's the last one for full validating sync. The others are tx pooling and block template generation (both for mining and not present in v3). Confirmation is always sequential, so basically the node will be fully functionally soon, and I'll be able to dedicate all efforts toward optimizing concurrent validation. This includes fan-out by tx with result aggregation by block, a moving download window to reduce the maximum blockage waiting on a gapped block download, automation of background snapshots, and automated store sizing configuration. These last two should be able fully manage the problem of excess paging (it's doing great presently).