Then you realize you need to store this confirmation_state somewhere, and realize it's just an association table between confirmed tx and header. So that's great, you also get reverse navigation for confirmed transactions, a query server bonus. Then you realize, holy crap that's a really big query resulting from elimination of the utxo store. Yep, that's where the true cost of validation concurrency rears its ugly head. So you think hard about how to make a store that is ridiculously fast. You cone to grips with the fact that no generalized database software is going to do that nearly as fast as a specialized append only set of in-memory hashmaps. And then you decided that mmap will make this possible, but has some serious drawbacks.