Bitcoin Developers Publish the Alert Key – Trustnodes

Bitcoin Developers Publish the Alert Key

0

Bitcoin’s alert key, which has on some rare occassions been used in emergency situations to notify nodes of vulnerabilities, has now publicly been revealed by Bryan Bishop as follows:

“mainnet public key:
04fc9702847840aaf195de8442ebecedf5b095cdbb9bc716bda9110971b28a49e0ead8564ff0db22209e0374782c093bb899692d524e9d6a6956e7c5ecbcd68284

mainnet private key:
30820113020101042053cdc1e0cfac07f7e1c312768886f4635f6bceebec0887f63a9d37a26a92e6b6a081a53081a2020101302c06072a8648ce3d0101022100fffffffffffffffffffffffffffffffffffffffffffffffffffffffefffffc2f300604010004010704410479be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798483ada7726a3c4655da4fbfc0e1108a8fd17b448a68554199c47d08ffb10d4b8022100fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364141020101a14403420004fc9702847840aaf195de8442ebecedf5b095cdbb9bc716bda9110971b28a49e0ead8564ff0db22209e0374782c093bb899692d524e9d6a6956e7c5ecbcd68284

testnet public key:
04302390343f91cc401d56d68b123028bf52e5fca1939df127f63c6467cdf9c8e2c14b61104cf817d0b780da337893ecc4aaff1309e536162dabbdb45200ca2b0a

testnet private key:
308201130201010420474d447aa6f46b4f45f67f21180a5de2722fc807401c4c4d95fdae64b3d6c294a081a53081a2020101302c06072a8648ce3d0101022100fffffffffffffffffffffffffffffffffffffffffffffffffffffffefffffc2f300604010004010704410479be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798483ada7726a3c4655da4fbfc0e1108a8fd17b448a68554199c47d08ffb10d4b8022100fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364141020101a14403420004302390343f91cc401d56d68b123028bf52e5fca1939df127f63c6467cdf9c8e2c14b61104cf817d0b780da337893ecc4aaff1309e536162dabbdb45200ca2b0a”

The alert key functionality was removed from the protocol itself in 2016, when a final message was sent asking pre-segwit nodes running v0.12.x or older to upgrade to the segregated witnesses (segwit) client. It remained non-public knowledge, however, until today.

Pre-segwit nodes alerted to upgrade to segwit client.
Pre-segwit nodes alerted to upgrade to segwit client.

Previously, a number of individuals had access to the key, with any one of them able to remove or cancel an alert that had been sent.

It was used in 2013 when there was an unintentional fork and in other situations when nodes needed to be urgently notified.

As long as the key was operational, it was never misused. How or why the very last alert was sent, however, is unclear. While its removal was justified on the basis that it could be misused, it might have also been the case they may have worried one developer might remove the last alert that was sent out.

As can be seen in the featured image, the notification aimed at node operators was very unintrusive as shown above at the bottom left.

It was merely used as a method of directly notifying node operators who might have not kept up with developments.

Now, there currently is no such way of direct notification, but there is a moderated mailing list which can be used, although that is mainly for bitcoin code discussions.

Other bitcoin forks may have copied the alert key which has now been publicly revealed. Bitcoin Cash removed it long ago, but whether other bitcoin fork nodes have also done so is unclear.

Copyrights Trustnodes.com

 

Subscribe
Notify of
0 Comments
Inline Feedbacks
View all comments