The views expressed in this article are those of the author and do not necessarily reflect the position of CoinGeek.
TL;DR: Satoshi Nakamoto created Bitcoin’s original alert system in 2010 to protect the network during emergencies, allowing trusted, signed warnings to reach nodes without interrupting mining. However, concerns over security and key management eventually led BTC Core to retire the system and publicly release its alert key. In contrast, BSV took a different approach by reintroducing an updated alert system with multiple key holders and additional safeguards, aiming to preserve Satoshi’s original vision of network security, accountability, and recovery.
Key Takeaways:
- Satoshi built the alert system in August 2010 for emergencies, allowing Bitcoin nodes to receive authoritative, signed warnings during critical network events.
- The original alert system allowed Satoshi to send signed network-wide warnings and temporarily restrict certain wallet functions without stopping mining.
- Bitcoin’s original alert system was used three times, successfully addressing protocol upgrades, a major blockchain fork, and the Heartbleed vulnerability.
- The alert key’s custody became uncertain after it was reportedly shared with multiple developers and ended up connected to Mt. Gox, raising serious security concerns.
- BTC Core retired the alert system in 2016, disabled it in 2017, and publicly released its private key in 2018, permanently undermining its ability to deliver trusted alerts.
- BSV reintroduced an updated alert system in 2024, using five key holders and a threshold-based structure to address the original system’s security and custody weaknesses.
- BSV preserves Satoshi’s original approach to emergency network protection, while BTC Core abandoned the mechanism because of failures in its management and security.
Two days ago, on October 31, 2026, the crypto press ran its annual White Paper Day routine: candle charts, a Saylor quote, “we are all Satoshi.” Yesterday was a quieter anniversary. On November 1, 2016, 10 years ago, bitcoin.org posted a notice titled “Alert System Retirement,” and the one instrument Satoshi Nakamoto built so an honest network could say “stop” began its eighteen-month execution.
Today is All Souls Day, when the Western Christian Church remembers its dead and listens for them. The grave I have in mind holds an instrument, not a man.
The alert key is the cleanest window we have into what BTC‘s maintainers decided Bitcoin is for. Satoshi built it under fire, in August 2010, ten days after he patched the worst bug in Bitcoin’s history, as his own answer to a question every money system eventually faces: what does an honest network do when something goes badly wrong?
Core answered that question differently. BSV answered it the way Satoshi did, and took the heat for it.
19 bad days
I wrote the summer of 2010 at length in Part 3 of my Written History of Bitcoin series at kurtwuckertjr.com, so if you want to learn about the chaos of that year, give it a read.
On July 28, 2010, an OP_1 OP_RETURN prefix turned out to make any script evaluate true, so anyone could spend anyone’s coins. Satoshi patched it within hours. On August 15, Jeff Garzik, one of the handful of developers then working alongside Satoshi, opened a bitcointalk thread called “Strange block 74638” because that block contained a transaction creating 184,467,440,737.09551616 BTC, two to the sixty-fourth satoshis. The sum had overflowed. Satoshi shipped v0.3.10 in about five hours, and the patched chain overtook the poisoned one at block 74,691.
CVE-2010-5139.
Same day, same man, commit 4bd188c, message: “misc changes.” That commit switched off roughly fifteen script opcodes (OP_CAT, OP_SUBSTR, OP_LSHIFT, OP_MUL and friends) as a denial-of-service precaution. BIP 347, the 2024 proposal to bring OP_CAT back to BTC, cites that exact commit by hash. BSV turned the opcodes back on in rolling updates between 2020 and 2026.
A 14-year detour, filed under “misc.”
Ten days later, on August 25, 2010, came the commitment that gave the network a voice. Title: “alert system.” Three safe-mode commits followed within the hour. It shipped in v0.3.11, and on August 27, Satoshi posted “Version 0.3.11 with upgrade alerts” to bitcointalk.
Three consensus-grade changes in 19 days, under fire, by one guy!
The fourth was the one that could talk to all nodes with authority.
What he actually built
His release post is tiny. “The alert system can display notifications on the status bar.” A line of text in your client. “In response to an alert, your node may also go into safe mode,” and safe mode disables the JSON-RPC send and balance commands “to protect it from losing money until you get a chance to upgrade.” If you disagreed with him, “you can use the switch -disablesafemode to re-enable them.” And the sentence the kill-switch crowd never quotes: “Nodes keep operating and do not stop generating in response to an alert.”
So the dreaded centralized override froze your wallet’s RPC send command, left mining untouched, and could be waved off with one flag. The purpose he gave was fork hygiene: the alert system “can make sure users are warned not to act on anything in the fork.” Even that much was gone by v0.3.20, when safe mode on alert was removed.
Garzik replied the same evening that alerts “are only accepted if signed by a specific key (held by satoshi)” and “cannot be generated by average nodes.” Did the cypherpunks riot? Did anyone call it a backdoor?
There was some bickering about it, but the answer is largely no, and one of the longer fights in that thread was about a compiler flag!
Two weeks earlier, on August 11, 2010, Satoshi was in a thread called “Escrow” defending the dullest possible escrow design, where “customer loses, but the thief doesn’t get the money either.” He wrote: “Imagine if gold turned to lead when stolen. If the thief gives it back, it turns to gold again.” He added that “money burning” was the wrong phrase because the funds were never truly destroyed.
Fourteen days after typing that, he built the signed network-wide warning, and the gold line comes back when this story reaches the BSV freeze. Stolen value going inert and coming back, and an honest network telling itself the truth in an emergency: those are not two topics.
Back to the top ↑
3 for 3
Satoshi never sent an alert. He left the project before he had to.
The first real alert went out on February 18, 2012, ahead of the February 20 protocol change. On March 12, 2013, during the 0.8 database fork, alert 1032 went out at priority 5000: “URGENT: chain fork, stop mining on version 0.8.” Two chains, a split network, healed inside a day, and the alert key is a large part of why. The last real alert was April 11, 2014, the Heartbleed upgrade notice.
Three uses, three successes, and not one false alarm or rogue message, ever! The known holders were Satoshi, Gavin Andresen, and theymos, the forum administrator.
Remember its successes, because the key was not killed for anything it did.
Back to the top ↑
Where it went
On September 10, 2016, on the bitcoin-dev list, Gregory Maxwell, Blockstream co-founder and Core contributor, wrote: “It was provided to MTGox by a developer.” (A developer. Singular. Unnamed then, unnamed since.) Then: “MTGox’s systems’ were compromised and later their CEO’s equipment taken by the Japanese police.” Mt. Gox‘s CEO was Mark Karpelès, arrested on August 1, 2015. So the key that could put a message on every Bitcoin node on earth sat on the equipment of the CEO of a compromised exchange, and then in a Tokyo evidence room.
Which developer handed it over? The thread does not say, and a decade later nobody has said…
Maxwell himself admitted, “No one can tell which of the key holders created a message.” Wladimir van der Laan, Core’s lead maintainer at the time: “no one can know who it has spread to over all those years.” Johnson Lau, another Core contributor: “We don’t know the actual date because the key is shared by many people.”
The maintainers of the most valuable open-source project in history could not tell you how many copies of their emergency key existed, or who had them.
Not exactly a clean chain of custody.
Back to the top ↑
The killing
Then came November 1, 2016 and the retirement notice, and bitcoin.org gave its reasons in its own words. The alert system “is a source of centralization” because “a single Alert Key can send network-wide alerts.”
“As more developers join, the Alert Key is given to others, but cannot be taken away from those who have left.” “This has led to the Alert Key potentially falling into the hands of malicious actors.” And it was no longer useful anyway, because users can get their news from major Bitcoin outlets (the press, in other words).
Every one of those sentences describes a custody failure by the people writing them. The key did not centralize itself. Nobody forced a developer to copy it to an exchange. And the proposed replacement for a cryptographically signed message from the protocol’s steward was checking Twitter…
From there, it runs like a demolition schedule. 2 November 2016: a pre-final alert. January 19, 2017: the final alert, which disabled the system and left every old node displaying a static message, “Alert Key Compromised.” March 8, 2017: Bitcoin Core 0.14 ships with that final alert hard-coded for legacy nodes. May 1, 2017: the planned release of the key is postponed, because “Older clients may contain Alert handling code which is exploitable using the alert key.” The code itself was already gone from Core 0.13.0.
Then on July 3, 2018, Bryan Bishop and Andrew Chow, two Core developers, published the private key, mainnet and testnet, on bitcoin.org. The stated reason was the key’s “unknown dissemination and proliferation.”
The logic is airtight in its way: if anyone can sign, no signature means anything.
The alert key was the network’s one channel for an authoritative warning, and the only instrument through which an author long gone from the project could ever have addressed every node at once. Core did not retire that channel. It published the key, so that any future message signed with it is indistinguishable from an impostor’s. That is not decommissioning a feature.
That is salting a grave.
Back to the top ↑
People I respect think a signed message makes BSV a permissioned network, and yes, it is controversial.
SV Node 1.1.0 reintroduced an alert system in early 2024, announced by BSV Association alongside the Network Access Rules (NAR) and Digital Asset Recovery (DAR). The Association’s hub says it takes “its name and general concept from the original Bitcoin alert key” but is “architecturally distinct”: a separate libp2p publish-subscribe topic, not the P2P relay. Informational messages are software updates and technical notices, which is exactly what Satoshi shipped in 0.3.11.
Core’s own reasons, one at a time. One key? BSV has five holders and a threshold. Cannot be taken away from those who left? Named parties under a published rule set, not a file that wandered onto an exchange server. The BSV design is not a copy of the 2010 key. It is a point-by-point answer to the way the 2010 key failed, which is more than the people who buried it ever attempted.
And what about freezing coins using a directive from NAR/DAR? Remember the escrow thread of August 11, 2010: gold turns to lead when stolen, and if the thief gives it back, it turns to gold again. A frozen output is lead, and a reassigned output under a court order is the gold coming back. Satoshi did not write that line about an alert system. He wrote it two weeks before he built one, defending a design where the thief ends up with nothing, but the victim can be made whole again.
You can dislike where BSV got the idea, but you cannot call the idea foreign to Bitcoin or its creator: Satoshi Nakamoto.
Back to the top ↑
The verdict
Strip the branding off.
Satoshi built a signed, network-wide warning himself, under fire, in the worst month of Bitcoin’s history. The key worked every time it was used, and it was killed for what it might do, after the people killing it had let it leak. And one chain decided the answer to “what happens when the money is stolen” was to publish the key and tell you to read the news, while the other rebuilt the instrument with the failure modes patched and a judge in the loop.
Core’s Bitcoin is the one where the author’s only emergency instrument lies buried under salted ground. BSV’s is the one where his actual answer to the emergency question is still running code, five signatures, and a court order away. Controversial? Sure. But it is All Souls Day, and I know which chain is still listening for a dead instrument and the idea it carried, and which one salted the ground so it would never have to.
Back to the top ↑
FAQs:
What was Bitcoin’s original alert system?
It is a mechanism created by Satoshi Nakamoto in 2010 to send signed emergency warnings to Bitcoin nodes.
Why did Satoshi create the alert system?
The alert system was created to protect users and the network during critical situations, such as protocol vulnerabilities and blockchain forks.
Why did BTC Core retire the alert system?
It was retired over concerns about centralization, compromised keys, and the inability to control who retained access to the alert key.
What happened to Bitcoin’s original alert key?
It was disabled in 2017 and publicly released in 2018, eliminating its ability to provide trusted alerts.
How does BSV’s alert system differ from the original?
It uses a separate communication channel, five designated key holders, and a threshold-based authorization structure designed to improve security and accountability.
This opinion piece is published to encourage discussion. The author’s views are their own and do not constitute legal, procurement, or policy advice, nor do they represent the positions of CoinGeek or its partners.
Back to the top ↑
Watch | DigiCon 2026: Interoperability starts with people
Nuoroda į informacijos šaltinį