Great looking stuff :)
Thanks! Here's hoping it can take off and help introduce people to web3.
Show HN: No more 12-word seed phrases
11–20 of 32 posts
Re: Show HN: No more 12-word seed phrases
#12Pretty cool idea, but does this solution actually give users ownership of their identity?
It absolutely does. All we store is an encrypted version of the user's master keychain (the 12-word seed phrase we're trying to eliminate). We can't access that keychain without the user's consent. The user is emailed a copy of this encrypted keychain and can take it with them to any service that supports bip39 seed phrases. Try getting Google to let you do that ;)
> All we store is an encrypted version of the user's master keychain
Is the seed created and encrypted on the client or the server?
Re: Show HN: No more 12-word seed phrases
#13I'm one of the founders of SimpleID. As a Web3 app developer, I have first hand experience hand holding users through the complicated on-boarding process. I built Graphite, a popular dApp, using traditional Web3 auth and I just recently cracked 10K users after 2 years... The status quo today expects users to navigate pop-ups, install extensions, and of course manage their 12-word key phrase! What I've learned is that…
It seems that your demo page (.../demo) is broken (it's 404ing with a NoSuchKey).
Anyway, I'm wondering if your solution helps users who forget their password? (Though I notice your initial comment says something about "get rid of passwords all together.)
Re: Show HN: No more 12-word seed phrases
#14Earlier quoted context omitted.
It absolutely does. All we store is an encrypted version of the user's master keychain (the 12-word seed phrase we're trying to eliminate). We can't access that keychain without the user's consent. The user is emailed a copy of this encrypted keychain and can take it with them to any service that supports bip39 seed phrases. Try getting Google to let you do that ;)
> All we store is an encrypted version of the user's master keychain Is the seed created and encrypted on the client or the server?
The seed is generated on the lambda, encrypted client side and stored in our database.
Re: Show HN: No more 12-word seed phrases
#15I'm one of the founders of SimpleID. As a Web3 app developer, I have first hand experience hand holding users through the complicated on-boarding process. I built Graphite, a popular dApp, using traditional Web3 auth and I just recently cracked 10K users after 2 years... The status quo today expects users to navigate pop-ups, install extensions, and of course manage their 12-word key phrase! What I've learned is that…
It seems that your demo page (.../demo) is broken (it's 404ing with a NoSuchKey). Anyway, I'm wondering if your solution helps users who forget their password? (Though I notice your initial comment says something about "get rid of passwords all together.)
Great catch! I pushed the demo up to netlify and it should work now
We are working on a solution where you never have to set or remember your password
Re: Show HN: No more 12-word seed phrases
#16Earlier quoted context omitted.
It absolutely does. All we store is an encrypted version of the user's master keychain (the 12-word seed phrase we're trying to eliminate). We can't access that keychain without the user's consent. The user is emailed a copy of this encrypted keychain and can take it with them to any service that supports bip39 seed phrases. Try getting Google to let you do that ;)
> All we store is an encrypted version of the user's master keychain Is the seed created and encrypted on the client or the server?
We chose this method because it requires trust of just one entity (the lambda end point we provide) rather than trust of each app that might interact with SimpleID's SDK. If the seed phrase is generated client-side within an app, that developer could hold onto that seed and use it maliciously.
Identities created through SimpleID can be used across multiple apps, so it's important to us that developers are only able to access data specific to their app (i.e. app-specific encryption keys).
Re: Show HN: No more 12-word seed phrases
#17Web 3.0 and its complex nature of on-boarding the non tech savvy ones. A tool like this is indeed needed.
I just remembered I saw this once on steemhunt too, a Steem based product curation platform.
Re: Show HN: No more 12-word seed phrases
#18Web 3.0 and its complex nature of on-boarding the non tech savvy ones. A tool like this is indeed needed. I just remembered I saw this once on steemhunt too, a Steem based product curation platform.
Steem is such a cool project. That's definitely high up on the priority list for us to support!
Re: Show HN: No more 12-word seed phrases
#19Nice site and solution. I clicked 'run' on the Examples page and at first I thought it was broken but then after about 20s it produced output--might want to drop some initial output that tells users to wait or something.
Re: Show HN: No more 12-word seed phrases
#20Nice site and solution. I clicked 'run' on the Examples page and at first I thought it was broken but then after about 20s it produced output--might want to drop some initial output that tells users to wait or something.
Thanks! And totally agree. We talked about this leading up to this launch and went back and forth with it. The runkit example you see on the site is using the actual production Node SDK because we want developers to literally be able to copy and paste the code. So we also want to make sure the console output is appropriate for all environments. We'll find a balance though.