We don’t want our customers subject to these types of attacks, so we aren’t burdening them with seed phrases in the first place.
I didn't get what they are doing differently now. I understood they are offering multisig solutions. But don't they consist of seed phrases, too?
Bitkey is a multisignature wallet that uses three keys instead of one
Most (all?) hardware wallets today have customers write down the seed phrase and re-enter it as part of onboarding. This in an unusual experience for most people. It is time-consuming. And of course then customers have to understand and appreciate how sensitive this material is that they've just written down and devise a plan both to never lose it and never let anyone else see it even for just a few seconds (a quick picture away from losing all your money).
Imagine instead an onboarding experience that takes a minute and doesn't involve any of this?
reply
Casa also recommends seedless setup for their customers https://blog.keys.casa/seedless-security-model/
reply
With the huge ledger backlash going on right now....like I don't know maybe because you're doing this from the start its different but (and also its only one of 3 keys and not a split of 1 key)
Did you look at the Liana wallet? Anything inspiring from that design you think might be useful for what Spiral is trying to accomplish?
reply
"Wallet is made up of three parts - a mobile “App”, a specialized “Hardware” device, and our backend “Server” - with each controlling one of 3 keys" using a 2 of 3 multi-sig. You know some people do this with unchained capital so they're sort of making that model streamlined.
I don't really like it myself. I mean just take the marketing from Liana wallet: https://twitter.com/raw_avocado/status/1658099154571218949
Gives the user all the power to make all the decisions they want.
I don't know sometimes with these companies I'm reminded of Maralyn Manson. "Some of them wan to abuse you, some of them want to be abused" https://www.youtube.com/watch?v=nSG-6xc-T4U
reply
I suspected they just aren't exposing them as part of the UX. They can't prevent an encoding from existing, but they can prevent users from knowing it exists.
reply