Sep 1, 2026 · 46 min
Bitkey replaces seed phrases with layered Bitcoin recovery
Clay Garrett: Why Bitkey Has No Seed Phrase & How It Keeps Your Bitcoin Safe
The conversation shows how multisignature design can make Bitcoin self-custody more recoverable without removing the user’s responsibility to verify transactions.
- 1The Coldcard hack investigation highlights how transaction patterns, fees, and wallet reconnaissance can reveal an attacker’s methods.
- 2Bitkey uses two of three separately generated keys instead of a seed phrase, combining hardware, recovery, and inheritance tools.
- 3Recovery contacts, waiting periods, device verification, and Cash App integration expand access while introducing trade-offs tied to each user’s threat model.
Don't miss
Clay Garrett demonstrates a Bitcoin transfer while verifying the destination address and amount on Bitkey’s device before confirming it.
The brief
The Coldcard hack opens a broader security question: what can transaction patterns, fee behavior, and possible wallet reconnaissance reveal about an attacker?
Clay Garrett, who leads Bitkey at Block, describes a two-of-three multisignature system whose keys are generated and kept across separate environments.
Bitkey avoids a traditional seed phrase by combining hardware, encrypted recovery data, recovery contacts, and inheritance tools, each with explicit safeguards and waiting periods.
A live transaction demonstration makes the design concrete: the destination address and amount appear on the device, and the user must intentionally confirm them.
The episode frames self-custody as a set of trade-offs rather than a universal formula, with Cash App Auto DCA lowering the barrier to adoption.
What was said on this episode
29 statements · 20 positive · 4 negative · 5 neutral
The Coldcard hack did not affect BitKey.
“there was nothing that affected BitKey, you know, completely isolated to cold cards”
Listen at 1:48
Coldcard’s misconfiguration routed entropy through a deterministic software generator.
“it actually routed it through the software one. And it was even a deterministic one”
Listen at 2:50
Knowing the flawed seed allowed prediction of Coldcard’s generated random numbers.
“if you knew the seed, you could basically predict every random number that it would spit out”
Listen at 2:55
The attacker used a fee rate of approximately 30 satoshis per virtual byte.
“it was, I think, exactly 30 sats per vbyte”
Listen at 4:29
BitKey’s three keys were generated with 256 bits of entropy each.
“all three keys that are part of BitKey were generated with the desired amount of entropy. They were all 256 bits of entropy.”
Listen at 9:48
BitKey’s multisig requires a second key if one key is compromised.
“if one key is compromised, you still have to get a second key to actually move funds”
Listen at 10:24
Security-sensitive companies should run continuous code scans where possible.
“you need to be running, you know, 24-7 scans against your code where possible”
Listen at 11:43
Clay declines to judge frontier-model access policies given limited data.
“I also am not going to, you know, sort of sit here and pass judgment with a limited data set right now”
Listen at 13:13
BitKey customers own two keys while BitKey owns the third.
“The customer owns two of the keys. BitKey owns the third.”
Listen at 15:00
BitKey requires two of three keys to spend, and cannot spend without the customer.
“need two out of three to spend. You can spend without BitKey. BitKey cannot spend without you.”
Listen at 15:17
An encrypted BitKey app key is useless without the user’s unlocked hardware.
“If someone gets access to that for any reason, it's useless to them unless they have your unlocked hardware”
Listen at 16:14
BitKey generates its three keys in separate environments.
“all three keys are created in three different environments”
Listen at 18:01
Many people find seed-phrase management difficult.
“people do find seed phrase management difficult”
Listen at 19:30
BitKey’s system is designed as a replacement for seed phrases.
“we developed a system that uh basically is as a replacement for that”
Listen at 21:17
BitKey requires at least two people to approve code merges.
“our code review process is it requires at least two people to get any code merged at all”
Listen at 24:28
Three separate groups can sign BitKey production code.
“We have three different groups that can sign production code”
Listen at 25:37
SPAKE2 prevents Block from man-in-the-middle interception during recovery-contact exchange.
“Block is not able to sort of man in the middle”
Listen at 30:16
Recovering through a lost phone initiates a seven-day waiting period.
“what that will do is start a seven-day waiting period”
Listen at 31:57
BitKey inheritance claims have a six-month waiting period.
“it's a six-month waiting period”
Listen at 33:35
BitKey’s screen provides additional protection against address-replacement attacks.
“The screen does give you an extra level of protection.”
Listen at 34:45
Clipboard replacement attacks may still occur on Android under some configurations.
“Probably could still happen on Android in the right configurations.”
Listen at 35:50
Existing BitKey funds are safe without the screen-equipped device.
“your funds are not at risk. If you don't have the screen device, your funds are safe.”
Listen at 36:20
People should continue using Bitcoin self-custody after recent hacks.
“I hope people stick with self-custody”
Listen at 40:32
Clay is more optimistic about Bitcoin self-custody after recent events.
“I've never been actually more bullish on Bitcoin self-custody because of it.”
Listen at 40:43
BitKey recently launched an Auto DCA feature.
“we just recently launched Auto DCA”
Listen at 41:04
Cash App Auto DCA automatically transfers excess Bitcoin to self-custody.
“when I exceed that, here's how much I want to sort of like automatically move over to self custody”
Listen at 41:14
Cash App integration enables discounted fees for Auto DCA.
“they're able to discount the fees as well”
Listen at 41:43
Block aims to make Bitcoin everyday money.
“we want to make bitcoin everyday money”
Listen at 44:30
Block will transparently share its ongoing product development.
“We are relentless in our roadmap. We are transparent. We're going to share what we're building.”
Listen at 45:03
Statements are attributed to the speaker as said on the episode and reflect their view at the time, not PodLume's. They are not advice.