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

It's pretty dumb that Nostr apps that rely on caching servers can just go offline if the server stops responding. For this reason I spent the last week making @Sovran have fallbacks so as long as some relays are online you will continue to have some level of functionality but in the best case you get the caching server user experience.

Another day of building the Nostr app I want to use. Latest: in-post web view. Open any linked site without leaving the conversation. Available in next release of @Sovran

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 @Sovran 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

Built loading skeletons for Nostr threads that don't jump around when content arrives. Measure each reply's real height, sort them so they fit the skeleton slots, then a shimmer pass masks any leftover shift.

Send me dms on whitenoise to npub1r50s0c73z0fdz5rugwjrqq0slnuhdzwlf4g7363ryfx2q0gulv5qrn7cc5 im testing something

No internet? No problem. With @Cashu you can send ecash offline for specific amounts. For fiat-denominated payments, in @Sovran we will automatically select the closest sat value that can be sent offline. This is almost always within <$0.01 of the intended amount—so small that its not meaningfully different.

I’ve been working on a new offline send flow for @Sovran. With @Cashu, offline sends are possible, but only for specific denominations. Our approach lets users choose whether to round up or round down to the nearest valid amount, making it easier to adapt the send amount for offline use while still giving users a bit more control. I chose this approach instead of building a proof selector. In my testing, proof selection felt much more complicated for normal users. With this flow, the wallet automatically calculates the proofs needed behind the scenes.

working on a better offline send ux for cashu