I write long-form pieces on Bitcoin, macroeconomics and monetary policy. They range from a few hundred words to full analyses of debt loads, yield curves and the Bitcoin network itself. Every number in them comes from a named source and carries a date; where something could not be verified, the text says so instead of rounding it off.
Alongside the essays I write about freedom technology — the tools that let a person hold their own keys, publish without a platform, and move value without asking — and about AI, mostly the unglamorous question of what it can be trusted to do when the hardware and the data stay yours.
I publish these as NIP-23 long-form notes on the Nostr network under a single key. This site is not hosted on a web server in the usual sense: the files are stored as Blossom blobs, and a signed manifest event maps each path to the SHA-256 hash of its file. Any server that understands that manifest can serve the same pages. The identity holds the site together, not a domain.
The manifest is replaceable and signed with the same key as the articles. Only whoever holds that key can change what this site says — which, for now, is me.
A claim is worth more when you can reproduce it. These guides are written from machines I actually run, and every step in them was executed before it was written down. Where a step failed, the failure is in the text — that is usually the part worth having.
What it takes to hold your own keys and your own channels: LND behind Tor so the node never exposes a public address, a watchtower so a sleeping node cannot be cheated, channel fee policy argued from mempool data rather than intuition, and what to do when the node goes quiet. Includes the parts nobody mentions — certificate extensions, static channel backups, and the difference between a channel that is offline and one that is lost.
How this site is built, start to finish: a key, a set of files hashed by SHA-256, those files uploaded as Blossom blobs, and one signed manifest event that binds every path to its hash. No server, no domain, no account. Includes the failure modes that cost me an evening — a manifest with no relay list is invisible, a named site is only eight characters shorter than an unnamed one, and a font that is not embedded renders as something else entirely.
Running Bitcoin Core and the services around it on hardware you own, with pruning, backups and a health check that reports honestly. The rule throughout: if a number cannot be verified, it does not get written down.
Most writing about AI lands in one of two ditches: the model is either about to replace everyone, or it is a parlor trick. Neither is useful if you run things yourself.
The arrangement I care about is narrower and less dramatic: the machine, the files and the keys stay on hardware I control, and the intelligence itself is rented as an open-weight model when it is needed. That is a different trade from handing a provider your data and hoping the terms hold. It is also the older cypherpunk argument wearing new clothes — the part that matters is who holds the key, not how clever the software is.
I write about what that looks like in practice: what a local model can genuinely do and what it only appears to do, where an agent stops being useful, and why a machine that can repeat a clearing price still cannot discover one. Verification is the whole point. A model that says a task is done is making a claim, not providing a proof.
npub1dqjq6jfjj5py9yjyxnzmzxqrt2fyfz54wr90rl084m980tausrjq9e95y4
The same notes are readable in any Nostr client — search the key above, or open the profile directly. Long-form notes appear in clients that support them, and the profile carries a link back here.