View in context in the libbitcoin Slack #general mirror.
op_check_sig_verify and op_check_multisig_verify . This machine can sync and validate the full chain in about 5 hours with the current build, but running after sync is better for smaller machines that already have CPU maxed out and/or are subject to thrashing in this heavy read/write scenario due to low/slow RAM/SSD.
So I'm going to make that choice a boolean config option, and while I'm at it will add the same for enabling confirmability checks. Since I've per-analyzed the variations on fan out, and a lot of tuning on both of these aspects, automating that choice is really the last big item in sync.