A Bitcoin block can carry full proof of work and still be invalid. I've catalogued 143 established cases from 2010 to 2026, including two previously unreported F2Pool timestamp failures this year.

Invalid Bitcoin blocks: full PoW, consensus invalid

deadmanoz's website

89 blocks in 2012 contained the same P2SH-invalid transaction, mined by pools that hadn’t upgraded. Archived explorer transaction lists and preserved headers establish its inclusion in all 89. Only four complete block bodies could be rebuilt. Both recent F2Pool headers survived in merge-mined chains, with no known Bitcoin-side capture. These chains also yielded ~1,400 stales new to the stale-blocks collection. Monitoring them is essential to a holistic Bitcoin monitoring effort. 127 of the 143 blocks have no complete body, yet their failures remain independently checkable. 10 further reports still need evidence. Old node files, pool logs or archives could help. Contributions and corrections:

GitHub

GitHub - bitcoin-data/invalid-blocks: Dataset of invalid blocks observed on the Bitcoin network.

Dataset of invalid blocks observed on the Bitcoin network. - bitcoin-data/invalid-blocks

Time to give my 10 year old servers another 10 years of life 😬

Palm Cove Bitcoin Bush Bash was a fucking blast Met a bunch of people who I previously only knew online, and also a bunch of new people too Everyone brings their own views and experiences, but all united by Bitcoin Looking forward to next time ❤️ @bitcoinbushbash

I travelled from Perth to Palm Cove (~5000km of travel via Melbourne) just for a re-up of @Soap21

I've published my Bitcoin merge-mining research repo: data and tooling for about 26 chains that have merge mined with Bitcoin. Recovered stale blocks a focus. Or, put another way, I ran nodes for about 20 non-Bitcoin 💩 chains, so others didn't have to!

GitHub

GitHub - deadmanoz/merge-mining-research: Bitcoin merge-mining research

Bitcoin merge-mining research. Contribute to deadmanoz/merge-mining-research development by creating an account on GitHub.

Self hosting will increasingly become necessary, for privacy AND defensive purposes Recount from huggingface regarding a recent security incident, model provider guardrails hampered investigation and response effort, fortunately they could self host

Security incident disclosure — July 2026

We’re on a journey to advance and democratize artificial intelligence through open source and open science.

AI Psychosis in software dev is having to read phrases like “load-bearing”, “seams”, “sidecar” constantly

It might be true.. I’ve been using Kimi occasionally for a few months, mainly only when I had no usage remaining on Claude/Codex, because it was much, much weaker But K3 does actually seem to be a very capable model from my brief experimentation Now if only I had the hardware to self host it 🥲

It has been a while, good return - daughter “slayed it” WORD5 #650 3/6 ⬛⬛⬛🟧⬛ 🟪🟧🟧🟧⬛ 🟪🟪🟪🟪🟪

WORD5

In a matter of a few hours I’ve got a completely private via Signal and self-hosted LLM (qwen2.5-tools) agent to interact with and use. It’s “self-configuring” and pretty capable for what it is (32B parameter model). It’s a tool I can comfortably use with my private documents, without worry of leaking to a provider. I understand the hype..