Content
@
0 reply
0 recast
0 reaction
nix
@nix
MPC-TSS seems fundamentally broken. The user's backup shard: - Is either in the hands of the provider, giving them custody (2/3). - Or requires the user to securely store an encryption key, essentially providing the same experience as a seed phrase. Every embedded wallet seems to use this approach. What am I missing?
2 replies
0 recast
2 reactions
Harry Noble
@harry
Check out the demo for Coinbase’s new smart wallet. You get the upside of an embedded experience (no apps to install, instant creation) and it’s all tied to your passkey, fully self sovereign and portable, no complex mpc setups to think through. keys.coinbase.com/developers
1 reply
0 recast
0 reaction
nix
@nix
This is very nice! I do think passkeys are the best way to do embedded wallets. Is the passkey is used to encrypt the actual ECDSA signer key hosted by Coinbase? How can I protect against Coinbase losing or censoring the actual key?
1 reply
0 recast
0 reaction
Harry Noble
@harry
The passkey is the actual key. Coinbase doesn’t hold anything. The passkey signature is validated by a contract directly onchain.
3 replies
0 recast
1 reaction
asadox.sol
@asadox
Does it scale well across multiple devices/OS?
1 reply
0 recast
0 reaction
Krish Chelikavada
@thecskc
It’s still a single point of failure since passkeys are dependent on a url, you’ll probably need to augment that with a recovery method
1 reply
0 recast
0 reaction
Jay Brower (jaymothy.eth)
@jayb
Which, to the original post, means that if the user loses their passkey they lose their wallet passkeys provide slightly better ux over this problem, but they don't solve it
1 reply
0 recast
0 reaction
