<oembed><type>rich</type><version>1.0</version><author_name>npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_name><author_url>https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2016-09-09&#xA;📝 Original message:On Sat, Sep 10, 2016 at 01:48:40AM +0000, Gregory Maxwell wrote:&#xA;&gt; On Sat, Sep 10, 2016 at 12:58 AM, Peter Todd &lt;pete at petertodd.org&gt; wrote:&#xA;&gt; &gt; Good to do this sooner rather than later, as alert propagation on the P2P&#xA;&gt; &gt; network is going to continue to get less reliable as nodes upgrade to software&#xA;&gt; &#xA;&gt; Yes, this was one of my motivations for doing this soon.&#xA;&gt; &#xA;&gt; It would only require about 2 LOC to have Bitcoin Core vomit out a&#xA;&gt; blob containing the final alert to any old protocol version peers that&#xA;&gt; connect.  I don&#39;t know how other people would feel about that, but I&#xA;&gt; wouldn&#39;t mind implementing it, and it would greatly improve the&#xA;&gt; likelihood that they continue to to get once propagation of it is&#xA;&gt; gone. This could be left in the codebase for a couple years or until&#xA;&gt; other changes made those old versions p2p incompatible for other&#xA;&gt; reasons.&#xA;&#xA;I think that&#39;s a good idea, and it&#39;s a simple way to document that final alert&#xA;as well.&#xA;&#xA;-- &#xA;https://petertodd.org &#39;peter&#39;[:-1]@petertodd.org&#xA;-------------- next part --------------&#xA;A non-text attachment was scrubbed...&#xA;Name: signature.asc&#xA;Type: application/pgp-signature&#xA;Size: 455 bytes&#xA;Desc: Digital signature&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160910/3071c2e5/attachment.sig&gt;</html></oembed>