So...... thinking on reducing processing time, I am wandering, and please correct me if I am wrong, that actually we don't need to go through the whole transaction history of an address to get the right RSZ etc, that are needed. Since if an address has a double R vulnerability then, all we need is just 2 outgoing transactions data right?
So to summarize, no matter how many transaction an address has (sometimes hundreds of thousands), we could limit the amount of data inquiry to limiting the checking of its transactions to say 100 transaction only, because if it has the double R vulnerability it will appear in any 2 outgoing transaction. Really we could limited to just 4 transactions per address, you get my point?
So...... thinking on reducing processing time, I am wandering, and please correct me if I am wrong, that actually we don't need to go through the whole transaction history of an address to get the right RSZ etc, that are needed. Since if an address has a double R vulnerability then, all we need is just 2 outgoing transactions data right?
So to summarize, no matter how many transaction an address has (sometimes hundreds of thousands), we could limit the amount of data inquiry to limiting the checking of its transactions to say 100 transaction only, because if it has the double R vulnerability it will appear in any 2 outgoing transaction. Really we could limited to just 4 transactions per address, you get my point?