The Shutdown Problem: How Does a Blockchain System End?

TL;DR

This paper explores the challenges of gracefully shutting down blockchain systems, especially those with long-term archival data, and discusses strategies like hard forks to achieve stable consensus at end-of-life.

Contribution

It defines the shutdown problem for blockchain systems, analyzes the difficulties posed by decentralized and unstable consensus mechanisms, and offers recommendations for managing end-of-life scenarios.

Findings

Shutdown is difficult due to decentralization and unstable consensus.

Stable consensus is crucial for long-term archival data.

Hard forks can facilitate graceful shutdowns.

Abstract

We define and examine the shutdown problem for blockchain systems: how to gracefully end the system's operation at the end of its useful life. A particular focus is those blockchain systems that hold archival data of long-lived interest. We outline what it means to achieve a successful shutdown, and compare those criteria to likely end-of-life conditions in a generic blockchain system. We conclude that the decentralized nature of blockchain systems makes shutdown difficult, particularly if the system uses an unstable consensus like the Nakamoto consensus of Bitcoin. Accordingly, we recommend against using blockchain with unstable consensus for any data whose value is likely to persist beyond the life of the blockchain system. For any such systems that are already in operation, we recommend considering a hard fork to implement stable consensus. Such consideration needs to happen well in advance of the system's end of life.