Oct 29, 2024

All is now good, and it's time to deal with that issue of tossing out the utxo store, which inherently assures confirmed and not double spent previous outputs. This then requires that as concurrent validation jobs complete, something must synchronize them (put them in order) for the purpose of verifying output confirmability. So another chaser is in order, this one requiring a total order over blocks (one block verified at a time). But then another problem. How do you know that a previous output recovered from the input point search is confirmed (prior, since the order is imposed by the chaser)? There are blocks that are being downloaded (and/or validated) well past the height of this confirmability point, that's what makes it concurrent! So you must be able to navigate from the previous output to its confirmed state (these states being set for future blocks during this same phase).