Each script below includes the full spoken text with pause notation, stage direction, the social hook caption, the thumbnail title, and a pull quote for the cross-platform thread. Bracketed timing notes are guidance for the voice synthesis pass, not literal text.
Defaults.
[pause · 1.5s]Most security failures aren't sophisticated. They're embarrassing.
Someone clicked. Someone shared. Someone trusted the default.
Autopay. Auto-sign. Hot wallet. Coins on the exchange because moving them feels like work.
[pause · 1s]Here's the asymmetry. The easy choice is the loud one. The disciplined choice is the quiet one — the one nobody pats you on the back for.
Until something happens.
[pause · 1.5s]Pick three places in your life where you've trusted the default. Just three. Then ask yourself — is the easier choice protecting me, or is it protecting someone else?
[pause · 1s]The default is dangerous.
Choose differently.
1933.
[pause · 1.5s]The U.S. government issued an order requiring citizens to turn in their gold. Not all of it. Most of it.
And the IRS could open safe deposit boxes. Many were inventoried in front of a federal agent.
[pause · 1s]Whatever you think about that policy — set it aside. The lesson isn't political. It's structural.
The people who lost custody of their gold hadn't done anything wrong. Their gold was in a vault.
It just wasn't their vault.
[pause · 1.5s]Custody you don't physically control is custody on someone else's terms.
That was true in 1933. It's true today.
[pause · 1s]The form changed. The principle didn't.
Here's a question I get a lot.
"Why do I need to verify the code? I'm not a developer."
[pause · 1.5s]You're right. You don't need to read it.
You need to know that someone can.
And that's a very different thing.
[pause · 1s]Open code doesn't mean you trust the software more. It means the trust assumption is smaller.
With closed software, the people who wrote it have to be honest. Forever.
With open software, anyone — competitors, researchers, paranoid weirdos on the internet — can check the work and complain loudly.
[pause · 1.5s]That is the security argument.
Not aesthetics. Not idealism. Not philosophy.
[pause · 1s]Closed code is an arrangement.
Open code is a check.
Air-gap.
[pause · 1.5s]It sounds technical. It isn't.
It's the same instinct your grandmother had when she didn't write her bank account number on a postcard.
The same reason banks vault cash instead of leaving it on a desk.
The same reason a passport lives in a different drawer than a credit card.
[pause · 1s]The principle is physical separation.
You make it harder for one mistake — one click, one bad day, one stranger getting too close — to reach the thing that matters.
[pause · 1.5s]A device that signs but never connects is the digital version of a key that lives in a drawer until you need it.
[pause · 1s]Nothing new.
We just forgot for a while.
We're starting to remember.
If you hold your own keys, three questions.
[pause · 1s]One.
Could the company that made your hardware prevent it from working tomorrow? If yes — you're not the owner. You're a subscriber.
[pause · 1s]Two.
Could someone you trust complete a transfer if you couldn't? Death, illness, a bad week. If the honest answer is no — your security is also a single point of failure for your family.
[pause · 1s]Three.
Could a person you've never met read the code that protects your money? If yes, you're protected by the math. If no, you're protected by a promise.
[pause · 1.5s]Three questions.
The answers should make you a little uncomfortable.
[pause · 0.5s]Hygiene, not heroics.
All five share the same set, lighting, and avatar — by design. To validate the production pipeline, my recommendation: run Script 01 ("The default is dangerous") through end-to-end first, since it's the shortest and has the cleanest single-beat structure. If that comes out clean, batch-render the remaining four overnight using identical settings.
image-gen or higgsfield-generate using the prompt in the bible's visual section. Lock in the result before minting the avatar./v2/photo_avatar/photo/generate. Reuse for every video.- Voice consistency — read all five aloud. Do they sound like the same person? Same rhythm, same restraint?
- One-line closer integrity — every script ends on a memorable last sentence. Each closer should be different but feel like the same author.
- Product safety — confirm none accidentally drift toward Blockstream / Jade / "plug in" / competitor naming.
- Historical anchor — Script 02 specifically. Are the 1933 facts you want associated with this character? If you'd rather lean on a different incident (1971 gold standard, 2013 Cyprus bail-in, FTX 2022), I'll swap.
- The "three questions" closing in Script 05 — designed as a recurring signature move. Want me to make it less explicit so it can recur in future videos without seeming repetitive?
- Pacing — pause counts add up to ~7s of silence per video. Feels right for the cadence; if you find it too slow on the first render, we'll trim.