,
8 tweets,
1 min read
Read on Twitter
0/ One of the biggest UX problems in crypto is private key mgmt
1/ In particular, this is hard to do in a trustless way while offering some sort of account recovery, and making it very easy to use the same identity across devices
2/ One approach is to figure out how to import your private keys into many deviecs
3/ Another is to store it in a central location (encrypted), and download and decrypt on demand
4/ Another still is multi party computation, which is similar to the last method, but which has much lower trust requirements
5/ However, there's another that I think is largely unexplored
Abstracting private keys on chain entirely by mapping them to an identity
With this approach, you don't need to import keys across devices at all
Abstracting private keys on chain entirely by mapping them to an identity
With this approach, you don't need to import keys across devices at all
6/ The other nice benefit of this approach is that it aligns nicely with the WebAuthN standard, which is quickly going to become what consumers expect
7/ In general, crypto has not explored the latter path enough. The notable exception is EOS
{fin}
{fin}
