<oembed><type>rich</type><version>1.0</version><author_name>npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8</author_name><author_url>https://nostr.ae/npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-12-09&#xA;📝 Original message:On Wed, Dec 9, 2015 at 7:29 AM, Gregory Maxwell via bitcoin-dev&#xA;&lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt; What was being discussed was the location of the witness commitment;&#xA;&gt; which is consensus critical regardless of where it is placed. Should&#xA;&gt; it be placed in an available location which is compatible with the&#xA;&gt; existing network, or should the block hashing data structure&#xA;&gt; immediately be changed in an incompatible way to accommodate it in&#xA;&gt; order to satisfy an ascetic sense of purity and to make fraud proofs&#xA;&gt; somewhat smaller?&#xA;&#xA;&gt;From this question one could think that when you said &#34;we can do the&#xA;cleanup hardfork later&#34; earlier you didn&#39;t really meant it. And that&#xA;you will oppose to that hardfork later just like you are opposing to&#xA;it now.&#xA;As said I disagree that making a softfork first and then move the&#xA;commitment is less disruptive (because people will need to adapt their&#xA;software twice), but if the intention is to never do the second part&#xA;then of course I agree it would be less disruptive.&#xA;How long after the softfork would you like to do the hardfork?&#xA;1 year after the softfork? 2 years? never?</html></oembed>