rich1.0npub1fyh6gqhg8zgyhhywkty047s64z2a7fjr307enrr3kqwtnk64plmsup2mv9https://nostr.ae/npub1fyh6gqhg8zgyhhywkty047s64z2a7fjr307enrr3kqwtnk64plmsup2mv9njumphttps://nostr.ae📅 Original date posted:2017-03-29 📝 Original message:> On 29 Mar 2017, at 04:50, Tom Zander <tomz at freedommail.ch <mailto:tomz at freedommail.ch>> wrote: > > On Tuesday, 28 March 2017 19:34:23 CEST Johnson Lau via bitcoin-dev wrote: >> So if we really want to get prepared for a potential HF with unknown >> parameters, > > That was not suggested. > > Maybe you can comment on the very specific suggestion instead? > > -- > Tom Zander > Blog: https://zander.github.io <https://zander.github.io/> > Vlog: https://vimeo.com/channels/tomscryptochannel <https://vimeo.com/channels/tomscryptochannel> Just take something like FlexTran as example. How you could get prepared for that without first finalising the spec? Or changing the block interval from 10 minutes to some other value? Also, fixing the sighash bug for legacy scripts? There are many other ideas that require a HF: https://en.bitcoin.it/wiki/User:Gmaxwell/alt_ideas <https://en.bitcoin.it/wiki/User:Gmaxwell/alt_ideas> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170329/9f5a04ec/attachment.html>