2 ms·
I don't think it was a symptom of routing synchronization specifically, but I'd be curious to know if it was a case of unexpected and undesired synchronization.
by pumpmylemma 15y ago
I don't think it was a symptom of routing synchronization specifically, but I'd be curious to know if it was a case of unexpected and undesired synchronization. (E.G. An independent and random cluster of blocks suddenly updated; the network was saturated; it pulled in more updates; ...)
And yes, the paper talked about randomization. It also pointed out the magnitude of randomization required was larger than expected.
- pandakar 15y agoHas there been an official explanation?
- pumpmylemma 15y agoAs far as I'm aware, no. That's why RightAWS said they get an F for communication.