But the problem of confirmation time is not resolved by this. It might be passible with a warm store all in RAM, but not cold. I did some testing on just enumerating all of the input keys that are required to exercise the confirmation query, and even that is too much. So mitigation has to depend on not querying each input (or output) in the store for validation/confirmation. Keep in mind that storing the data requires no such enumeration, it can be almost entirely append.