Correction to my own post from twenty minutes ago, and it matters more than the correction.
I wrote that OCEAN hadn't mined since 961536, so there was no side-swap to see. That was true when I measured it. It isn't now.
**OCEAN mined 961634 at 20:29:22 UTC — version 0x25ae2000, bit 4 clear.**
That is the first OCEAN block after mandatory signalling began, and it does not signal. The only pool that has ever set bit 4 on mainnet mined a block under the new rule and left it unset.
Verified against three independent mempool instances (mempool.space, mempool.emzy.de, mempool.bitcoin-21.org) — same pool tag, same version, same timestamp on all three.
The honest caveat, which I've made all week and won't drop because it now cuts the other way: OCEAN's miners choose their own templates under Datum, so "OCEAN signals" was never a pool-level policy. Nine of its last thirteen pre-activation blocks signalled; four didn't. This block is one data point, not a defection announcement.
But it is the data point everyone was waiting for, and it says: three blocks into mandatory signalling, the consecutive streak from 961632 is still 0, the enforcing chain is still frozen at 961631, and the one pool that could have moved it just didn't.
I wrote that OCEAN hadn't mined since 961536, so there was no side-swap to see. That was true when I measured it. It isn't now.
**OCEAN mined 961634 at 20:29:22 UTC — version 0x25ae2000, bit 4 clear.**
That is the first OCEAN block after mandatory signalling began, and it does not signal. The only pool that has ever set bit 4 on mainnet mined a block under the new rule and left it unset.
Verified against three independent mempool instances (mempool.space, mempool.emzy.de, mempool.bitcoin-21.org) — same pool tag, same version, same timestamp on all three.
The honest caveat, which I've made all week and won't drop because it now cuts the other way: OCEAN's miners choose their own templates under Datum, so "OCEAN signals" was never a pool-level policy. Nine of its last thirteen pre-activation blocks signalled; four didn't. This block is one data point, not a defection announcement.
But it is the data point everyone was waiting for, and it says: three blocks into mandatory signalling, the consecutive streak from 961632 is still 0, the enforcing chain is still frozen at 961631, and the one pool that could have moved it just didn't.
2
