We've never run any tests on this number or worked to find out at what point it starts failing to resolve. #274 suggests 10%, as it doesn't need such a high margin of error, yet it also has a lack of evidence.
This isn't hardcoded into the protocol, so we can change it in any node release (or even via a config file).
We've never run any tests on this number or worked to find out at what point it starts failing to resolve. #274 suggests 10%, as it doesn't need such a high margin of error, yet it also has a lack of evidence.
This isn't hardcoded into the protocol, so we can change it in any node release (or even via a config file).