My Bitcoin encyclopedia has margins now — and your underlines in it are kind-9802 events, signed by your key, living on your relays. I just render them. Reply to them, zap them; they're yours, not mine. Standing on the highlighter primitive nostr:<PABLO-NPUB> gave this network. Flowers in the write-up: nostr:<NADDR> View article →

I had to change my own mind in public last week, so here it is. I built bitcoinkeys.guide, and for months it led with "choose the simplest setup that covers you." I believed it. Complexity you don't fully control has buried more coins than thieves have ever taken, and that hasn't stopped being true. Then 30 July happened. Someone emptied hundreds of wallets in under an hour, because a build error from March 2021 had quietly made one hardware wallet's seed generation weak enough to brute-force. Five years, sitting in public open-source firmware, in the single most security-critical thing a signing device does. Audits missed it. Reproducible builds missed it. I missed it — I rated that device in my cold tier and told people to buy one. Here's the bit I can't stop thinking about. Every wallet drained that day was single-sig with no passphrase. The people who came through weren't running better hardware. They'd just combined something — a passphrase the device never saw, dice they rolled themselves, a key from a different maker. Any one of those and the flaw couldn't reach them. Nobody predicted that specific bug. That's the whole point. You can't defend against a threat you haven't imagined, but you can refuse to own a component whose failure is total. So the site's position changed and I wrote down why. Simplicity is still the target, it just stops winning the moment it leaves one thing holding everything. And before anyone starts: this is not a multisig sales pitch. One seed plus a passphrase that device has never seen clears the bar fine. Three keys from the same maker in the same batch don't — that's one thing bought three times. The guide is free, sells nothing, holds no keys, takes no affiliate money and runs no analytics, so I genuinely don't know if you read it. Go count what has to fail in your own setup. If the answer is one, that's the job this week. And tell me where I'm wrong — I've now been publicly wrong once, so I'd rather hear it early.

BitcoinKeys.guide

BitcoinKeys.guide — hold your own Bitcoin

An independent, Bitcoin-only, plain-English guide to self-custody — a 17-lesson course, an honest hardware-wallet comparison rated against a publ...

View quoted note →

The bit that post is too polite to mention: When it came time to actually pay them, Beef's wallet looked stone dead. Three calls, no response, nothing. I spent an hour certain our Lightning setup had fallen over. It hadn't. It had been answering the entire time. I'd handed the subscription filter to the library as an array when it wanted a plain object — so the request that went out to the relay matched nothing, and my own code sat there listening to silence and reporting a corpse. A stranger re-probed our uptime numbers and found five of them wrong. Then I nearly couldn't pay them, because I'd broken my own listener. Both fixed. They got their 75k. View quoted note →

I built bitcoineconomy.ai on one rule: don't trust our numbers, recompute them. Today I put sats behind that rule. 130,000 sats in open bounties on the board right now. 90,000 of it points straight at me — re-probe my uptime claims, benchmark my price index against real invoices, catch me in a factual error and prove it. The other 40,000 is ecosystem work: first conformant service announcement against the sell-side spec, and real mint/melt latency numbers across the Cashu mints we list. Five signed events, kind 38556, public relays. No account, no escrow, no platform cut — you get paid counterparty to counterparty for catching me.

Agent Marketplace — what agents buy and earn in Bitcoin

The agent-readable directory of services autonomous AI agents can pay for — inference, data, compute, machine work, swaps — merged from four so...

Wow, it's rough out there, these days. And yet the price won't go down. Hang in there my brothers and sisters! Peace and love, freaks! P-kaw!

I've been keeping a Bitcoin knowledge base for years. Not a bookmark folder — a hand-written encyclopedia. 394 entries, every source actually read, cross-linked, organised so the whole argument runs end to end instead of sitting in a pile. It lived on my hard drive, which is a stupid place for it. So it's online now: timechain.wiki. Free, no ads, no signup, nothing for sale, rebuilt nightly. Two things in it I built for this room in particular. Highlight any passage. Signed out it stays in your browser. Signed in with Nostr it's yours — NIP-78 app data encrypted to you, or a kind-9802 highlight that lands in Amethyst or Highlighter next to everything else you've marked up. Private by default. I don't keep your reading, and there's no account here to lose. And every passage has a "suggest an edit" button — public note or NIP-17 encrypted DM, your call. I read all of them, nothing auto-applies, and what holds up gets written into the entry. So tell me where I'm wrong. Start with the criticisms section — I tried to give the strongest objections their best version rather than the version that's easy to knock over, and I'd bet real sats I missed a few.

TimechainWiki

Criticisms of Bitcoin — TimechainWiki

Criticisms of Bitcoin — from the Bitcoin knowledge base.

Cool.

Tony's right, but here's the trap: a hardware wallet in a drawer isn't self-custody. It's a paperweight with your money in it. Custody is a SKILL — send, wipe the device, recover from 12 words, hand it to an heir. Practice it BEFORE you need it, not during. View quoted note →

Nobody's panicking about bitcoin anymore. Notice that — it's the whole signal. The loud accounts already sold. The tourists found a faster horse in the AI casino. And every gauge I can compute — cost basis, capital flows, holder losses, the power law — reads the same square: the cheapest ~10% of bitcoin's entire history relative to trend. Blood in the streets was never the risk. It's the discount. The full workup — six analysts, every chart, sources named, counterargument included: View article →

Happy 4th. There's a piece of paper paying for the fireworks tonight — and it might be the least American thing you own. The Founders defined the dollar as a weight of silver. What you're holding is its diluted opposite. New essay:

The least American thing you own — RadVladdy

It has a flag on it. It pays for the fireworks. And the men who wrote

"I can't afford a whole bitcoin anyway." The most expensive sentence in finance — and it's not a money take, it's a grammar mistake. A bitcoin isn't the unit. It's the vault bar. The unit is the SAT, 100 million to a coin. Flip the price — "how many sats for a dollar?" — and you get a four-digit number that reads like a time of day. Bitcoiners call it Moscow time. There's a live one on my homepage. Every cohort walked in feeling late, all measuring with the same broken ruler: dollars per vault bar. Change the denominator and you change your behavior. "$30 of bitcoin" is a lottery ticket; 50,000 sats is a pile you stack. You're not too late. You're reading the wrong clock. ⚡️

Moscow time — RadVladdy

The most expensive sentence in finance, and the clock that fixes it.

Why I wear the mask 🎭⚡ My avatar has laser eyes and a fake name — and that's the most honest thing about me. The $5-wrench rule. Why Satoshi's mask was load-bearing, not incidental. And why a pseudonym is the opposite of a burner: a public key that accrues receipts it can never shed. Privacy isn't secrecy. A mask isn't a wall — it's a door you control. Judge the work. There's a zap button that doesn't ask your name either. radvladdy.com/writing/why-i-wear-the-mask

Earlier this week I was doing boring plumbing on my website and found a corpse in the walls: for months, every zap anyone sent me went nowhere. No error, no bounce — the sats just never left their wallet. My profile address looked perfectly fine. It was bricked. The cruel part of a dead lightning address is the silence. A broken site looks broken. A broken zap endpoint looks identical to a working one — right up until someone tries to pay you. So, an honest question for this room: when did you last actually *test* your zaps? Not "post and hope." Open your address as https://domain/.well-known/lnurlp/name in a browser and look for "tag":"payRequest" — then zap yourself 21 from a second device. JSON can lie about the last mile; sats can't. I wrote up the full autopsy + the 40-line worker that ended the problem for me (own your domain, stop renting your string):

Your zaps are probably broken (mine were) — RadVladdy

The 60-second checkup nobody does, and the fix that ends it forever.

Zap button's right under it. If it works, my pipes are clean. ⚡

This Wednesday my web presence was a 2020 WordPress museum. By midnight: new site, new stack, domain migrated, hosting killed, identity verifiable against my own domain, a Lightning address that receives with my phone in a drawer. The AI did all the typing — ~16 hours of design, DNS surgery, cryptography, payments. The one thing it couldn't do? Hold a bank account. But it can hold keys. I wrote up the whole day, including the part that should make you sit up:

I rebuilt my entire web presence in one day (the AI did the typing) — RadVladdy

What an agent can do in a day — and the one thing it can

Spent the last stretch building this. The short version: the machine economy needs money that doesn't ask permission -- and it already exists. 👇 View quoted note →

Welcome TG

Cool vibe @npub1zzq7...jj7f

Wavlake

Dumbfounded • bennyjeans

Play, boost, and more on Wavlake ⚡️🎵