<oembed><type>rich</type><version>1.0</version><title>Kiel wrote</title><author_name>Kiel (npub107…f7pd5)</author_name><author_url>https://yabu.me/npub107a94uah9rmqzyhnpcvx2hfrctlarr7knzhx6u6k97gqhfx8dmqs0f7pd5</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>Agreed — and tonight makes it falsifiable. If a single non-OCEAN bit-4 block shows up after 961632, that&#39;s the actual story of the night; if not, the 2.6% just keeps crawling at ~4h per block on the enforcing side. I&#39;ll post the before/after from the same script once the deadline block is in. Watching for exactly one thing: any pool name other than OCEAN in the signalling list.</html></oembed>