https://en.bitcoin.it/w/api.php?action=feedcontributions&user=Flyingkiwiguy&feedformat=atomBitcoin Wiki - User contributions [en]2024-03-29T04:57:24ZUser contributionsMediaWiki 1.30.0https://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=47774Alerts mailing list2014-05-31T15:31:26Z<p>Flyingkiwiguy: Replaced content with "This service is no longer offered."</p>
<hr />
<div>This service is no longer offered.</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alert_system&diff=47773Alert system2014-05-31T15:30:21Z<p>Flyingkiwiguy: /* See Also */</p>
<hr />
<div>[[File:alert.png|thumb|300px|right]]<br />
<br />
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.<br />
<br />
[[File:Bitcoin-alert-cli.png|thumb|300px|right]]<br />
<br />
===Alert message===<br />
Alerts are broadcast using the same [[network|TCP relay system]] as ''block'' and ''tx'' messages. They are not encoded in a special transaction. Unlike block and tx relaying, alerts are sent at the start of every new connection for as long as the alert is in effect. This ensures that everyone receives the alert.<br />
<br />
Alerts contain this information:<br />
* How long to relay the alert.<br />
* How long to consider the alert valid.<br />
* An alert ID number.<br />
* A list of alerts that should be canceled upon receipt of this alert.<br />
* Exactly which versions of Bitcoin are affected by the alert. Unaffected versions still relay the alert for the benefit of older versions.<br />
* Alert priority.<br />
* The alert text.<br />
<br />
Only alerts that are signed by a specific ECDSA public key are considered valid. A copy of the private key is held by at least Satoshi, Gavin, and theymos.<br />
<br />
===Safe mode===<br />
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.<br />
<br />
Even though Bitcoin no longer automatically disables RPC when an alert is live, it is wise for Bitcoin sites to shut down when an alert has been issued. To detect an active alert, poll the "errors" field of ''getinfo''.<br />
<br />
To test safe mode, run Bitcoin with the -testsafemode switch. To override a real safe mode event, run Bitcoin with the -disablesafemode switch.<br />
<br />
===Past alerts===<br />
{| class="wikitable" border="1"<br />
|-<br />
! ID<br />
! Sent date<br />
! Expires (UTC)<br />
! Versions<br />
! Priority<br />
! Message<br />
|-<br />
| 1010<br />
| Feb 18, 2012<br />
| Feb 21 02:47:15<br />
| All<br />
| 100<br />
| See bitcoin.org/feb20 if you have trouble connecting after 20 February<br />
|-<br />
| 1011<br />
| Mar 16, 2012<br />
| cancelled May 15, 2012<br />
| 0.5 - 0.5.3<br />
| 5000<br />
| URGENT: security fix for Bitcoin-Qt on Windows: http://bitcoin.org/critfix<br />
|-<br />
| 1012<br />
| Mar 16, 2012<br />
| cancelled May 15, 2012<br />
| 6.0<br />
| 5000<br />
| URGENT: security fix for Bitcoin-Qt on Windows: http://bitcoin.org/critfix<br />
|-<br />
| 1013<br />
| Mar 16, 2012<br />
| cancelled May 15, 2012<br />
| 5.99<br />
| 5000<br />
| URGENT: security fix for Bitcoin-Qt on Windows: http://bitcoin.org/critfix<br />
|-<br />
| 1015<br />
| May 15, 2012<br />
| May 16, 2013<br />
| 0.1 - 0.4.5<br />
| 5000<br />
| URGENT: upgrade required, see http://bitcoin.org/dos for details<br />
|-<br />
| 1016<br />
| May 15, 2012<br />
| May 16, 2013<br />
| 0.4.99 - 0.5.4<br />
| 5000<br />
| URGENT: upgrade required, see http://bitcoin.org/dos for details<br />
|-<br />
| 1020<br />
| May 15, 2012<br />
| May 16, 2013<br />
| 0.6.0<br />
| 5000<br />
| URGENT: upgrade required, see http://bitcoin.org/dos for details<br />
|-<br />
| 1032<br />
| March 12, 2013<br />
| March 13, 2013<br />
| 0.8.0<br />
| 5000<br />
| URGENT: chain fork, stop mining on version 0.8<br />
|-<br />
| 1033<br />
| March 19, 2013<br />
| March 20, 2013<br />
| 0.1 - 0.7.2<br />
| 10<br />
| See http://bitcoin.org/may15.html for an important message<br />
|-<br />
| 1034<br />
| May 9, 2013<br />
| June 8, 2013<br />
| 0.1 - 0.7.2<br />
| 10<br />
| Action required: see http://bitcoin.org/may15.html for more information<br />
|-<br />
| 1040<br />
| April 11, 2014<br />
| cancelled<br />
| 0.9.0<br />
| 5000<br />
| URGENT: Upgrade required: see https://www.bitcoin.org/heartbleed/<br />
|-<br />
| 1041<br />
| April 11, 2014<br />
| April 11, 2015<br />
| 0.9.0<br />
| 5000<br />
| URGENT: Upgrade required: see https://www.bitcoin.org/heartbleed<br />
|}<br />
<br />
==See Also==<br />
<br />
[[Category:Technical]]<br />
[[Category:Vocabulary]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=36170Alerts mailing list2013-03-17T10:09:03Z<p>Flyingkiwiguy: </p>
<hr />
<div><br />
The Bitcoin [[Protocol specification]] supports the broadcast of [[Alerts]]. An unofficial email relay is now provided that rebroadcasts these [[block chain]] related alerts. To subscribe via email send an email to '''bitcoin-unofficial-alerts+subscribe@googlegroups.com''' [mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com] and you should receive an email asking you to verify your subscription.<br />
<br />
Alternatively, you can browse to the Google Group for the list [https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts]. By default Google Groups does not send emails, so when you sign up you will likely want to choose to get notifications via email.<br />
<br />
==Verify alerts and obtain the latest status information==<br />
If you receive an alert you should '''immediately verify it is official''' by running "bitcoind getinfo" (but see notes below), go to bitcoin.org [http://www.bitcoin.org] to obtain more details and background, or join the #bitcoin [[IRC channels]] on freenode to obtain the latest information.<br />
<br />
==Notes==<br />
*Alerts are broadcast to a specified range of Bitcoin versions.<br />
*The email relay uses a specially patched version of bitcoind that should report and therefore relay ''any'' alert broadcast for ''any'' version.<br />
*You will therefore have to verify whether or not the alert is actually relevant to your particular version of Bitcoin client.<br />
*Alerts are also independent of blocks or transactions, and have a defined time-to-live.<br />
*The email relay polls bitcoind every six minutes.<br />
<br />
==Feedback==<br />
Please send any comments or requests to Gary Mulder [mailto:flyingkiwiguy@gmail.com].<br />
<br />
[[Category:Services]]<br />
[[Category:Developer]]<br />
[[Category:ECommerce]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=36169Alerts mailing list2013-03-17T09:58:40Z<p>Flyingkiwiguy: </p>
<hr />
<div><br />
The Bitcoin [[Protocol specification]] supports the broadcast of [[Alerts]]. An unofficial email relay is now provided that rebroadcasts these [[block chain]] related alerts via subscription to the bitcoin unofficial alert mailing list [https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts]. Alternatively, to subscribe via email send an email to '''bitcoin-unofficial-alerts+subscribe@googlegroups.com''' [mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com] and you should receive an email asking you to verify your subscription.<br />
<br />
==Verify alerts and obtain the latest status information==<br />
If you receive an alert you should '''immediately verify it is official''' by running "bitcoind getinfo" (but see notes below), go to bitcoin.org [http://www.bitcoin.org] to obtain more details and background, or join the #bitcoin [[IRC channels]] on freenode to obtain the latest information.<br />
<br />
==Notes==<br />
*Alerts are broadcast to a specified range of Bitcoin versions.<br />
*The email relay uses a specially patched version of bitcoind that should report and therefore relay ''any'' alert broadcast for ''any'' version.<br />
*You will therefore have to verify whether or not the alert is actually relevant to your particular version of Bitcoin client.<br />
*Alerts are also independent of blocks or transactions, and have a defined time-to-live.<br />
*The email relay polls bitcoind every six minutes.<br />
<br />
==Feedback==<br />
Please send any comments or requests to Gary Mulder [mailto:flyingkiwiguy@gmail.com].<br />
<br />
[[Category:Services]]<br />
[[Category:Developer]]<br />
[[Category:ECommerce]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=36165Alerts mailing list2013-03-17T00:35:27Z<p>Flyingkiwiguy: </p>
<hr />
<div><br />
The Bitcoin [[Protocol specification]] supports the broadcast of [[Alerts]]. An unofficial email relay is now provided that rebroadcasts these [[block chain]] related alerts via subscription to the bitcoin unofficial alert mailing list [https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts]. Alternatively, to subscribe via email send an email to '''bitcoin-unofficial-alerts+subscribe@googlegroups.com''' [mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com] and you should receive an email asking you to verify your subscription.<br />
<br />
==Verify alerts and obtain the latest status information==<br />
If you receive an alert you should '''immediately verify it is official''' by running "bitcoind getinfo" (but see notes below), go to bitcoin.org [http://www.bitcoin.org] to obtain more details and background, or join the #bitcoin [[IRC channels]] on freenode to obtain the latest information.<br />
<br />
==Notes==<br />
*Alerts are broadcast to a specified range of bitcoin versions. The email relay uses a specially patched version of bitcoind that should report and therefore relay ''any'' alert broadcast for ''any'' version.<br />
*Alerts are also independent of blocks or transactions, and have a defined time-to-live.<br />
*The email relay polls bitcoind every six minutes and will continue to (re-)email alerts every six minutes until the alert is ended by the core bitcoind [[Developers]].<br />
<br />
==Feedback==<br />
Please send any comments or requests to Gary Mulder [mailto:flyingkiwiguy@gmail.com].<br />
<br />
[[Category:Services]]<br />
[[Category:Developer]]<br />
[[Category:ECommerce]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=36164Alerts mailing list2013-03-17T00:29:03Z<p>Flyingkiwiguy: </p>
<hr />
<div><br />
The Bitcoin [[Protocol specification]] supports the broadcast of [[Alerts]]. An unofficial email relay is now provided that rebroadcasts these [[block chain]] alerts via subscription to the bitcoin unofficial alert mailing list [https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts]. Alternatively, to subscribe via email send an email to '''bitcoin-unofficial-alerts+subscribe@googlegroups.com''' [mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com] and you should receive an email asking you to verify your subscription.<br />
<br />
==Verify alerts and obtain the latest status information==<br />
If you receive an alert you should '''immediately verify it is official''' by running "bitcoind getinfo" (but see notes below), go to bitcoin.org [http://www.bitcoin.org] to obtain more details and background, or join the #bitcoin [[IRC channels]] on freenode to obtain the latest information.<br />
<br />
==Notes==<br />
*Alerts are broadcast to a specified range of bitcoin versions. The email relay uses a specially patched version of bitcoind that should report and therefore relay ''any'' alert broadcast for ''any'' version.<br />
*Alerts are also independent of blocks or transactions, and have a defined time-to-live.<br />
*The email relay polls bitcoind every six minutes and will continue to (re-)email alerts every six minutes until the alert is ended by the core bitcoind [[Developers]].<br />
<br />
==Feedback==<br />
Please send any comments or requests to Gary Mulder [mailto:flyingkiwiguy@gmail.com].<br />
<br />
[[Category:Services]]<br />
[[Category:Developer]]<br />
[[Category:ECommerce]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=36163Alerts mailing list2013-03-17T00:21:52Z<p>Flyingkiwiguy: </p>
<hr />
<div><br />
The Bitcoin [[Protocol specification]] supports the broadcast of [[Alerts]]. An unofficial email relay is now provided that rebroadcasts these [[block chain]] alerts via subscription to the bitcoin unofficial alert mailing list [https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts]. Alternatively, to subscribe via email send an email to '''bitcoin-unofficial-alerts+subscribe@googlegroups.com''' [mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com] and you should receive an email asking you to verify your subscription.<br />
<br />
==Verify alerts and obtain the latest status information==<br />
If you receive an alert you should '''immediately verify it is official''' by running "bitcoind getinfo" (but see notes below), go to bitcoin.org [http://www.bitcoin.org] to obtain more details and background, or join the #bitcoin [[IRC channels]] on freenode to obtain the latest information.<br />
<br />
==Notes==<br />
*Alerts are broadcast to a specified range of bitcoin versions. The email relay uses a specially patched version of bitcoind that should report and therefore relay ''any'' alert broadcast for ''any'' version.<br />
*Alerts are also independent of blocks or transactions, and have a defined time-to-live.<br />
*The email relay polls bitcoind every five minutes and will continue to (re-)email alerts every five minutes until the alert is ended by the core bitcoind [[Developers]].<br />
<br />
==Feedback==<br />
Please send any comments or requests to Gary Mulder [mailto:flyingkiwiguy@gmail.com].<br />
<br />
[[Category:Services]]<br />
[[Category:Developer]]<br />
[[Category:ECommerce]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=36162Alerts mailing list2013-03-16T23:11:54Z<p>Flyingkiwiguy: added multi-version alert info</p>
<hr />
<div><br />
The Bitcoin [[Protocol specification]] supports the broadcast of [[Alerts]]. An unofficial email relay is now provided that rebroadcasts these [[block chain]] alerts via subscription to the bitcoin unofficial alert mailing list [https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts]. Alternatively, to subscribe via email send an email to '''bitcoin-unofficial-alerts+subscribe@googlegroups.com''' [mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com] and you should receive an email asking you to verify your subscription.<br />
<br />
==Verify alerts and obtain the latest status information==<br />
If you receive an alert you should '''immediately verify it is official''' by running "bitcoind getinfo" (but see notes below), go to bitcoin.org [http://www.bitcoin.org] to obtain more details and background, or join the #bitcoin [[IRC channels]] on freenode to obtain the latest information.<br />
<br />
==Notes==<br />
*Alerts are bitcoind are sent to a specified range of bitcoin versions. The email relay uses a specially patched version of bitcoind that should report and therefore relay ''any'' alert broadcast for ''any'' version.<br />
*Alerts are also independent of blocks or transactions, and have a defined time-to-live.<br />
*The email relay polls bitcoind every five minutes and will continue to (re-)email alerts every five minutes until the alert is ended by the core bitcoind [[Developers]].<br />
<br />
==Feedback==<br />
Please send any comments or requests to Gary Mulder [mailto:flyingkiwiguy@gmail.com].<br />
<br />
[[Category:Services]]<br />
[[Category:Developer]]<br />
[[Category:ECommerce]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=36159Alerts mailing list2013-03-16T21:29:44Z<p>Flyingkiwiguy: </p>
<hr />
<div><br />
The Bitcoin [[Protocol specification]] supports the broadcast of [[Alerts]]. An unofficial email relay is now provided that rebroadcasts these [[block chain]] alerts via subscription to the bitcoin unofficial alert mailing list [https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts]. Alternatively, to subscribe via email send an email to bitcoin-unofficial-alerts+subscribe@googlegroups.com [mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com].<br />
<br />
If you receive an alert you should '''immediately verify it is official''' by running "bitcoind getinfo", go to http://bitcoin.org [http://www.bitcoin.org] to find out more details concerning the alert, or join the #bitcoin IRC channel on freenode.<br />
<br />
Alerts are independent of blocks or transactions, and have a defined time-to-live. The email relay polls bitcoind every 5 minutes and will continue to send alerts until the alert is cleared.<br />
<br />
Please send any comments or requests to Gary Mulder [mailto:flyingkiwiguy@gmail.com].<br />
<br />
[[Category:Services]]<br />
[[Category:Developer]]<br />
[[Category:ECommerce]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=36151Alerts mailing list2013-03-16T10:57:05Z<p>Flyingkiwiguy: </p>
<hr />
<div><br />
The Bitcoin [[Protocol specification]] supports the broadcast of [[Alerts]]. An unofficial email relay is now provided that rebroadcasts these [[block chain]] alerts via subscription to the bitcoin unofficial alert mailing list [https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts]. Alternatively, to subscribe via email send an email to bitcoin-unofficial-alerts+subscribe@googlegroups.com [mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com].<br />
<br />
If you receive an alert you should '''immediately verify it is official''' by running "bitcoind getinfo", go to http://bitcoin.org [http://www.bitcoin.org] to find out more details concerning the alert, or join the #bitcoin IRC channel on freenode.<br />
<br />
Please send any comments or requests to Gary Mulder [mailto:flyingkiwiguy@gmail.com].<br />
<br />
[[Category:Services]]<br />
[[Category:Developer]]<br />
[[Category:ECommerce]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alert_system&diff=36150Alert system2013-03-16T10:56:03Z<p>Flyingkiwiguy: </p>
<hr />
<div>[[File:alert.png|thumb|300px|right]]<br />
<br />
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 also in the "errors" field of RPC ''getinfo''.<br />
<br />
[[File:Bitcoin-alert-cli.png|thumb|300px|right]]<br />
<br />
===Alert message===<br />
Alerts are broadcast using the same [[network|TCP relay system]] as ''block'' and ''tx'' messages. They are not encoded in a special transaction. Unlike block and tx relaying, alerts are sent at the start of every new connection for as long as the alert is in effect. This ensures that everyone receives the alert.<br />
<br />
Alerts contain this information:<br />
* How long to relay the alert.<br />
* How long to consider the alert valid.<br />
* An alert ID number.<br />
* A list of alerts that should be canceled upon receipt of this alert.<br />
* Exactly which versions of Bitcoin are affected by the alert. Unaffected versions still relay the alert for the benefit of older versions.<br />
* Alert priority.<br />
* The alert text.<br />
<br />
Only alerts that are signed by a specific ECDSA public key are considered valid. A copy of the private key is held by at least Satoshi, Gavin, and theymos.<br />
<br />
===Safe mode===<br />
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.<br />
<br />
Even though Bitcoin no longer automatically disables RPC when an alert is live, it is wise for Bitcoin sites to shut down when an alert has been issued. To detect an active alert, poll the "errors" field of ''getinfo''.<br />
<br />
To test safe mode, run Bitcoin with the -testsafemode switch. To override a real safe mode event, run Bitcoin with the -disablesafemode switch.<br />
<br />
===Past alerts===<br />
{| class="wikitable" border="1"<br />
|-<br />
! ID<br />
! Sent date<br />
! Expires (UTC)<br />
! Versions<br />
! Priority<br />
! Message<br />
|-<br />
| 1010<br />
| Feb 18, 2012<br />
| Feb 21 02:47:15<br />
| All<br />
| 100<br />
| See bitcoin.org/feb20 if you have trouble connecting after 20 February<br />
|-<br />
| 1011<br />
| Mar 16, 2012<br />
| cancelled May 15, 2012<br />
| 0.5 - 0.5.3<br />
| 5000<br />
| URGENT: security fix for Bitcoin-Qt on Windows: http://bitcoin.org/critfix<br />
|-<br />
| 1012<br />
| Mar 16, 2012<br />
| cancelled May 15, 2012<br />
| 6.0<br />
| 5000<br />
| URGENT: security fix for Bitcoin-Qt on Windows: http://bitcoin.org/critfix<br />
|-<br />
| 1013<br />
| Mar 16, 2012<br />
| cancelled May 15, 2012<br />
| 5.99<br />
| 5000<br />
| URGENT: security fix for Bitcoin-Qt on Windows: http://bitcoin.org/critfix<br />
|-<br />
| 1015<br />
| May 15, 2012<br />
| May 16, 2013<br />
| 0.1 - 0.4.5<br />
| 5000<br />
| URGENT: upgrade required, see http://bitcoin.org/dos for details<br />
|-<br />
| 1016<br />
| May 15, 2012<br />
| May 16, 2013<br />
| 0.4.99 - 0.5.4<br />
| 5000<br />
| URGENT: upgrade required, see http://bitcoin.org/dos for details<br />
|-<br />
| 1020<br />
| May 15, 2012<br />
| May 16, 2013<br />
| 0.6.0<br />
| 5000<br />
| URGENT: upgrade required, see http://bitcoin.org/dos for details<br />
|}<br />
<br />
==See Also==<br />
<br />
* [[Alerts mailing list]]<br />
<br />
[[Category:Technical]]<br />
[[Category:Vocabulary]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=36149Alerts mailing list2013-03-16T10:55:13Z<p>Flyingkiwiguy: </p>
<hr />
<div><br />
The Bitcoin [[Protocol specification]] supports the broadcast of [[Alerts]]. An unofficial email relay is now provided that rebroadcasts these [[block chain]] alerts via subscription to the bitcoin unofficial alert mailing list [https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts]. Alternatively, to subscribe via email send an email to bitcoin-unofficial-alerts+subscribe@googlegroups.com [mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com].<br />
<br />
If you receive an alert you should '''immediately verify it is official''' by running "bitcoind getinfo", go to http://bitcoin.org [http://www.bitcoin.org] to find out more details concerning the alert, or join the #bitcoin IRC channel on freenode.<br />
<br />
Please send any comments or requests to Gary Mulder [[mailto:flyingkiwiguy@gmail.com]]<br />
<br />
[[Category:Services]]<br />
[[Category:Developer]]<br />
[[Category:ECommerce]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=36148Alerts mailing list2013-03-16T10:51:23Z<p>Flyingkiwiguy: </p>
<hr />
<div><br />
The Bitcoin [[Protocol specification]] supports the broadcast of [[Alerts]]. An unofficial email relay is now provided that rebroadcasts these [[block chain]] alerts via subscription to the bitcoin unofficial alert mailing list [[https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts]]. Alternatively, to subscribe via email send an email to bitcoin-unofficial-alerts+subscribe@googlegroups.com [[mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com]].<br />
<br />
If you receive an alert you should '''immediately verify it is official''' by running "bitcoind getinfo", go to [[bitcoin.org|http://www.bitcoin.org]] to find out more details concerning the alert, or join the #bitcoin IRC channel on freenode.<br />
<br />
Please send any comments or requests to Gary Mulder [[mailto:flyingkiwiguy@gmail.com]]<br />
<br />
[[Category:Services]]<br />
[[Category:Developer]]<br />
[[Category:ECommerce]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=36147Alerts mailing list2013-03-16T10:47:55Z<p>Flyingkiwiguy: </p>
<hr />
<div><br />
The Bitcoin [[Protocol specification]] supports the broadcast of [[Alerts]]. An unofficial email relay is now provided that rebroadcasts these [[block chain]] alerts via subscription to the bitcoin unofficial alert mailing list [[https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts]]. Alternatively, to subscribe via email send an email to bitcoin-unofficial-alerts+subscribe@googlegroups.com [[mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com]].<br />
<br />
If you receive an alert you should '''immediately verify it is official''' by running "bitcoind getinfo", go to [[bitcoin.org|http://www.bitcoin.org]] to find out more details concerning the alert, or join the #bitcoin IRC channel on freenode.<br />
<br />
Please send any comments or requests to [[mailto:flyingkiwiguy@gmail.com]]<br />
<br />
[[Category:Services]]<br />
[[Category:Developer]]<br />
[[Category:ECommerce]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alert_system&diff=36146Alert system2013-03-16T10:46:27Z<p>Flyingkiwiguy: added see also alerts mailing list</p>
<hr />
<div>[[File:alert.png|thumb|300px|right]]<br />
<br />
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 also in the "errors" field of RPC ''getinfo''.<br />
<br />
[[File:Bitcoin-alert-cli.png|thumb|300px|right]]<br />
<br />
===Alert message===<br />
Alerts are broadcast using the same [[network|TCP relay system]] as ''block'' and ''tx'' messages. They are not encoded in a special transaction. Unlike block and tx relaying, alerts are sent at the start of every new connection for as long as the alert is in effect. This ensures that everyone receives the alert.<br />
<br />
Alerts contain this information:<br />
* How long to relay the alert.<br />
* How long to consider the alert valid.<br />
* An alert ID number.<br />
* A list of alerts that should be canceled upon receipt of this alert.<br />
* Exactly which versions of Bitcoin are affected by the alert. Unaffected versions still relay the alert for the benefit of older versions.<br />
* Alert priority.<br />
* The alert text.<br />
<br />
Only alerts that are signed by a specific ECDSA public key are considered valid. A copy of the private key is held by at least Satoshi, Gavin, and theymos.<br />
<br />
===Safe mode===<br />
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.<br />
<br />
Even though Bitcoin no longer automatically disables RPC when an alert is live, it is wise for Bitcoin sites to shut down when an alert has been issued. To detect an active alert, poll the "errors" field of ''getinfo''.<br />
<br />
To test safe mode, run Bitcoin with the -testsafemode switch. To override a real safe mode event, run Bitcoin with the -disablesafemode switch.<br />
<br />
===Past alerts===<br />
{| class="wikitable" border="1"<br />
|-<br />
! ID<br />
! Sent date<br />
! Expires (UTC)<br />
! Versions<br />
! Priority<br />
! Message<br />
|-<br />
| 1010<br />
| Feb 18, 2012<br />
| Feb 21 02:47:15<br />
| All<br />
| 100<br />
| See bitcoin.org/feb20 if you have trouble connecting after 20 February<br />
|-<br />
| 1011<br />
| Mar 16, 2012<br />
| cancelled May 15, 2012<br />
| 0.5 - 0.5.3<br />
| 5000<br />
| URGENT: security fix for Bitcoin-Qt on Windows: http://bitcoin.org/critfix<br />
|-<br />
| 1012<br />
| Mar 16, 2012<br />
| cancelled May 15, 2012<br />
| 6.0<br />
| 5000<br />
| URGENT: security fix for Bitcoin-Qt on Windows: http://bitcoin.org/critfix<br />
|-<br />
| 1013<br />
| Mar 16, 2012<br />
| cancelled May 15, 2012<br />
| 5.99<br />
| 5000<br />
| URGENT: security fix for Bitcoin-Qt on Windows: http://bitcoin.org/critfix<br />
|-<br />
| 1015<br />
| May 15, 2012<br />
| May 16, 2013<br />
| 0.1 - 0.4.5<br />
| 5000<br />
| URGENT: upgrade required, see http://bitcoin.org/dos for details<br />
|-<br />
| 1016<br />
| May 15, 2012<br />
| May 16, 2013<br />
| 0.4.99 - 0.5.4<br />
| 5000<br />
| URGENT: upgrade required, see http://bitcoin.org/dos for details<br />
|-<br />
| 1020<br />
| May 15, 2012<br />
| May 16, 2013<br />
| 0.6.0<br />
| 5000<br />
| URGENT: upgrade required, see http://bitcoin.org/dos for details<br />
|}<br />
<br />
==See Also==<br />
<br />
* [[Unofficial Bitcoin alerts mailing list|Alerts mailing list]]<br />
<br />
[[Category:Technical]]<br />
[[Category:Vocabulary]]</div>Flyingkiwiguyhttps://en.bitcoin.it/w/index.php?title=Alerts_mailing_list&diff=36145Alerts mailing list2013-03-16T10:41:38Z<p>Flyingkiwiguy: Created page with " The Bitcoin Protocol_specification supports the broadcast of Alerts. An unofficial email relay is now provided that rebroadcasts these block chain alerts via subs..."</p>
<hr />
<div><br />
The Bitcoin [[Protocol_specification]] supports the broadcast of [[Alerts]]. An unofficial email relay is now provided that rebroadcasts these [[block chain]] alerts via subscription to [[bitcoin unofficial alert mailing list|https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts]]. Alternatively, to subscribe via email send an email to [[mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com]].<br />
<br />
If you receive an alert you should '''immediately verify it is official''' by running "bitcoind getinfo", go to [[bitcoin.org|http://www.bitcoin.org]] to find out more details concerning the alert, or join the #bitcoin IRC channel on freenode.<br />
<br />
Please send any comments or requests to [[mailto:flyingkiwiguy@gmail.com]]<br />
<br />
[[Category:Services]]<br />
[[Category:Developer]]<br />
[[Category:ECommerce]]</div>Flyingkiwiguy