Ripple CTO: It is still uncertain whether the network issue has been resolved or self-repaired

Ripple's Chief Technology Officer, David Schwartz, updated that it is still uncertain whether the network issue has been resolved or self-repaired. According to previous displays on the XRPL browser page, network activity froze for 64 minutes at block height 93927174 and then restarted at 10:58 AM UTC on February 4th.

David Schwartz added that if nodes know they cannot reach consensus with other nodes about the network status, four things will happen:

1. Nodes find a starting point they won't reach in advance;

2. Nodes try to find a location where normal operation can be resumed from the starting point or after;

3. Over time (ideally within 30 seconds), the network will reform at a safe and appropriate point;

4. Once a critical point is reached, they will jointly complete a round of consensus and release verification proving that this round of consensus has been successfully completed.