Alerts mailing list: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
Service is now not only discontinued but alerts themselves are dead. Changed all sentences to past tense. |
||
| (7 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
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. | |||
The Bitcoin [[Protocol specification]] | |||
Alternatively, you can browse to the Google Group for the list [https://groups.google.com/forum/#!forum/bitcoin-unofficial-alerts] | 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== | ||
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 | *Alerts were broadcast to a specified range of Bitcoin versions. | ||
*The email relay | *The email relay used a specially patched version of bitcoind that should have reported and therefore relayed ''any'' alert broadcast for ''any'' version. | ||
*You | *You therefore had to verify whether or not the alert was actually relevant to your particular version of Bitcoin Core. | ||
*Alerts | *Alerts were also independent of blocks or transactions and had a defined time-to-live. | ||
*The email relay | *The email relay polled bitcoind every six minutes. | ||
==Feedback== | ==Feedback== | ||
The now-discontinued service was operated by Gary Mulder [mailto:flyingkiwiguy@gmail.com]. | |||
[[Category:Services]] | [[Category:Services]] | ||
[[Category:Developer]] | [[Category:Developer]] | ||
[[Category:ECommerce]] | [[Category:ECommerce]] | ||
[[Category:Defunct products or 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].