Feb 8, 2025

I completed the confirmation change last night that we discussed at the last meeting. That took about 24 hours and worked out a little simpler than I expected. Turns out there is no index change necessary to optimize strong_tx queries during confirmation, those can remain indexed against the tx table primary key, since we must identify all spends of the same point by hash, and those resolve directly to the spending tx pk. The run completed on the maxi in similar time to previous runs without the change. Testing now on the mini. Also, I'm starting to see that there is a way to get more concurrency out of confirmation, and probably also resolve the thrashing for certain. Spending some time on that now.