BUIP013 (passed X): Upgrade alert system so that Bitcoin Unlimited can send message alerts to nodes

[theZerg]

@theZerg I recommend disabling the alert system per A (which got more votes than B) and then open a dialogue with Classic (when they have time) as to how they intend to upgrade their alert system

Update:

@solex With Classic binaries now available, BU should move to prevent a rogue message being broadcast. Since the private key is shared by several individuals, there is no way to know who actually sent out a message. So there is plausible deniability if an alert like "Critical consensus bug found in Classic/BU, please shut down immediately" is circulated.

I can make a patch/pull request - should I do it against this repo? https://github.com/BitcoinUnlimited/BitcoinUnlimited/tree/0.11cfg_stats

Hi @bitcartel. Make a pull request against https://github.com/BitcoinUnlimited/BitcoinUnlimited/tree/0.12bu

 

[Roy Badami]

Why should BU relay those messages? If another Bitcoin Client emerged with their own alert system, BU would be under no obligation to relay their messages - unless the user wanted to.

Of course we're under no obligation to relay other clients' messages, but in the spirit of cooperation I'd suggest it would be constructive to do so.

My vision of the future is one in which there are several cooperating full node implementations. If those implementations choose to retain some version of the alert system, perhaps with each implementation using their own keys, then it seems desirable that the implementations should cooperate to relay each others messages.

 

[bitcartel]

@theZerg Issued a pull request. Thanks.