Alert system - Revision history

Luke-jr: Reverted edits by AllEd01 (talk) to last revision by Theymos

2022-07-11T23:59:06Z

Reverted edits by AllEd01 (talk) to last revision by Theymos

← Older revision		Revision as of 23:59, 11 July 2022
Line 17:		Line 17:
	* The alert text.		* The alert text.

	Only alerts that are signed by a specific ECDSA public key are considered valid. Some known private ~~keyholders~~ were [[Satoshi Nakamoto]], [[User:gavinandresen\|Gavin Andresen]] and [[User:Theymos\|theymos]], but the private key was made public after the alert system was retired, so there is no longer any special group of alert-key-holders.		Only alerts that are signed by a specific ECDSA public key are considered valid. Some known private key holders were [[Satoshi Nakamoto]], [[User:gavinandresen\|Gavin Andresen]] and [[User:Theymos\|theymos]], but the private key was made public after the alert system was retired, so there is no longer any special group of alert-key-holders.

	===Safe mode===		===Safe mode===

AllEd01: corrected spelling

2022-06-29T20:21:05Z

corrected spelling

← Older revision		Revision as of 20:21, 29 June 2022
Line 17:		Line 17:
	* The alert text.		* The alert text.

	Only alerts that are signed by a specific ECDSA public key are considered valid. Some known private ~~key holders~~ were [[Satoshi Nakamoto]], [[User:gavinandresen\|Gavin Andresen]] and [[User:Theymos\|theymos]], but the private key was made public after the alert system was retired, so there is no longer any special group of alert-key-holders.		Only alerts that are signed by a specific ECDSA public key are considered valid. Some known private keyholders were [[Satoshi Nakamoto]], [[User:gavinandresen\|Gavin Andresen]] and [[User:Theymos\|theymos]], but the private key was made public after the alert system was retired, so there is no longer any special group of alert-key-holders.

	===Safe mode===		===Safe mode===

Theymos: Mention that it was published

2018-09-13T07:05:55Z

Mention that it was published

← Older revision		Revision as of 07:05, 13 September 2018
Line 17:		Line 17:
	* The alert text.		* The alert text.

	Only alerts that are signed by a specific ECDSA public key are considered valid. Some known private key holders ~~are~~ [[Satoshi Nakamoto]], [[User:gavinandresen\|Gavin Andresen]] and [[User:Theymos\|theymos]]~~. There are other people able to issue alerts in~~ the ~~event of~~ the ~~incapacitation~~ of ~~the aforementioned.<ref>http://www.reddit~~.~~com/r/Bitcoin/comments/2dz9ri/why_in_the_world_does_theymos_have_the_private/cjuu360</ref>~~		Only alerts that are signed by a specific ECDSA public key are considered valid. Some known private key holders were [[Satoshi Nakamoto]], [[User:gavinandresen\|Gavin Andresen]] and [[User:Theymos\|theymos]], but the private key was made public after the alert system was retired, so there is no longer any special group of alert-key-holders.

	===Safe mode===		===Safe mode===
Line 37:		Line 37:
	In 2016, the alert system was retired<ref name="org"/> because of the possibility of privileged users sending political alert messages, <!-- because of consensus that there shouldn't be privileged users in a decentralized system in the first place, [reword?]--> and because of the possibility of the alert key having been taken from [[Mark Karpelès]] by the Japanese police in 2014.<ref>https://github.com/bitcoin/bitcoin/pull/7692</ref>		In 2016, the alert system was retired<ref name="org"/> because of the possibility of privileged users sending political alert messages, <!-- because of consensus that there shouldn't be privileged users in a decentralized system in the first place, [reword?]--> and because of the possibility of the alert key having been taken from [[Mark Karpelès]] by the Japanese police in 2014.<ref>https://github.com/bitcoin/bitcoin/pull/7692</ref>

	The alert key was scheduled to be released to the public in May 2017, but this ~~has since been~~ postponed.<ref name="org"/>		The alert key was scheduled to be released to the public in May 2017, but this was postponed.<ref name="org"/> It was eventually published in July 2018.

	===Past alerts===		===Past alerts===

Belcher: /* See Also */ added link to pull request where removing the alert system was discussed

2018-03-22T15:54:38Z

See Also: added link to pull request where removing the alert system was discussed

← Older revision		Revision as of 15:54, 22 March 2018
Line 135:		Line 135:

	==See Also==		==See Also==

			* https://github.com/bitcoin/bitcoin/pull/7692 - The pull request where removing the alert system from [[Bitcoin Core]] was discussed

	[[Category:Technical]]		[[Category:Technical]]

Taras at 00:51, 27 July 2017

2017-07-27T00:51:22Z

← Older revision		Revision as of 00:51, 27 July 2017
Line 1:		Line 1:
	Bitcoin versions 0.3.10 introduced an '''alert system''' which ~~allows~~ messages about critical network problems to be broadcast to all clients.		[[File:Prefinal alert.png\|thumb\|300px\|The prefinal alert message in the status bar of the GUI client]]Bitcoin versions 0.3.10 introduced an '''alert system''' which allowed messages about critical network problems to be broadcast to all clients.

	The alert system has been completely retired.<ref>https://bitcoin.org/en/alert/2016-11-01-alert-retirement</ref>. The code was removed since 0.13.0 and since 0.14.0 any old nodes will receive a static hard-coded "Alert Key Compromised" message.		The alert system has been completely retired.<ref name="org">https://bitcoin.org/en/alert/2016-11-01-alert-retirement</ref> The code was removed since 0.13.0 and since 0.14.0 any old nodes will receive a static hard-coded "Alert Key Compromised" message.

	~~[[File:Prefinal alert.png\|thumb\|300px\|The prefinal alert message in the status bar of the GUI client]]~~

	When an alert was in effect, the message it contains would appear in the status bar of all clients and in the "errors" field of RPC ''getinfo''. Any script registered with the <code>-alertnotify</code> command-line option will be notified.		When an alert was in effect, the message it contains would appear in the status bar of all clients and in the "errors" field of RPC ''getinfo''. Any script registered with the <code>-alertnotify</code> command-line option will be notified.
Line 19:		Line 17:
	* The alert text.		* The alert text.

	Only alerts that are signed by a specific ECDSA public key are considered valid. ~~The~~ known private key holders are [[Satoshi Nakamoto]], [[User:gavinandresen\|Gavin Andresen]] and [[User:Theymos\|theymos]]. There are other people able to issue alerts in the event of the incapacitation of the aforementioned.<ref>http://www.reddit.com/r/Bitcoin/comments/2dz9ri/why_in_the_world_does_theymos_have_the_private/cjuu360</ref>		Only alerts that are signed by a specific ECDSA public key are considered valid. Some known private key holders are [[Satoshi Nakamoto]], [[User:gavinandresen\|Gavin Andresen]] and [[User:Theymos\|theymos]]. There are other people able to issue alerts in the event of the incapacitation of the aforementioned.<ref>http://www.reddit.com/r/Bitcoin/comments/2dz9ri/why_in_the_world_does_theymos_have_the_private/cjuu360</ref>

	===Safe mode===		===Safe mode===


	Until version 0.3.20, Bitcoin went into safe mode when a valid alert was received. In safe mode, all RPC commands that send BTC or get info about received BTC return an error. Current Bitcoin versions no longer go into safe mode in response to alerts, though Bitcoin ''will'' still go into safe mode when it detects on its own that something is seriously wrong with the network.		Until version 0.3.20, Bitcoin went into safe mode when a valid alert was received. In safe mode, all RPC commands that send BTC or get info about received BTC return an error. Current Bitcoin versions no longer go into safe mode in response to alerts, though Bitcoin ''will'' still go into safe mode when it detects on its own that something is seriously wrong with the network.

Line 38:		Line 34:

	The alert system was hastily implemented by [[Satoshi Nakamoto]] after the [[value overflow incident]] on August 15, 2010. Satoshi never actually used this system; it remained dormant until the [[February 20, 2012 protocol change]], for which an alert was issued on February 18.<ref>[https://bitcoin.org/en/alert/2012-02-18-protocol-change February 20, 2012 Protocol Changes] at bitcoin.org</ref>		The alert system was hastily implemented by [[Satoshi Nakamoto]] after the [[value overflow incident]] on August 15, 2010. Satoshi never actually used this system; it remained dormant until the [[February 20, 2012 protocol change]], for which an alert was issued on February 18.<ref>[https://bitcoin.org/en/alert/2012-02-18-protocol-change February 20, 2012 Protocol Changes] at bitcoin.org</ref>

			In 2016, the alert system was retired<ref name="org"/> because of the possibility of privileged users sending political alert messages, <!-- because of consensus that there shouldn't be privileged users in a decentralized system in the first place, [reword?]--> and because of the possibility of the alert key having been taken from [[Mark Karpelès]] by the Japanese police in 2014.<ref>https://github.com/bitcoin/bitcoin/pull/7692</ref>

			The alert key was scheduled to be released to the public in May 2017, but this has since been postponed.<ref name="org"/>

	===Past alerts===		===Past alerts===

Belcher: updated text saying the alert system has been completely retired

2017-07-04T15:43:39Z

updated text saying the alert system has been completely retired

← Older revision		Revision as of 15:43, 4 July 2017
Line 1:		Line 1:
	Bitcoin versions 0.3.10 introduced an '''alert system''' which allows messages about critical network problems to be broadcast to all clients.		Bitcoin versions 0.3.10 introduced an '''alert system''' which allows messages about critical network problems to be broadcast to all clients.

	The alert system has been ~~removed since 0.13~~.~~0 and is planned to be entirely deprecated~~<ref>https://bitcoin.org/en/alert/2016-11-01-alert-retirement</ref>.		The alert system has been completely retired.<ref>https://bitcoin.org/en/alert/2016-11-01-alert-retirement</ref>. The code was removed since 0.13.0 and since 0.14.0 any old nodes will receive a static hard-coded "Alert Key Compromised" message.

	[[File:Prefinal alert.png\|thumb\|300px\|The prefinal alert message in the status bar of the GUI client]]		[[File:Prefinal alert.png\|thumb\|300px\|The prefinal alert message in the status bar of the GUI client]]

934: layout

2016-11-26T12:47:26Z

layout

← Older revision		Revision as of 12:47, 26 November 2016
Line 1:		Line 1:
	~~{{multiple image\|align=vertical\|width=300~~
	~~\|image1=alert.png~~
	~~\|image2=bitcoin-alert-cli.png~~
	~~\|footer=An alert appearing on bitcoin clients~~
	}}
	Bitcoin versions 0.3.10 introduced an '''alert system''' which allows messages about critical network problems to be broadcast to all clients.		Bitcoin versions 0.3.10 introduced an '''alert system''' which allows messages about critical network problems to be broadcast to all clients.

Line 27:		Line 22:

	===Safe mode===		===Safe mode===


	Until version 0.3.20, Bitcoin went into safe mode when a valid alert was received. In safe mode, all RPC commands that send BTC or get info about received BTC return an error. Current Bitcoin versions no longer go into safe mode in response to alerts, though Bitcoin ''will'' still go into safe mode when it detects on its own that something is seriously wrong with the network.		Until version 0.3.20, Bitcoin went into safe mode when a valid alert was received. In safe mode, all RPC commands that send BTC or get info about received BTC return an error. Current Bitcoin versions no longer go into safe mode in response to alerts, though Bitcoin ''will'' still go into safe mode when it detects on its own that something is seriously wrong with the network.

Line 34:		Line 31:

	==History==		==History==
			{{multiple image\|align=vertical\|width=300
			\|image1=alert.png
			\|image2=bitcoin-alert-cli.png
			\|footer=An alert appearing on bitcoin clients
			}}

	The alert system was hastily implemented by [[Satoshi Nakamoto]] after the [[value overflow incident]] on August 15, 2010. Satoshi never actually used this system; it remained dormant until the [[February 20, 2012 protocol change]], for which an alert was issued on February 18.<ref>[https://bitcoin.org/en/alert/2012-02-18-protocol-change February 20, 2012 Protocol Changes] at bitcoin.org</ref>		The alert system was hastily implemented by [[Satoshi Nakamoto]] after the [[value overflow incident]] on August 15, 2010. Satoshi never actually used this system; it remained dormant until the [[February 20, 2012 protocol change]], for which an alert was issued on February 18.<ref>[https://bitcoin.org/en/alert/2012-02-18-protocol-change February 20, 2012 Protocol Changes] at bitcoin.org</ref>

934: retired

2016-11-26T12:45:20Z

retired

← Older revision		Revision as of 12:45, 26 November 2016
Line 4:		Line 4:
	\|footer=An alert appearing on bitcoin clients		\|footer=An alert appearing on bitcoin clients
	}}		}}
	Bitcoin versions 0.3.10 ~~and later have~~ an '''alert system''' which allows messages about critical network problems to be broadcast to all clients. When an alert is in effect, the message it contains ~~will~~ appear in the status bar of all clients and in the "errors" field of RPC ''getinfo''. Any script registered with the <code>-alertnotify</code> command-line option will be notified.		Bitcoin versions 0.3.10 introduced an '''alert system''' which allows messages about critical network problems to be broadcast to all clients.

			The alert system has been removed since 0.13.0 and is planned to be entirely deprecated<ref>https://bitcoin.org/en/alert/2016-11-01-alert-retirement</ref>.

			[[File:Prefinal alert.png\|thumb\|300px\|The prefinal alert message in the status bar of the GUI client]]

			When an alert was in effect, the message it contains would appear in the status bar of all clients and in the "errors" field of RPC ''getinfo''. Any script registered with the <code>-alertnotify</code> command-line option will be notified.

	===Alert message===		===Alert message===

Harding: Added Bitcoin Core documentation navbox

2015-08-17T15:57:32Z

Added Bitcoin Core documentation navbox

← Older revision		Revision as of 15:57, 17 August 2015
Line 135:		Line 135:
	==External links==		==External links==
	https://bitcoin.org/en/alerts		https://bitcoin.org/en/alerts

			{{Bitcoin Core documentation}}

Taras at 20:44, 16 August 2015

2015-08-16T20:44:28Z

← Older revision		Revision as of 20:44, 16 August 2015
Line 4:		Line 4:
	\|footer=An alert appearing on bitcoin clients		\|footer=An alert appearing on bitcoin clients
	}}		}}
	Bitcoin versions 0.3.10 and later have an alert system which allows messages about critical network problems to be broadcast to all clients. When an alert is in effect, the message it contains will appear in the status bar of all clients, in the "errors" field of RPC ''getinfo''~~, and will notify any~~ script registered with ~~Bitcoin~~-Qt/~~bitcoind -alertnotify~~ command-line option.		Bitcoin versions 0.3.10 and later have an '''alert system''' which allows messages about critical network problems to be broadcast to all clients. When an alert is in effect, the message it contains will appear in the status bar of all clients and in the "errors" field of RPC ''getinfo''. Any script registered with the <code>-alertnotify</code> command-line option will be notified.

	===Alert message===		===Alert message===
Line 26:		Line 26:

	To test safe mode, run Bitcoin with the -testsafemode switch. To override a real safe mode event, run Bitcoin with the -disablesafemode switch.		To test safe mode, run Bitcoin with the -testsafemode switch. To override a real safe mode event, run Bitcoin with the -disablesafemode switch.

			==History==
			The alert system was hastily implemented by [[Satoshi Nakamoto]] after the [[value overflow incident]] on August 15, 2010. Satoshi never actually used this system; it remained dormant until the [[February 20, 2012 protocol change]], for which an alert was issued on February 18.<ref>[https://bitcoin.org/en/alert/2012-02-18-protocol-change February 20, 2012 Protocol Changes] at bitcoin.org</ref>

	===Past alerts===		===Past alerts===