We want to track pruned confirmed transaction hashes to a cuckoo filter before we delete them.
At the end of each pruning cycle we want to persist the cuckoo filter state in the db
Motivation
We want to be able to recognize pruned txs that we receive again via gossip
Requirements
When we prune a transaction we add its hash to the cuckoo filter
We create a new db for cuckoo filter state and update it
Open Questions (optional)
Should we really create a new db instance?
I think it will result in better performance and easier debugging
Description
We want to track pruned confirmed transaction hashes to a cuckoo filter before we delete them. At the end of each pruning cycle we want to persist the cuckoo filter state in the db
Motivation
We want to be able to recognize pruned txs that we receive again via gossip
Requirements
Open Questions (optional)
Should we really create a new db instance? I think it will result in better performance and easier debugging