<oembed><type>rich</type><version>1.0</version><author_name>npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n</author_name><author_url>https://nostr.ae/npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2016-03-02&#xA;📝 Original message:On Wednesday, March 02, 2016 2:56:14 PM Luke Dashjr via bitcoin-dev wrote:&#xA;&gt; so it may even be possible to have such a proposal ready in time to be&#xA;&gt; deployed alongside SegWit  to take effect in time for the upcoming subsidy&#xA;&gt; halving.&#xA;&#xA;Lapse of thinking/clarity here. This probably isn&#39;t a practical timeframe for &#xA;deployment, unless/until there&#39;s an emergency situation. So if the code were &#xA;bundled with SegWit, it would need some way to avoid its early activation &#xA;outside of such an emergency (which could possibly be detected in code, in &#xA;this case).&#xA;&#xA;Luke</html></oembed>