How does Kaspa keep running during a network outage?

When part of the Kaspa network loses connectivity, the protocol degrades gracefully rather than failing catastrophically. Each isolated segment keeps producing local consensus — nodes don't halt, crash, or roll back. Once the connection restores, the separated segments reconcile automatically, merging their work without manual intervention. This behavior is built into the protocol's mathematical foundation, not bolted on afterward. For a beginner, this means a connectivity hiccup — whether a data-center outage or a regional internet disruption — does not freeze the chain or erase transaction history.