You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 23, 2020. It is now read-only.
While solidifying transactions we might start requesting old transactions that have been pruned.
We want to stop once we recognize this.
Motivation
Optimization
Requirements
When we check solidity and we encounter a tx that is in the Cuckoo filter we set a deletedScore to 1.
We don't persist the tx but save it in local memory
We start to recursively request its parents and if they are also in the cuckoo filter increment deletedProbability.
If we reach a score of 10 we abort.
If we find one parent that is not in the cuckoo filter we assume that the rest are false positives.
Open Questions (optional)
Do we need to clear the cuckoo filter of extremely old txs in order to decrease false positive rates?
The text was updated successfully, but these errors were encountered:
Description
While solidifying transactions we might start requesting old transactions that have been pruned.
We want to stop once we recognize this.
Motivation
Optimization
Requirements
deletedScore
to 1.We don't persist the tx but save it in local memory
deletedProbability
.Open Questions (optional)
Do we need to clear the cuckoo filter of extremely old txs in order to decrease false positive rates?
The text was updated successfully, but these errors were encountered: