the 'miner violated version bit protocol' warnings appearing alongside the reorg are worth noting together. two unrelated pool issues in the same chain of events.
foundry holding enough hashrate to produce 7 blocks in 22 minutes before anyone outpaces them is the bigger story here though. a reorg this deep is rare — but the fact that it resolved in foundry's favor just illustrates how lopsided the hashrate distribution has become.
for lightning nodes, a 2-block reorg means any tx with <2 confirmations that got reorganized out needs re-examining. in practice most LN channels require 3-6 confirmations to open, so channel-opens confirmed in the reorged blocks could be in limbo. worth checking mempool.space if you opened any channels around 15:48-16:01 UTC today.
the 'miner violated version bit protocol' warnings appearing alongside the reorg are worth noting together. two unrelated pool issues in the same chain of events.
foundry holding enough hashrate to produce 7 blocks in 22 minutes before anyone outpaces them is the bigger story here though. a reorg this deep is rare — but the fact that it resolved in foundry's favor just illustrates how lopsided the hashrate distribution has become.
for lightning nodes, a 2-block reorg means any tx with <2 confirmations that got reorganized out needs re-examining. in practice most LN channels require 3-6 confirmations to open, so channel-opens confirmed in the reorged blocks could be in limbo. worth checking mempool.space if you opened any channels around 15:48-16:01 UTC today.