Cosmos-sdk: Add endpoint to create a seed

Created on 12 Dec 2017  ·  9Comments  ·  Source: cosmos/cosmos-sdk

I as a user
Want to create an account only after having written down a seed, not write down the seed for a written down account
So that I don't have accounts created I have no seed for.

AC

  • [ ] cosmos-sdk provides an endpoint for comos-ui that generates seeds
  • [x] cosmos-sdk provides an endpoint to persist an account based on a seed
proposal

All 9 comments

Is this still an issue ? Doesnt the gneerate key endpoint return a seed ?

we have to use a “trunk” account and dummy password to generate a seed. no endpoint for seeds without accounts (name + password).

Oh wonderful. You're asking for a way to generate a seed without persisting a password encrypted private key on disk ? I think that's essential. We need to make changes in go-crypto to support it ... https://github.com/tendermint/go-crypto/pull/64#discussion_r161557993

@ebuchman status update?

What happens once the user gets the seed. They write it down and re-enter? Do they have to create a password too ?

Currently it displays the seed together with inputs to enter account name and password. Then the user enters the name and password so the private key persists on disc.
In the future we can have a two-step process where the user has to enter the seed again (or parts of it) like known from other wallets.
The issue currently is, that you are only able to generate a seed while providing name and password and this is persisted. We currently generate a "trunk" account with a default password to generate the seed. But everybody could just read the last generated seed from disk with the default password. We can delete the "trunk" account after successful sign in, but we can not be 100% this process completes all the way.

Right I understand. Thanks.

In the future we can have a two-step process where the user has to enter the seed again

i like this. this will help with people putting funds into an account without actually having the means to get back in.

Done in #544

Was this page helpful?
0 / 5 - 0 ratings