Does the current implementation support reading and writing historical versions of the same key at different block heights? It seems that current Entry has not yet implemented the OldId described in the paper, so it always returns the value of a key at the latest block height and updates the indexer in-place.