Difference between revisions of "Alerts mailing list"

From Bitcoin Wiki
Jump to: navigation, search
(Service is now not only discontinued but alerts themselves are dead. Changed all sentences to past tense.)
 
Line 1: Line 1:
The Bitcoin [[Protocol specification]] supports the broadcast of [[Alerts]]. In the past, an unofficial email relay was 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.
+
The Bitcoin [[Protocol specification]] previously supported the broadcast of [[Alerts]]. In the past, an unofficial email relay was provided that rebroadcast these [[block chain]] related alerts. To subscribe via email, you sent an email to '''bitcoin-unofficial-alerts+subscribe@googlegroups.com''' [mailto:bitcoin-unofficial-alerts+subscribe@googlegroups.com] to receive an email asking you to verify your subscription.
  
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.
+
Alternatively, you can browse to the Google Group for the list [https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts].
  
 
==Verify alerts and obtain the latest status information==
 
==Verify alerts and obtain the latest status information==
If you receive an alert you should '''immediately verify it is official''' by running "bitcoin-cli 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.
+
 
 +
When you received an alert, you should have '''immediately verified it was official''' by running "bitcoin-cli getinfo" (but see notes below), gone to bitcoin.org [http://www.bitcoin.org] to obtain more details and background, or joined the #bitcoin [[IRC channels]] on Freenode to obtain the latest information.
  
 
==Notes==
 
==Notes==
*Alerts are broadcast to a specified range of Bitcoin versions.
+
*Alerts were 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.
+
*The email relay used a specially patched version of bitcoind that should have reported and therefore relayed ''any'' alert broadcast for ''any'' version.
*You will therefore have to verify whether or not the alert is actually relevant to your particular version of Bitcoin client.
+
*You therefore had to verify whether or not the alert was actually relevant to your particular version of Bitcoin Core.
*Alerts are also independent of blocks or transactions, and have a defined time-to-live.
+
*Alerts were also independent of blocks or transactions and had a defined time-to-live.
*The email relay polls bitcoind every six minutes.
+
*The email relay polled bitcoind every six minutes.
  
 
==Feedback==
 
==Feedback==
Please send any comments or requests to Gary Mulder [mailto:flyingkiwiguy@gmail.com].
+
The now-discontinued service was operated by Gary Mulder [mailto:flyingkiwiguy@gmail.com].
  
 
[[Category:Services]]
 
[[Category:Services]]

Latest revision as of 13:15, 6 January 2018

The Bitcoin Protocol specification previously supported the broadcast of Alerts. In the past, an unofficial email relay was provided that rebroadcast these block chain related alerts. To subscribe via email, you sent an email to bitcoin-unofficial-alerts+subscribe@googlegroups.com [1] to receive an email asking you to verify your subscription.

Alternatively, you can browse to the Google Group for the list [2].

Verify alerts and obtain the latest status information

When you received an alert, you should have immediately verified it was official by running "bitcoin-cli getinfo" (but see notes below), gone to bitcoin.org [3] to obtain more details and background, or joined the #bitcoin IRC channels on Freenode to obtain the latest information.

Notes

  • Alerts were broadcast to a specified range of Bitcoin versions.
  • The email relay used a specially patched version of bitcoind that should have reported and therefore relayed any alert broadcast for any version.
  • You therefore had to verify whether or not the alert was actually relevant to your particular version of Bitcoin Core.
  • Alerts were also independent of blocks or transactions and had a defined time-to-live.
  • The email relay polled bitcoind every six minutes.

Feedback

The now-discontinued service was operated by Gary Mulder [4].