S14 E9: Jameson Lopp on Casa, Self Custody & Bitcoin Maximalism
The audio keeps playing while you browse the site.
Read the transcript9,139 words, every line links to the minute it was said
Ask this episode
We recorded in August 2023, and the room was hot enough that I opened the episode with a joke about the studio heat. Jameson Lopp, CTO of Casa, joined me for an hour that started with his old job at BitGo, wandered through the short life of the Casa Node, and ended up in a long argument about what maximalism is for. He has also written a history of Bitcoin maximalism and keeps a running review of metal seed backups, and I had questions about both.
I started with the career change. People who followed his path from BitGo to Casa tend to assume it was a strategy decision, and I wanted to know whether I had it right.
Leaving BitGo for the Harder Path
The reason Jameson gave was physical before it was philosophical: "my sleep was being affected." Enterprise custody carries a particular kind of stress, since a mistake there lands on a lot of other people's money. What he wanted instead was work centered on "helping individuals help themselves and be their own bank."
He described the individual route as the more difficult one, and he chose it knowing that. In his words, he "wanted to continue pushing forward in what I believe is the harder path, which is getting people to take responsibility and take custody and do what I think is best." Custody for institutions has a clear customer who pays a clear price. Custody for individuals means convincing millions of people to take on a chore they currently hand to an exchange.
A later episode picks this thread up: Mike Belshe on BitGo, self custody and the future of Bitcoin. On this episode, the thing Jameson keeps coming back to is a force he calls "the looming threat of convenience," which is what pulls people toward custodians the moment self-custody gets fiddly.
The Casa Node Autopsy
I had a personal stake in the next topic. In early 2019 I was a Casa Node user, and I remembered the automated Lightning micropayments the company sent out as rewards for keeping your node online. It was a cute mechanism, and I had assumed it signaled a company with a big node-in-a-box future. So I asked what happened.
First he fixed my timeline. "A lot of people actually misunderstand the timeline of Casa," he said, and the node came after the 2018 multisig service, not before it. The service was the core product from the start, and the node was added later as something that complemented it.
The numbers behind the shutdown were unglamorous. The market for a plug-in full node is "probably fewer than 10,000 people total, and it's mostly hobbyists and tinkerers." Hardware is expensive, support for hardware is its own business, and the margins do not rescue you. "It's very difficult to pull that off and scale it as a profitable business." He pointed to earlier attempts that ran into the same wall, namely the Bitnodes hardware and John Light's Bitseed project.
Support was the other half. In his description, "when you are deploying hardware into unknown environments and unknown networks, there's a huge surface area of unanticipated sort of edge cases and things that end up going wrong." One customer's router does something odd, another's ISP blocks a port, and the support queue fills with problems that have nothing to do with Bitcoin. I also asked whether investors ever asked about adding Litecoin support alongside Bitcoin. He said no real customer demand existed for it.
What a Multisig Subscription Buys You
Casa's subscription confuses people, so I asked him to lay it out. The software does not hold your funds. The keys stay with the user, and one result is the line he used for what happens if the company disappears or you stop paying: "Casa can't do anything." If you let a subscription lapse, you keep control of your keys and can sweep the funds to any address you like.
What the subscription pays for is recovery help and humans on the other end of a support channel. There is also a quieter piece of the design. Casa backs up the public keys and derivation paths for your multisig, and this matters more than it sounds. In Jameson's words: "If you lose any of the public keys that go to that multisig, that could actually be a catastrophic loss." You can hold two of three private keys, with every backup intact, and still be stuck if you no longer know the full set of public keys that built the wallet.
The same design philosophy covers user error. He said, "we're trying to set these up to help people put themselves in a very robust position so that they can make mistakes." Everyone loses a device eventually or forgets which drawer a backup went in, and the point is to survive the first mistake.
Multisig does not run itself, and he said so plainly: "it's not a set-it-and-forget-it type of operation." Firmware gets outdated, and an outdated device can turn into a lost key. So the app runs health checks. "A health check in our app, basically, it's, you know, doing a Bitcoin signed message. So it's just proving that you still have the ability to cryptographically sign with your keys." It sounds trivial, but it catches a dead device or a forgotten passphrase while you still have time to fix it.
He did not oversell the effort: it "certainly requires more work than just putting 12 words on a metal plate and burying it in the ground for 30 years."
I also asked about Ethereum, since a Bitcoin-first company supporting it raises eyebrows. Jameson said customers wanted a multi-asset custodian, and that "we actually had beta Ethereum support in the mobile app" before it became a regular feature. It can be switched off, so a Bitcoin-only user never has to see it. One more thing he said on custody trade-offs: "as a result, that means people are using key management devices from other companies, other vendors that we have no control over." Casa chooses to support hardware it does not make, which is part of why the health check exists.
Why Shamir Falls Short of Multisig
I wanted his view on SLIP-39, Shamir Secret Sharing, since it comes up every time someone discovers that metal backups can be split. His objection starts with how recovery works: "you basically end up having to reconstitute all the keys in a single location." At the moment of recovery, the whole secret exists on one device in one room, which is the exact exposure you were trying to avoid when you split it up.
The second objection is about auditing. With multisig on the chain, "it's literally on the blockchain," and he added that any observer can see which public keys correspond to which signatures. In his description, "any type of multisig that you're doing on the blockchain, you know, all of those public keys that are being used and all of the relevant signatures, you can see which public keys they correspond to." Shamir shares leave no trace of this kind, so you cannot verify the setup from the outside.
Flexibility is the third. In multisig, "you're not married to any one of your keys in your key set." You can swap a compromised or lost key for a new one by moving funds to a new wallet, and Shamir is, as he put it, "a bit more rigid, whereas multisig is a bit more flexible."
He is realistic about the reason people still reach for it: "the less parts there are involved, the less potential points of failure there are."
Seventy Backups, a Hydraulic Press and a 9-Volt Battery
This was the part I had most wanted to talk about. Jameson has tested roughly 70 to 75 metal seed backup products, and the reviews are public. I asked what the testing involves, and the answer is fire, corrosion, and a 20-ton hydraulic press meant to simulate what happens to a plate when a building collapses on it.
His design preference came out of that process: single-piece metal with a punched grid wins over tile-based systems that you assemble. The reasoning is mechanical. Loose tiles can scatter or shift under impact, and a single plate cannot. About marking methods, he said, "the best format and really easiest format seems to be the simple straight punch, just putting a divot into a grid somewhere."
Within the Cryptosteel line, he prefers the Capsule over the Cassette because of structural integrity under pressure.
The most resilient marking technique he has found is also the most homebrew. Acid etching, done at home with wax, a 9-volt battery, saline solution and electrodes, outlasts everything else he has put through the testing. It sounds like a chemistry-class demo, and it also survives a lot of abuse.
Maximalism, Right-Winger Labels and Your Enemies
We went from metal plates to the culture war, which is where I like to end up. Jameson described the origins of maximalism as defensive: "maximalism really started out as a rejection of people trying to print their own money with cheap copied projects." HEX came up, and he described its claim "that you were staking HEX, but it wasn't even staking." On the technical side, "in reality, no one really cares what mining algorithm powers a network other than the miners themselves."
He thinks it turned ugly later. "I think things really came to a head, though, during the scaling wars," he said, and people ended up "absorbing the memetics of toxic maximalism" as a standard part of belonging.
I offered a theory, which was mostly a joke. Europeans are more reasonable about it. In the United States, a lot of people read The Bitcoin Standard and then adopt maximalism as an all-encompassing identity. Jameson did not argue, and instead described it as "more of a sociological phenomenon" than a technical position.
He also took exception to the way American libertarians get labeled. "When you get called a right-winger, it always means you're like a Trump supporter or whatever, which is ridiculous. But that's something that I think American libertarians have had to deal with for many years." His own description: "I'm an avid anarcho-capitalist. I'm not a winger of any kind." And what comes first is the work: "I'm a technologist first."
His practical conclusion about other networks was blunt. "This is a space of permissionless innovation and people are going to have demands for functionality that probably shouldn't be on Bitcoin. And that's okay." The consequence, in his view, is that policing other chains is a waste of effort: "If you don't want that stuff on Bitcoin, it seems kind of silly to be yelling at people for doing it on other networks."
Near the end I asked whether he would be at Baltic Honeybadger in Riga. He will be in Europe around then and is skipping the event. We also fumbled the scheduling for the recording itself, which I blamed on what I called fiat time zones, and Jameson repeated the phrase back to me with a laugh as the episode wound down.
His last long thought was about enemies, which is the line I would have picked for the thumbnail. "Bitcoin is for enemies. So support your enemies." He followed it with the reason: "Whenever you have a large enough number of people paying attention to you, someone will find reasons to declare you to be an enemy."
Listen to Jameson Lopp on Spotify, Apple Podcasts, YouTube, and More
Time stamps:
- 00:00:00– Intro and Sponsors (Wasabi Wallet, Cryptosteel, ShopinBit, Satodime)
- 00:01:08– Welcome Jameson Lopp, CTO of Casa
- 00:02:21– Any Regrets About Leaving BitGo?
- 00:04:10– BitGo vs. Casa: Multisig for Companies vs. Individuals
- 00:04:39– Self-Custody vs. the Threat of Convenience
- 00:05:57– What Happened to the Casa Node?
- 00:07:25– Casa's Real Timeline: Multisig First, $10,000 a Year
- 00:08:45– Why Node-in-a-Box Businesses Die Off
- 00:10:45– The Hidden Cost of Supporting Hardware
- 00:12:31– Lightning Rewards, Jack Dorsey and the Casa Node Unboxing
- 00:14:13– Usability as Casa's Ethos
- 00:15:00– No Single Points of Failure
- 00:16:24– Ad: Wasabi Wallet
- 00:17:17– Does Jameson Use CoinJoin?
- 00:18:30– Donations and Privacy
- 00:19:03– Why Use Casa Instead of Electrum and Hardware Wallets?
- 00:20:58– Losing the Wallet Descriptor Can Be Catastrophic
- 00:22:33– Sovereign Recovery Instructions
- 00:23:15– What You Pay For: Human Support
- 00:24:07– Free, Standard and Premium Plans
- 00:25:36– Why Casa Added Ethereum
- 00:28:49– Stablecoin Plans
- 00:29:00– What Happens If You Stop Paying?
- 00:30:26– The Incentive to Renew
- 00:30:57– Health Checks
- 00:33:15– Multisig Requires More Work
- 00:34:05– Ad: Cryptosteel
- 00:35:07– SLIP-39 Shamir Secret Sharing vs. Multisig
- 00:36:40– Auditability and Key Rotation
- 00:38:56– Public Keys on the Blockchain
- 00:39:25– Metal Backup Reviews and Benchmarks
- 00:40:16– Keep It Simple: Lessons from 75 Devices
- 00:41:44– Cryptosteel Capsule vs. Cassette
- 00:43:30– The Schrödinger's Cat Backup
- 00:43:56– Why a 20-Ton Hydraulic Press?
- 00:44:42– A History of Bitcoin Maximalism
- 00:47:18– Dash Masternodes and HEX "Staking"
- 00:48:22– Toxic Maximalism and the Scaling Wars
- 00:49:04– The Pandemic Wave of Maximalists
- 00:50:51– Mass Adoption Without the Masses
- 00:51:04– Ad: Satodime
- 00:51:58– Maximalism as a Lifestyle
- 00:52:51– Anarcho-Capitalist, Not a Right-Winger
- 00:54:17– A Technologist First
- 00:54:54– The "Running Grin" Tweet and Ethereum's Pre-Mine
- 00:56:39– Permissionless Innovation
- 00:57:02– Counterparty, Rare Pepes and NFTs on Bitcoin
- 00:58:15– "Bitcoin Is for Enemies"
- 00:58:37– Fiat Time Zones and Goodbye
- 00:59:29– Ad: ShopinBit
Verify this episode
This is the SHA-256 fingerprint of the MP3 as published here, timestamped in the Bitcoin blockchain with OpenTimestamps. If one byte of the file changes, the fingerprint changes.
- SHA-256
a1c15e8934f68fa51788f1fa38234b14066d9978d1f31d4dafcebba7faeb7098- Proof
- 2023-08-23_s13_e9_jameson_lopp_on_self_custody_and_bitcoin_maximalism.mp3.ots · all episode hashes (proof)
- Status
- Anchored in Bitcoin block 974,312
- Timestamped
- After release. The episode came out on 23 Aug 2023, but this proof was made on 3 Nov 2026 and anchored in block 974,312, so it proves this exact file existed by 3 Nov 2026, not on the release date.
How to check it yourself
- Download the MP3 and the proof into the same folder.
- Run
sha256sum 2023-08-23_s13_e9_jameson_lopp_on_self_custody_and_bitcoin_maximalism.mp3(on a Mac:shasum -a 256 2023-08-23_s13_e9_jameson_lopp_on_self_custody_and_bitcoin_maximalism.mp3). The result must match the SHA-256 above. - Install the OpenTimestamps client (
pip install opentimestamps-client) and runots verify 2023-08-23_s13_e9_jameson_lopp_on_self_custody_and_bitcoin_maximalism.mp3.ots. It hashes the MP3 again and checks the proof against your own Bitcoin node, then prints the block and the date the file existed by. Without a node,ots info 2023-08-23_s13_e9_jameson_lopp_on_self_custody_and_bitcoin_maximalism.mp3.otsshows the block height to look up in any block explorer.
Related
S17 E42: Bob Summerwill on Ethereum Classic & Bitcoin’s Fork Season
I first met Bob Summerwill in person at the Proof of Work Summit in September 2023: the event where Bitcoiners, Litecoiners…
S17 E24: Zach Herbert on Passport Prime, KeyOS & the End of Air-Gapped
Some interviews you plan for weeks. This one I planned around a box. Two weeks after Zach Herbert handed me a Passport…
S15 E66: Jameson Lopp on Michael Saylor, Bitcoin Ossification & Paranoid Crypto Anarchism
Jameson Lopp on Michael Saylor's paranoid crypto-anarchist line, Bitcoin ossification, Lightning, Drivechains, the 21 million…
Comments
Comments run on my own server. No trackers, no tracking cookies.