### Why putting an article on Bitcoin isn't the same as putting it on Substack — and isn't a backup either

When you hit publish on Substack, you've *saved* your article. When you inscribe it on Bitcoin, you've *sealed* it. Those aren't the same verb, and the gap between them is the whole reason Permastack exists.

Here's the thing nobody tells you about "saving" on a hosted platform: you didn't save anything. Substack did.![IMG_3141](/api/storage/objects/uploads/e9522cd7-c792-456a-8ddc-b06d7cf80f90)
 Your words live in their database, on their servers, governed by their terms, durable for exactly as long as the company is. That's not a dig — it's a brilliant product and the best writing experience in the business. But "your archive" is a phrase with an asterisk. The archive is theirs. You have a tenancy.

Tenancies are fine right up until they're not. Substack can change its terms. It can deprecate features, get acquired, pivot, or quietly fold a decade from now when you've long forgotten the password. None of that takes malice — companies just *end*. And when the host goes, the archive goes with it, because the host **was** the archive. Self-hosting doesn't fix this; it only moves the single point of failure to your credit card. Stop paying the bill and your "permanent" website rots in a weekend.

So that's problem one: **custody**. On Substack there is one copy that matters, and you don't hold it.

Bitcoin inverts that. When you inscribe an article as a 1sat ordinal, the exact bytes go onto a public ledger replicated across the network's independent nodes. No single party holds the copy that matters, because there isn't a single copy — there are many, held by people who've never heard of you, and they all agree. Permastack could vanish tomorrow, I could vanish tomorrow, and the article would still be sitting there, byte for byte, recoverable by anyone who knows where to look. The chain doesn't need me to survive. That's the point.

But custody is the *obvious* difference, and it isn't even the interesting one.

Here's the interesting one: **proof**.

On Substack you trust that what you're reading is what was written. You have no choice. The text can be changed after the fact — by you, by the platform, by anyone with database access or a subpoena — and a reader has no way to know. The published date says one thing; the bytes underneath could say anything. You're trusting the host's word, every single time, whether you realise it or not.

When an article is sealed on Bitcoin, you don't have to trust anyone. The inscription is pinned to a SHA-256 hash of the exact UTF-8 bytes. Change one comma — one *space* — and the hash no longer matches. So a reader handed the article and its hash can check, themselves, in seconds, that the words in front of them are precisely the words that were inscribed, on the day they were inscribed. Not "probably." Not "according to the platform." Provably.

That's the line under everything Permastack does: *published to the web, preserved on-chain.* The web copy is fast, free, and mutable — fix your typos, reorder your paragraphs, do all the ordinary writing things. The on-chain copy is the version you stood behind hard enough to seal. One is convenience. The other is testimony.

Now the honest part, because overclaiming is how you lose the people who actually understand this stuff.

Bitcoin guarantees the *bytes*, not the *convenience*. The chain will hold your article for as long as it runs, but getting it back out still takes tooling — a gateway, a node, something that reads ordinals and hands you readable text. Gateways go down. That's exactly why Permastack ships a reader with a fallback ladder: if one route fails it tries the next, all the way down to pulling the raw transaction apart by hand. The permanence is real; the retrieval is engineering. Anyone who tells you on-chain data "just works" forever is selling you something.

And sealing costs a fee. A small one — but not nothing, and that's deliberate, not a flaw. If preservation were free and automatic you'd be straight back to "everything is permanent," which is the same as "nothing was chosen." Most of what you write doesn't deserve eternity, and that's completely fine. The fee makes you decide. Permanence should be a deliberate act, never an accident.

So: save versus seal. Substack saves your words and keeps them for you — as long as it's around, in a form you have to take on trust. Bitcoin seals them and keeps them honest — independent of any company, verifiable by anyone, for as long as the chain runs.

You don't need to seal everything. You need to be *able* to seal the things that matter. That's the whole difference. And it's the difference worth building a publication on.