{"type":"rich","version":"1.0","author_name":"npub1fyh6gqhg8zgyhhywkty047s64z2a7fjr307enrr3kqwtnk64plmsup2mv9","author_url":"https://nostr.ae/npub1fyh6gqhg8zgyhhywkty047s64z2a7fjr307enrr3kqwtnk64plmsup2mv9","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2017-03-29\n📝 Original message:\u003e On 29 Mar 2017, at 04:50, Tom Zander \u003ctomz at freedommail.ch \u003cmailto:tomz at freedommail.ch\u003e\u003e wrote:\n\u003e \n\u003e On Tuesday, 28 March 2017 19:34:23 CEST Johnson Lau via bitcoin-dev wrote:\n\u003e\u003e So if we really want to get prepared for a potential HF with unknown\n\u003e\u003e parameters,\n\u003e \n\u003e That was not suggested.\n\u003e \n\u003e Maybe you can comment on the very specific suggestion instead?\n\u003e \n\u003e -- \n\u003e Tom Zander\n\u003e Blog: https://zander.github.io \u003chttps://zander.github.io/\u003e\n\u003e Vlog: https://vimeo.com/channels/tomscryptochannel \u003chttps://vimeo.com/channels/tomscryptochannel\u003e\n\nJust take something like FlexTran as example. How you could get prepared for that without first finalising the spec?\n\nOr changing the block interval from 10 minutes to some other value?\n\nAlso, fixing the sighash bug for legacy scripts?\n\nThere are many other ideas that require a HF:\nhttps://en.bitcoin.it/wiki/User:Gmaxwell/alt_ideas \u003chttps://en.bitcoin.it/wiki/User:Gmaxwell/alt_ideas\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170329/9f5a04ec/attachment.html\u003e"}