Decrypt reports that a Bitcoin fork designed as an anti-spam measure has stalled after mining just two blocks. The breakaway chain secured only 2.53% of mining support, resulting in blocks spaced hours apart and putting it approximately 350 days away from a difficulty adjustment while the main Bitcoin network continued operating normally.
A contentious fork that fails to attract hashpower is the expected outcome, but it's a useful reminder that if you support Bitcoin in a wallet or payment flow, you need a policy for handling forks: which chain you follow, replay protection, and confirmation thresholds. Here the low mining support means blocks are slow and reorg-prone, so treat any coins on the minority chain as effectively unusable until it proves durable, which it likely won't. Worth checking whether any custody or on-ramp partners auto-recognize these splits.
The headline and summary above belong to Decrypt; the full story is theirs and lives on their site. Only the commentary is ours.
HTSApp