Lixin Liu on the Keystone Hardware Wallet (S8 E12 Full Article)
The audio keeps playing while you browse the site.
Read the transcript7,107 words, every line links to the minute it was said
Ask this episode
Lixin Liu was on the show just five episodes earlier, talking about the Cobo Vault as its head of hardware. Then things moved fast. When he came back, he was the CEO of a new company, Keystone, with the same team and the same device in a new shell. I had to know what happened.
We talked about why they left Cobo, what's new in the hardware, why Cobo Vault owners get a discount instead of a firmware update, the next generation, supply chain defenses and how to onboard safely. The original show notes have the short version.
Why They Left Cobo
"The story goes back to late 2017," Lixin said. Cobo started with a custodial product, Cobo Wallet, where "they have your private key" and you could earn "5% or 6% annual gain." Then the founders "incubated me as the head of hardware to start the hardware wallet called Cobo Vault." One founder, Discus Fish, is "also one of the co-founders of F2Pool."
The first generation didn't take off. The second one, launched in mid-2020 at "around 150 US dollars," targeted the West and "was very successful and grows very well." But the hoped-for "synergy they expected between Cobo Wallet and Cobo Vault didn't happen."
So Cobo chose to "keep the hardware wallet into minimum maintenance and fully focus on the centralized service." Lixin didn't hold it against them. "I can fully understand that from a business perspective." But no new devices meant no future for the product. "That is unacceptable for me and also for the Cobo Vault team. And that's the main reason why we left Cobo and started a new company called Keystone."
They also turned down a different path. "We didn't want to get into centralized services. Even they gave us very attracting offers, but money is not just what we want."
Same Shape, Better Device
"Personally, I bought out all the intellectual properties of Cobo Vault," Lixin said. That let Keystone keep the design and code, then fix what users had asked for.
The microSD slot moved. On the Cobo Vault it hid behind the battery, because it was meant for rare firmware updates. Then users started moving PSBTs on it, since "the large PSBT transactions cannot be transited with the QR code because that will cause too many QR codes." Now the slot is on the outside.
The battery circuit changed after "maybe 1% of the users are complaining about the battery." The camera got faster at reading QR codes. On the software side, Keystone moved to "BC-UR 2.0," the QR standard that "will be long-term maintained by Blockchain Commons and other Bitcoin developers." The hope was to make "the whole community, especially the QR code standard, more standardized."
Why There's No Migration Firmware
The ideal plan was a firmware that would turn a Cobo Vault into a Keystone. It couldn't happen without Cobo. "Cobo Vault can only recognize a firmware which is signed by a specific key," and "we don't have access to that key. Only Cobo team has that access."
The migration itself would have been small. It "only changes the public key that was embedded in the system." Without Cobo's signature, though, it couldn't be done. So Keystone offered something else: "the 50% discount for the old Cobo Vault users." Old devices still work, since "the code is open sourced" under a license that allows commercial use.
Toward a More Open Next Generation
Lixin knows where the criticism lands. "Right now we have open source secure element firmware, but the community is still criticizing us that our Android layer is closed source."
He had two options in mind. One is "the direction of Specter DIY," with fully open firmware. The other is "GrapheneOS, which is an operating system which is fully open source," so they could keep their existing Java code. The target was "the end of 2022 or early 2023." He also mentioned exploring "a Bitcoin-only device" for the next generation.
I asked about a 100% open source device. "It's definitely impossible to make a 100% open source hardware because you have to purchase some kind of ICs from other companies." Small chips for the screen and camera carry their own code, and nobody in the industry can open all of it. That would take scale: if wallets sold "100 million devices every year," vendors could make their own chips.
Hardware simply takes time. "Even for us, it takes us at least six months to develop a new hardware," and fully open source "usually takes one year or even more."
A Signer, Not a Silo
Lixin's design philosophy came through clearly. "There's no perfection in security, especially if we put user experience into consideration." He sees every hardware wallet as "legit," each "trying to find a balance between security and the user experience."
The reason is speed. Bitcoin "is developing very fast," with Taproot, Lightning and "coin mixing, like Wasabi Wallet." No hardware team can build all of that alone, so he sees the hardware wallet's role as narrow on purpose. "The role of the hardware wallet is you are just a signer." That means being "as compatible as possible with other software wallets," for coin mixing, or for merchants "using BTCPay Server."
Selling Worldwide
Growing sales gave Keystone "more negotiation power with the logistics vendors" and room to cut shipping costs and open new countries like the UAE. Localization matters too. "Not every Bitcoiner can speak English." A strong reseller in Russia with localized videos and support helped sales there, and Spanish and Russian were planned for the device.
He also liked the idea of hardware wallets in physical stores, because "you can buy the hardware wallet with cash, rather than credit card or leaving your shipping address to the vendor."
Three Layers Against Supply Chain Attacks
Keystone kept Cobo's defenses and listed them plainly. There's an "anti-tampering sticker." There's web authentication, where each device's key pair is checked against "the Amazon Cloud HSM" to "make sure that your device, your Keystone device, is running the official Keystone firmware." And there's the "self-destruct mechanism": if someone opens the device in transit, "the device will destroy the firmware."
Keystone also doesn't allow third-party firmware, to close off a social engineering route where a user is tricked "into installing the hacker's firmware."
Onboarding, Step by Step
For new users, Lixin suggested "using Keystone with BlueWallet" for single signature. Then Shamir, "just like Trezor, the same standard, which is SLIP-39." Then multisig, a full node and privacy tools like Wasabi.
He stressed compatibility for edge cases. If Keystone ever disappeared, which he called "almost impossible to happen," your Shamir shares "should be recovered on other devices, which can be Trezor."
His best advice was about simplicity. He had seen someone use "so many layers of encryption on their recovery phrase. And then they forgot how they encrypted their recovery phrase." So "don't make your solution over complicated," and practice. He liked Casa's regular "health check" idea, because it checks "that you are still familiar with your multi-signature."
That wasn't a hypothetical. It happened to a friend of his, who couldn't recover the phrase and "lost everything."
He was clearly all in. "Last time I remember, we had the conversation at like 4 p.m. my time. Right now, I'm having it at 8 p.m."
What Makes This Episode Worth Listening To
You rarely hear a founder explain a spin-off this openly, a few weeks after it happened. Lixin covers what changed, what couldn't, and where Keystone wanted to go. His closing advice on simple, practiced setups is worth hearing whatever wallet you use.
You can read the full transcript, the original show notes, or visit Lixin Liu's guest page. For the earlier conversation, see his Cobo Vault episode.
Listen to Lixin Liu on Spotify, Apple Podcasts, and More
Time stamps:
- 00:04:11– How Cobo started
- 00:06:55– The second-generation Cobo Vault
- 00:07:48– Minimum maintenance
- 00:08:57– Leaving Cobo to start Keystone
- 00:10:28– Buying the IP
- 00:11:20– The microSD slot moves outside
- 00:12:49– Battery and camera fixes
- 00:13:41– BC-UR 2.0
- 00:15:41– Open source Cobo Vault code
- 00:16:49– No migration firmware
- 00:17:45– The 50% discount
- 00:23:21– A Bitcoin-only device
- 00:24:18– Opening the Android layer
- 00:25:05– GrapheneOS or Specter DIY
- 00:27:36– Security vs user experience
- 00:29:21– Bitcoin moves fast
- 00:30:09– Just a signer
- 00:31:16– Shipping and new countries
- 00:33:09– Localization
- 00:35:56– Buying in stores with cash
- 00:36:51– Web authentication
- 00:38:20– Self-destruct
- 00:39:51– No third-party firmware
- 00:41:10– Why 100% open hardware is impossible
- 00:44:42– Hardware takes time
- 00:45:45– Onboarding with BlueWallet
- 00:48:30– Don't overcomplicate
- 00:49:19– Practice and health checks
- 00:51:06– Compatible backups
- 00:52:50– Working extra hours
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
dedf27348afc875d9c0203cf5b1043ad54fc417e47b45fb7fddc4b4186d4a7bb- Proof
- 2021-06-24_btctkvr_s8_e12_lixin_liu_keystone_final.mp3.ots · all episode hashes (proof)
- Status
- Anchored in Bitcoin block 974,312
- Timestamped
- After release. The episode came out on 24 Jun 2021, 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 2021-06-24_btctkvr_s8_e12_lixin_liu_keystone_final.mp3(on a Mac:shasum -a 256 2021-06-24_btctkvr_s8_e12_lixin_liu_keystone_final.mp3). The result must match the SHA-256 above. - Install the OpenTimestamps client (
pip install opentimestamps-client) and runots verify 2021-06-24_btctkvr_s8_e12_lixin_liu_keystone_final.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 2021-06-24_btctkvr_s8_e12_lixin_liu_keystone_final.mp3.otsshows the block height to look up in any block explorer.
Related
S8 E12: Lixin Liu on the KeyStone Hardware Wallet
It was only 5 episodes ago that Lixin Liu had joined the Bitcoin Takeover Podcast to talk about the Cobo Vault. But…
Cobo Launches 2nd Gen Vault Hardware Wallet (Rebranded KeyStone, 2021)
The second generation of Cobo Vault hardware wallets comes with interesting features & lower price.
S4 E9: Lixin Liu on the Cobo Vault & Cobo Tablet (Rebranded KeyStone, 2021)
Cobo Vault creator Lixin Liu talks about building a hardware wallet for the Chinese miners and adapting it for Western markets.
Comments
Comments run on my own server. No trackers, no tracking cookies.