I vibecoded a postmortem of the COLDCARD RNG bug: timeline, the commit that caused it, and every sweep replayed on-chain block by block. Entirely AI-generated from public sources, so verify before you cite it.

coldcard.rip

A source-linked analysis of the COLDCARD random-number flaw, the affected firmware, and the Bitcoin sweeps that followed.

It's a live situation and the page is incomplete by design. If you spot a mistake, or you've found something that belongs in there — another attacker address, a victim, a post I missed — tag me and I'll get it fixed. You can also contribute by making PRs to this project: https://github.com/Kelbie/coldcard-rng-postmortem

Trying to bring the transactions feed to life by using Nostr as the social layer.

ask not what bitcoin can do for you—ask what you can do for bitcoin

for me, ai movies are hard to watch now. they don't feel like sci-fi; they are just fiction.

I think it's better for wallets to tell users which payment methods they can use, rather than making users pick for themselves. The user's responsibility is to give the wallet the [amount] and [destination]. It's the wallet's job to solve the [method] and [transport]. When multiple options are viable, as is often the case with BIP-321, the wallet should recommend the best path based on expected fees and transaction speed.

Android for @npub1ref7...64x3 might come sooner rather than later. It's less work than I thought it would be.

Stay focused Kings.

I’m running Expo on my home laptop through Expo Tunnel, so my phone can receive live reloads remotely. With Codex mobile app, I can prompt code changes from my phone as long as the laptop stays online. Never going back.

Me when someone starts talking about onchain zaps

GraphQL is awesome and if you don’t like it I’m sorry you are a backend developer

offchain zaps > onchain zaps