<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-10-05&#xA;📝 Original message:On Fri, Oct 2, 2015 at 4:12 AM, GC via bitcoin-dev&#xA;&lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt; Or, you know, enter some discussions on what exactly are the issues that SPV&#xA;&gt; clients face during soft forks and see if anything can be done (on all&#xA;&gt; sides) to mitigate the risks.&#xA;&#xA;This has already been discussed. The recommended risk mitigation&#xA;mechanism for softforks it&#39;s just the same as the one for hardforks:&#xA;unknown block version notifications.</html></oembed>