<oembed><type>rich</type><version>1.0</version><author_name>npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0u</author_name><author_url>https://nostr.ae/npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0u</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2013-10-30&#xA;📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----&#xA;Hash: SHA1&#xA;&#xA;If I understand the code correctly, it&#39;s not about rejecting blocks.&#xA;It&#39;s about noticing that &gt;50% of recent blocks are declaring a version&#xA;number that is meaningless to you. Chances are, there&#39;s been a soft&#xA;fork and you should upgrade.&#xA;&#xA;On 10/30/13 1:24 AM, Mike Hearn wrote:&#xA;&gt; &#xA;&gt; But if you are getting soft-forked recent versions of the&#xA;&gt; reference implementation WILL alert you; see this code in&#xA;&gt; main.cpp:&#xA;&gt; &#xA;&gt; &#xA;&gt; Perhaps I&#39;m confused about how we&#39;re using the term soft fork. My &#xA;&gt; understanding is that this is where a new upgrade is designed to&#xA;&gt; look valid to old nodes, and if you don&#39;t upgrade you rely on the&#xA;&gt; miner majority to get you &#34;back on track&#34;. For instance, P2SH was&#xA;&gt; done this way - old nodes that didn&#39;t upgrade during that&#xA;&gt; transition believed all spends of P2SH outputs were valid, even&#xA;&gt; those spending someone elses coins.&#xA;&gt; &#xA;&gt; In this case, the code you cite won&#39;t do anything because your&#xA;&gt; client will never reject a block during a soft-forking upgrade,&#xA;&gt; even if it does something that&#39;s supposed to be invalid or&#xA;&gt; nonsensical.&#xA;&gt; &#xA;&gt; If a new block version changes the serialization format or script &#xA;&gt; language or SIGHASH rules such that old clients reject the block,&#xA;&gt; then they will end up on a hard fork and the alerting code will&#xA;&gt; trigger, which is correct and as it should be.&#xA;-----BEGIN PGP SIGNATURE-----&#xA;Version: GnuPG/MacGPG2 v2.0.19 (Darwin)&#xA;Comment: GPGTools - http://gpgtools.org&#xA;Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/&#xA;&#xA;iQIcBAEBAgAGBQJScMvBAAoJEAdzVfsmodw4I5sQAL0Wq4e7b6/KX2zl9RmtFl5S&#xA;qM9ZJkJV8qzirj1hMgVwvnuOj147Vb3EkJujxeMa8ujepXKZ215mMCLnCHPzWPpJ&#xA;jTtOBn1FCkCUbyt9uSbZ+56NR+ElmSOsDpAJ8IR9VywHriCxm4OIAMCLTR6CKRfr&#xA;6NWySvjEMlsSHyr7DFaJTlMqo+KIUWGmP7tdPu1L2AvNE+613dI5q76IjUHYoxhu&#xA;2dDtanYUvFCsdLZEnjTr1N45BBf1mTSlPfmA1ZWHgM779h6VIyb0TeO+iCaxpvWp&#xA;2RpSDj3+diFdMUK2uu69ZcwkREH0/RoQLOys6U5DfaGkpPtjY0YXB5DwN9quKgzX&#xA;padWzbQ0flpwWLYOPYrWATz4sWflxZJu6wHAcUkRS5k9crOLVjritXs1205x7YET&#xA;0H9jtbqXmBRXidCP2BOZPdq0PGDF8g2VeEHR69JRe3F3dBfSvbgHfKoiF1jpLLqb&#xA;rttoP+nD4ZRX8FesV2E/DEZgDZJMd8eqDKNDjq7Db4BTDg24Nq2ATNE2fBtenXwI&#xA;nXVNdmnvjDxjF0weJGlYgaQTfgVwHRxs+j4qgY4VLM0qEYplhHgg+KmOMFUtxAF/&#xA;sZv6w56XtCZS3LdNONAJSZzXIcqgmcodiWKVxkTL29dsWKikcBL5cG9ipdfmjQKT&#xA;eccFOHArsbW3eSfKP/Mb&#xA;=FSQI&#xA;-----END PGP SIGNATURE-----</html></oembed>