Support Mnemonic Code for easy key restoration about maskbook

[Jack-Works]

supported

[yisiliu]

Shall we consider this as in our next big release? Although current users need to create a new key pair.

[Tedko]

Highly recommend get this done b4 DWeb and other Pr events / summit. Otherwise on media side we have to spend nearly same manpower for noticing user

…

On Wed, Jul 10, 2019 at 01:51 Yisi Liu ***@***.***> wrote: Shall we consider this as in our next big release? Although current users need to create a new key pair. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#15?email_source=notifications&email_token=ABTAVTKSIKUTREH5CUY5UODP6WPIVA5CNFSM4HGR5OVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZSZC4Y#issuecomment-509972851>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABTAVTK7V6XY5A52GEXVTXTP6WPIVANCNFSM4HGR5OVA> .

[neruthes]

Recently it has been increasingly clear that keypair transfer is more important than keypair backup, and keystore backup is also more important than keypair backup. In essence, keypair backup is a partial backup and is therefore not enough to restore everything. For backup purposes, we still need whole-keystore backup; for transfer purposes, text is not the best medium of transfer, especially when at least one device has optical input capability. Alive backup is better than static backup, and almost everyone has at least 2 devices which may have Maskbook support soon if not now.

In conclusion, I would argue that this kind of backup is not what we really want.

[Tedko]

It’s more about standard, since naturally we are more close to the so called Web3 concept (and Web3 foundation, Eth community foundation). I don’t want to create another standard on that since the key transfer is already implemented by other company (such as Brave b4) even though their solution do involve a server. It is very urgent to support the memoric word if we want to get their support and using the community’s budget to educate the users. The DWeb is July 20 and Web3 summit is Aug 17. We’d better complete this feature by then.

…

On Wed, Jul 10, 2019 at 10:01 Neruthes (a.k.a. J.N.) < ***@***.***> wrote: Recently it has been increasingly clear that keypair transfer is more important than keypair backup, and keystore backup is also more important than keypair backup. In essence, keypair backup is a partial backup and is therefore not enough to restore everything. For backup purposes, we still need whole-keystore backup; for transfer purposes, text is not the best medium of transfer, especially when at least one device has optical input capability. Alive backup is better than static backup, and almost everyone has at least 2 devices which may have Maskbook support soon if not now. In conclusion, I would argue that this kind of backup is not what we really want. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#15?email_source=notifications&email_token=ABTAVTM2H4Q2Q4ULSAVHABTP6YIWTA5CNFSM4HGR5OVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZUDHKA#issuecomment-510145448>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABTAVTOHRCQ35UNXRHC4KWLP6YIWTANCNFSM4HGR5OVA> .

[Tedko]

Also since these repo are available for public, let’s discuss somewhere else and put conclusion here, then see if the community wanna join us or not.

…

On Wed, Jul 10, 2019 at 10:06 Suji Yan ***@***.***> wrote: It’s more about standard, since naturally we are more close to the so called Web3 concept (and Web3 foundation, Eth community foundation). I don’t want to create another standard on that since the key transfer is already implemented by other company (such as Brave b4) even though their solution do involve a server. It is very urgent to support the memoric word if we want to get their support and using the community’s budget to educate the users. The DWeb is July 20 and Web3 summit is Aug 17. We’d better complete this feature by then. On Wed, Jul 10, 2019 at 10:01 Neruthes (a.k.a. J.N.) < ***@***.***> wrote: > Recently it has been increasingly clear that keypair transfer is more > important than keypair backup, and keystore backup is also more important > than keypair backup. In essence, keypair backup is a partial backup and is > therefore not enough to restore everything. For backup purposes, we still > need whole-keystore backup; for transfer purposes, text is not the best > medium of transfer, especially when at least one device has optical input > capability. Alive backup is better than static backup, and almost everyone > has at least 2 devices which may have Maskbook support soon if not now. > > In conclusion, I would argue that this kind of backup is not what we > really want. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#15?email_source=notifications&email_token=ABTAVTM2H4Q2Q4ULSAVHABTP6YIWTA5CNFSM4HGR5OVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZUDHKA#issuecomment-510145448>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABTAVTOHRCQ35UNXRHC4KWLP6YIWTANCNFSM4HGR5OVA> > . >

[Jack-Works]

If you want to do this breaking change, you should make a vote to ask current users if they want to do this

[Tedko]

@Jack-Works will do. actually we don't even have a good way to let them vote now. will think later. for now let's finish 1. key tsf mechanism 2. Mnemonic Code

[neruthes]

Preview

[neruthes]

@Tedko Would you suggest to prioritize mnemonic words over keystore transfer?

[Tedko]

Still, Key transfer 1st. The others feature better be done* before Web3 summit.

[yisiliu]

@Jack-Works

[Tedko]

@Jack-Works updates?

[Jack-Works]

we have discussed this

can be done without breaking but need a lot of time

[Tedko]

@Jack-Works great. let me know updates. Happy 10/1