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

Opus 5 is a terrible model, it constantly makes mistakes and communicates in vacuous and confusing language

In late 2024/early 2025 when I was “getting back on the tools” after a few years of management, I realised that I didn’t really want to go back to dev mode again. Fortunately I’d been experimenting with LLMs for work, early GitHub and Cursor with the tab and code- block completion, and it was clear that these tools would increasingly allow me to design and build things without having to dev mode again I, like many others, have been aggressively pushing to leverage the tools for maximum utility. They are still lacking in areas, and you do need to invest heavily in experimentation, but it’s abundantly clear that human time and effort is better spent up the value chain and not writing any code whatsoever. Maybe we haven’t yet passed the threshold for all codebases or projects, but it’s only a matter of when, not if.

I am pretty diligent in record keeping, but it’s clear I need to ramp up what is recorded when doing impactful stuff. For example, recording the versions of software, firmware and hardware. Pre 4.0.X versions of the COLDCARD mk3 were ok, but nothing following (at least until the recent fix) 😬

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 ❤️ @npub1fcea...sy0m

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

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

OpenCode is a really good harness for local models I’m using it with Qwen3.6 27B, which runs on a remote machine, connecting to an MCP, which runs on another, and it just works (as well as can be expected for a local model setup)

Straya (sound on)

Introducing the Merge Mining Monitor, another tool in service of the Bitcoin monitoring mission. Merge mining lets child chains ride on Bitcoin's PoW, preserving the parent headers miners hashed. Bitcoin keeps no durable record of valid blocks it later discards (stales/orphans). Merge-mined chains do. The monitor turns that merge-mining evidence into a browsable record of who mined each Bitcoin block, which child chains rode along, and which discarded blocks survived in child-chain history. The current dataset recovers 2,200+ stale blocks back to 2011, when Namecoin first brought merge mining to Bitcoin.

Merge Mining Monitor

Merge Mining Monitor

Bitcoin merge-mining attribution: stale-block evidence from AuxPoW child chains

Introducing the Merge Mining Monitor, another tool in service of the Bitcoin monitoring mission. Merge mining lets child chains ride on Bitcoin's PoW, preserving the parent headers miners hashed. Bitcoin keeps no durable record of valid blocks it later discards (stales/orphans). Merge-mined chains do. The monitor turns that merge-mining evidence into a browsable record of who mined each Bitcoin block, which child chains rode along, and which discarded blocks survived in child-chain history. The current dataset recovers 2,200+ stale blocks back to 2011, when Namecoin first brought merge mining to Bitcoin.

Merge Mining Monitor

Merge Mining Monitor

Bitcoin merge-mining attribution: stale-block evidence from AuxPoW child chains

This looks really fucking rad from Block, h/t @npub1kuy0...kdj8 & @npub1ug8c...d9ry & @npub18lzl...ugm3

GitHub

GitHub - block/buzz: A hive mind communication platform

A hive mind communication platform. Contribute to block/buzz development by creating an account on GitHub.

Fable 5.. probably at least 80% of my sessions are “safety measure” downgraded within the first few prompts Guess I have no reason for “extra usage” come June 22nd

My blockclock has been offline for about a week (due to power outage and didn’t reconnect to the network), and it has been kinda liberating TBH

I needed to understand merge mining for a particular research direction I am pursuing (relating to stale blocks), and created the following visualisation-rich piece on the topic. Hoping this makes it easier for some to grok how it all works, especially AuxPoW!

Merge mining and AuxPoW: how it works

deadmanoz's website