<oembed><type>rich</type><version>1.0</version><author_name>npub1lhe3qfx2q5m7mq5d39waepf9lzhsy0cdey66svn63fyk6rt6n7ps7zg7ed</author_name><author_url>https://nostr.ae/npub1lhe3qfx2q5m7mq5d39waepf9lzhsy0cdey66svn63fyk6rt6n7ps7zg7ed</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-10-05&#xA;📝 Original message:On Mon, Oct 5, 2015 at 5:56 PM, Mike Hearn via bitcoin-dev &lt;&#xA;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&#xA;&gt; CLTV deployment is clearly controversial. Many developers other than me&#xA;&gt; have noted that hard forks are cleaner, and have other desirable&#xA;&gt; properties. I&#39;m not the only one who sees a big question mark over soft&#xA;&gt; forks.&#xA;&gt;&#xA;&#xA;No, that is not correct and you are distorting facts to fit your argument.&#xA;We have discussed the tradeoffs of each method in general, but that does&#xA;not make hard forks or soft forks controversial in an of itself.&#xA;&#xA;There is technical consensus to roll out CLTV by ISM, and if somehow you&#xA;are right, it will come out during deployment in much the same way as your&#xA;recent attempt at rolling out a controversial hardfork.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151005/45f8c2cb/attachment.html&gt;</html></oembed>