{"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:2015-09-28\n📝 Original message:On Mon, Sep 28, 2015 at 09:01:02AM -0400, Gavin Andresen wrote:\n\u003e I think three things need to happen:\n\u003e \n\u003e 1) Stop pretending that \"everyone must agree to make consensus rule\n\u003e changes.\" \"Rough consensus\" is what we've always gone with, and is good\n\u003e enough.\n\u003e \n\u003e 2) Mr. Todd (or somebody) needs to write up a risk/benefit security\n\u003e tradeoff analysis doo-hickey document and publish it. I'm reasonably\n\u003e confident that the risks to SPV nodes can be mitigated (e.g. by deploying\n\u003e mempool-only first, before the soft fork rolls out), but as somebody who\n\u003e has only been moderately paying attention, BETTER COMMUNICATION is needed.\n\u003e What should SPV wallet authors be doing right now, if anything? Once the\n\u003e soft fork starts to roll out or activates, what do miners need to be aware\n\u003e of? SPV wallet authors?\n\nDo you have such a document for your BIP101? That would save me a lot of\ntime, and the need for that kind of document is significantly higher\nwith BIP101 anyway.\n\n\nRe: mempool, CLTV-using transactions are non-standard and are not\nrelayed in all Bitcoin Core releases. (see my pull-req #5000 -\nDiscourage NOPs reserved for soft-fork upgrades - for why) I believe\nthat meets your suggestion of deploying mempool-only first.\n\n-- \n'peter'[:-1]@petertodd.org\n0000000000000000032420ad2987adc954df855f9ae10cf608e911b431f640e0\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 650 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150928/24bdf9f3/attachment.sig\u003e"}