Instead of stopping if it encounters a "sufficient" number of transactions which don't meet the threshold for being confirmed within the target, it keeps looking to add more transactions to see if there is a temporary blip in the data. This allows a smaller number of required data points.pull/365/head
parent
d3e30bca1b
commit
1ba43cc0ec
Loading…
Reference in new issue