Collaborative custody solves the self-sabotage problem
The speaker argued that seedless, collaborative custody models eliminate the high risk of user error inherent in traditional DIY seed-phrase management without violating Bitcoin's permissionless ethos.
The argument
Historically, self-custody required complex, error-prone manual setups like writing down and hiding seed phrases, which deterred mainstream adoption. By using multi-signature setups where a key partner (like Block) co-signs but cannot see transactions, users gain recovery and inheritance features safely.
The thesis, stress-tested
✓ What validates it
- —
▸ Risks discussed
- ▸Reliance on a third-party coordinator for recovery paths
- ▸Potential firmware vulnerabilities in hardware wallets
Hear it yourself
"And so, like, putting self custody users into the situation of, like, am I going to resist the attacker? I am gonna try to trick the attacker. Like, how am I going to navigate the situation? You know, and some of these solutions are like, put put your backup key in a bank lockbox because then you have to go there or whatever. But, like, all of these really put a lot of the onus on the on the self custody owner in a violent situation. And so I think to really solve the problem, what we need to do kind of as an industry is take on the assumptions of if an attacker has full knowledge of your wallet setup and the victim is fully compliant, can you still protect the Bitcoin? Mhmm."
05:10
AFFILIATE LINK · ZORTIX MAY EARN A COMMISSION · NEVER A RECOMMENDATION TO TRADE