why does the txindex and blockfilter index try to "keep in sync" why not just check every block in the currently active chain when we start and then deal with changes? they both use leveldb so can easily tell a consumer whether they have that particular block in the index
i guess for txindex it would be kind of annoying to have a partial index
phantomcircuit: I'm not clear what you're suggesting to do different
luke-jr, at least for the block filter index, instead of keeping track of the "tip" just walk the current chain and try to rebuild
it makes something that's O(1) O(n) but it means it's more flexible
phantomcircuit: it's not clear to me how that would be practically different
you mean how you could have some blocks indexed and others not?