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