514 lines
129 KiB
HTML
514 lines
129 KiB
HTML
<html><body><style>
|
|
* {
|
|
font-family:sans-serif;
|
|
}
|
|
body {
|
|
text-align:center;
|
|
padding:1em;
|
|
}
|
|
.messages {
|
|
width:100%;
|
|
max-width:700px;
|
|
text-align:left;
|
|
display:inline-block;
|
|
}
|
|
.messages img {
|
|
background-color:rgb(248,244,240);
|
|
width:36px;
|
|
height:36px;
|
|
border-radius:0.2em;
|
|
display:inline-block;
|
|
vertical-align:top;
|
|
margin-right:0.65em;
|
|
}
|
|
.messages .time {
|
|
display:inline-block;
|
|
color:rgb(200,200,200);
|
|
margin-left:0.5em;
|
|
}
|
|
.messages .username {
|
|
display:inline-block;
|
|
font-weight:600;
|
|
line-height:1;
|
|
}
|
|
.messages .message {
|
|
display:inline-block;
|
|
vertical-align:top;
|
|
line-height:1;
|
|
width:calc(100% - 3em);
|
|
}
|
|
.messages .message .msg {
|
|
line-height:1.5;
|
|
}
|
|
</style><div class="messages"><div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-05 14:19</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-05 14:19</div><div class="msg">@andreaf set the channel purpose: <a href="https://github.com/status-im/ideas/pull/142">https://github.com/status-im/ideas/pull/142</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-04-05 14:22</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-05 14:22</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-04-05 14:22</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-04-05 14:22</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-04-05 14:22</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-05 14:22</div><div class="msg">@andreaf set the channel topic: <a href="https://github.com/status-im/ideas/pull/142">https://github.com/status-im/ideas/pull/142</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-04-05 14:28</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-05 14:36</div><div class="msg">@chad already helped me to improve this ideas, I tried to simplify it a lot, and I hope the current version is better.
|
|
The basic idea is to allow users to import accounts created with MyCrypto, MetaMask, Toshi, Cipher Browser, and other mnemonic wallets. This, in my opinion, should help the "Beta is launched successfully " objective, but I would like to have more ideas and help from you guys</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-04-05 14:38</div><div class="msg">yes it sounds really great to me</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-04-05 14:38</div><div class="msg">and we can hopefully replace those 12 words with something more handy some day (just dreaming)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-05 14:39</div><div class="msg">:slightly_smiling_face: those words are actually part of the BIP39 that almost all wallets support, but maybe one day we can have something better :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-04-05 14:40</div><div class="msg">definitely agree that the access flow to wallets should be unique - easier for me as user to learn it once then trying to adap to different ways</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-05 14:54</div><div class="msg">This is also falls in line with #design-team OKRs for ?Good wallet experience? as something like ?wallet extendability?.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-05 15:16</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-05 15:32</div><div class="msg">I have question about UX: if we use the password only to lock the app, users can recover the account with just the 12 words, exactly like with accounts created in MetaMask, Toshi, MyCrypto, etc. If they then go to MyCrypto, the form asks for an optional password. Do you think they can understand that they don't need to put the password that they use to lock the account? If they use that password they will recover a different wallet in MyCrypto. This is not a problem with Status, but a general "problem" for new people in blockchain.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-05 15:33</div><div class="msg">MyCrypto is the only exception. If you want to recover the account in other wallet, they don't ask for a password so users will only use the 12 words.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-05 15:43</div><div class="msg">when you say ?that password they will recover a different wallet in MyCrypto? do you mean a password they created somewhere else such as MetaMask? And will recover a MetaMask wallet in MyCrypto? If so, yeah, that's confusing.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-05 15:44</div><div class="msg">I think they won't understand. Even me could thought I need a password</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-05 15:44</div><div class="msg">We need to create a f.a.q for this</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-05 15:46</div><div class="msg"><a href="https://myetherwallet.github.io/knowledge-base/migration/">https://myetherwallet.github.io/knowledge-base/migration/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-05 15:51</div><div class="msg">yeah this is an example:
|
|
* you install metamask
|
|
* it asks for a password
|
|
* you get a 12 mnemonic words
|
|
* you go to MyCrypto
|
|
* access your wallet with "mnemonic phrase"
|
|
* put your mnemonic phrase and submit the form
|
|
|
|
At this point, the first address you see in the list should be the same you have in metamask.
|
|
|
|
If you instead fill the password field with the password you used in metamask, you generate a different wallet.
|
|
|
|
This is like this in MetaMask, Toshi, Cipher Browser etc. Even if you create a mnemonic wallet from the new interface in the beta of MyCrypto.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-05 15:52</div><div class="msg">So they use the password only to lock the account on the phone, like the phone pin.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-05 16:01</div><div class="msg">if you created an account with the current Status app, you can't import it in other wallets.
|
|
|
|
with idea #094-compatibility we fix the compatibility following the standards, so a user can import the account in MyCrypto/MEW using the 12 mnemonic words and the password.
|
|
|
|
with idea #142-recovery I would like to remove the password from the creation of the wallet and leave it only to lock the phone. Doing this users will be able to:
|
|
|
|
* import the Status account in MyCrypto/MEW without password.
|
|
* import the Status account in other mnemonic wallets (MetaMask, Toshi, etc), that ask only for the 12 mnemonic words to generate the private key.
|
|
* Import in Status an account created in MetaMask etc</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-05 16:07</div><div class="msg">please ask any question, I know that the generation of private keys can be confusing :mindblown:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-05 16:07</div><div class="msg">I'll be afk ~ 2h</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-05 16:27</div><div class="msg">Sorry, had to step out for 30 minutes. The model is confusing in that you learn that with whatever wallet you setup first and create mnemonic for is ?de facto federated? when you go to other wallets. I say de facto because as a user how many of these 12 word mnemonics are you likely to use if one can give you access to multiple wallets ? why use others? Even if you would like to see MyCrypto wallet first in your example and use password + mnemonic how likely are you to remember all these combinations. Please let me know if I?m not thinking about ?mnemonic phrases? correctly.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-04-05 16:31</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-05 17:12</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-06 07:14</div><div class="msg">yeah in general I think a simple user can use just one mnemonic phrase to use the same account everywhere. for sure other users want to have multiple account, but in general all the wallets are compatible so I think ours should be too</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-06 07:14</div><div class="msg">why do you think the model is confusing?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-04-06 08:23</div><div class="msg">Regardless of accessing through other wallets; it might be confusing to have to use a password for recovery. We are not communicating this clearly enough and people might feel safe with their seedphrase alone. If we keep this we need to validate in UX testing whether people know what to do to recover. This wasn't covered in the last tests. @patrick771 does this fit in the upcoming test?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-06 08:28</div><div class="msg">my proposal would be to follow all the others wallets, and use the password only to lock the account in the app, and only mnemonic words to recover. we should still communicate this clearly. what do you think @hester?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-06 08:37</div><div class="msg">Yes, we should test both recovery and, possibly, some of these cases such as importing an account made in MetaMark into Status using just a mneumonic to sign in. And also if people understand why we might ask you lock an account with a password to begin with - i.e. eventually for recovery.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-06 08:48</div><div class="msg">For people who are new to Ethereum, it's a new model of account creation, authentication and recovery. In the long term it could be potentially less confusing and more efficient than the current state of u-name + pword because you potentially have to remember one thing (mneumonic) when transferring a wallet or logging in (password). It?s just something we need to verify with UXR but I agree that we should be compatible with other wallets .</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-06 08:51</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-06 09:08</div><div class="msg">_o/</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-06 09:19</div><div class="msg">yeah you are right, it's difficult for new people, and in general the private keys idea is something that a normal user cannot know about</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-06 09:19</div><div class="msg">but it's in general the blockchain world more than Status</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-04-06 10:03</div><div class="msg">This seems like the best solution. At the same time, I'm sure there is a reason we use both password and seedphrase (mnemonic words) both. Would love to understand this and what the consequence would be of using only the seed phrase. Feels like this is a security/UX tradeoff. If we understand the risks we can consider other mitigations.
|
|
|
|
If anyone can explain, @jarradhope?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-06 10:07</div><div class="msg">yes you are right @hester, more feedback on this would be very appreciated. My research on other wallet ended up noticing that they all use the password to lock the account or keystore file, but the private key is generated only with the 12 mnemonic words (BIP39 allows empty passphrase). The new MyCrypto beta added the generation of mnemonic wallets but without password. I also asked them in their discord chat and they replied:
|
|
|
|
> The reasoning behind not including it was because it wouldn't really add significant security benefit, but does discourage people from using it.
|
|
|
|
thank you for helping, the more :eyes: we have on this, the better decisions we can take!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-06 10:52</div><div class="msg">just to give more context to @jarradhope, this idea is related to idea 94, which is already implemented in a PR. <a href="https://github.com/status-im/ideas/pull/139/files">https://github.com/status-im/ideas/pull/139/files</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-06 10:53</div><div class="msg"><a href="https://github.com/status-im/status-go/pull/783">https://github.com/status-im/status-go/pull/783</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-06 12:47</div><div class="msg">If you don't want to use a password, store the HD data structure in iOS and Android secure enclave please and sign from secure enclave, if you do this properly you will get fingerprint login</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-06 12:49</div><div class="msg">Please do not store the private key unencrypted and please do not store it in an encrypted state in which the user cannot recover the account</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-06 12:50</div><div class="msg">I'm all for using the secure enclave, that way we get _more_ security and a _better_ UX</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-06 12:51</div><div class="msg">Also note that you will have issues with sending whisper messages in this case, so you will need a *secure* way to expose the whisper private key leaf in memory</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-06 12:53</div><div class="msg">If you don't fully understand the HD key structure, signing of transactions, and how to secure private keys - sorry but you shouldn't be allowed to give input on this or make suggestions as you are being reckless with our peoples safety and security - their assets, their money and the reputation of Status as a whole, One mess up here in production and NO ONE will use the application and trust will near impossible to rebuild. No matter how convenient it is.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-06 12:56</div><div class="msg">If you want to automatically encrypt the keypair and leave on disk (wooo no passwords!!), then make sure that the user has recorded the key phrase down so in the event the application database is corrupted the user can still recover, AND IF there is ever any value detected on that users account, force them to encrypt their db as a malicious attack will expose the encryption key in the app db.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-06 12:57</div><div class="msg">thank you @jarradhope, I understand what you say. my idea was only related to the part in which we use BIP39 to generate the seed to be compatible with other wallet but not in the way we store the private key. Do you think they can be two different things or they can't be separated. Sorry if I'm missing something here but I would like to understand more.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-06 12:58</div><div class="msg">Copying from other apps is also a bad practice, please make sure you understand it before blindly copying bad practices set by other wallets, its better to learn from first principles and understand what your doing.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-06 12:58</div><div class="msg">seed generation is seperate, we've already talked about making it more compatible</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-06 13:08</div><div class="msg">yes in the other idea we make it compatible using the standard constants. But in this idea I don't want to remove the password when we encrypt the private key, but only in the BIP39 generation of the seed.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-06 13:09</div><div class="msg">that's fine</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-06 13:09</div><div class="msg">and what do we do about existing users?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-06 13:10</div><div class="msg">do you plan to add checksum into address? public key compression ?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-06 13:14</div><div class="msg">we said that since we are in alpha we could be able to communicate this to people and use only "new accounts" since we need to do it for other breaking changes</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-04-06 13:19</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-04-06 13:22</div><div class="msg">@adamb as fyi since this is probably also relevant for the current security audit (and probably ongoing security process)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-06 13:27</div><div class="msg">@naghdy @andreaf @adamb @hester @patrick771 @andrey @roman could you please create a HD Wallet 'Study session' / call and learn the HD structure, and how transaction signing works, it would be immensley beneficial if all the Go developers understood it in depth, as well as the Clojure devs, along with UXR so we can come up with informed solutions.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/b11645e09683360c0849df16c77e9980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">themue</div><div class="time">2018-04-06 13:29</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-04-06 13:30</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-04-06 13:41</div><div class="msg">Excellent idea and totally agree we need this. I'll set it up!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-04-06 13:51</div><div class="msg">@naghdy @jarradhope: who within Status can I ask as a teacher?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-07 02:42</div><div class="msg">it's probably me</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-04-09 00:09</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-04-09 14:47</div><div class="msg">Session is planned for April 30th.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-04-09 14:52</div><div class="msg">From the discussion above I understand that we'd need to go over the following topics:
|
|
|
|
*Why we all need to understand HD key structure*
|
|
*HD (Hierarchical Deterministic) wallet structure*
|
|
Private key generation
|
|
Public key generation
|
|
*Seed generation (using BIP39?) (BIP = Bitcoin Improvement Proposals)*
|
|
*Signing of transactions*
|
|
*Securing private keys*
|
|
*Secure enclave (on iOS, on Android)*
|
|
*Encrypting the key pair*
|
|
*Key compression*
|
|
*Exposing/accessing Whisper private key*
|
|
*Recovering the key pair*
|
|
*Risks and mitigation*
|
|
Database corruption
|
|
Noting down key phrase
|
|
Encrypting database</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-04-09 14:55</div><div class="msg">This seems like a lot:) @jarradhope please let me know if there's anything I can do to help prepare.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-04-10 09:08</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-04-10 09:37</div><div class="msg">Hi @hester. I don't seem to be invited to the session on the 30th. Can you please make sure the Go team is invited?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-04-10 09:52</div><div class="msg">added you, I'll check again!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-11 09:42</div><div class="msg">@hester @patrick771 did you have the opportunity to think about possible changes in the UX? I implemented the code and I'm opening a PR so that we can test it. the best thing would be to create a new branch that has all the changes from both #094-compatibility and #142-recovery but I'm open to discuss about it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-11 09:54</div><div class="msg">Hey @andreaf I?m still definitely interested in increasing security and compatibility side and would like to explore some UX options but paused given some of the concerns raised by @jarradhope and others about ensuring that we're all in agreement and understand HD wallet structure and details of signing transactions. Could you maybe walk us through what you're thinking for the new PR in the mean time?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-11 10:14</div><div class="msg">I have a question here:
|
|
|
|
Use case: I have existing Status account but I want to use a wallet that I have created in Metamask. It is not possible to recover a wallet in the existing Status account, is it?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-11 10:15</div><div class="msg">yes you are right @patrick771. In the new PR, the changes are only removing the password in the `BIP39` seed generation but keeping it to encrypt the keys. It requires the changes made in #094-compatibility to be fully testable. So this means that to recover an account you only need the 12 mnemonic words, and the password, since is only used to encrypt the keys in the local storage, can be change every time an account is recovered.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-11 10:16</div><div class="msg">it's not possible in the current account, but it will be possible if we want to continue with ideas #094-compatibility and #142-recovery</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-11 10:19</div><div class="msg">:+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-11 11:55</div><div class="msg">btw I also agree on pausing this until we have the study session, but I'm open to questions and discussions about it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-11 12:04</div><div class="msg">So question is, which I think you raised in the other thread, is what do we do about the password in the case that a user wants to recover another wallet when in Status?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-11 12:29</div><div class="msg">there are 2 scenarios I think:
|
|
|
|
1 - Users created an account in another wallet that doesn't use the password to create the seed, but only to encrypt the keys (MetaMask, MyCrypto, Jaxx, MEW etc). They set the 12 mnemonic words in status and we recover the seed, and they set the password and we use it to encrypt the keys. Pretty much like now but the wording below the password field should change (now it says you need the same password to recover the account).
|
|
|
|
2 - Users created an account in another wallet that generated a seed with mnemonic words and password (I don't know any other wallet like this so far). We could have an advanced options to specify the password to recover the account but it seems more difficult and less usable (but I don't want to take decisions in UX of course).
|
|
|
|
This paragraph from Mastering Ethereum can also be an interesting read:
|
|
<a href="https://github.com/ethereumbook/ethereumbook/blob/develop/wallets.asciidoc#optional-passphrase-in-bip-39">https://github.com/ethereumbook/ethereumbook/blob/develop/wallets.asciidoc#optional-passphrase-in-bip-39</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-11 16:06</div><div class="msg">Thanks for the context and links to the material. Would it be possible to create a test branch in the mean time? Is it possible to roll back these changes if you do merge work from #094-compatibility and #142-recovery? I basically wondering if we could prototype your changes?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-11 16:20</div><div class="msg">yes I'm working on having builds for iOS and android to be able to test them but I stuck with a couple of problems in jenkins. I hope to fix it today</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-04-12 09:02</div><div class="msg">@andreaf do we have objections to continue?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-12 09:03</div><div class="msg">I don't think so but we decided to wait for the study sessions on the 30th to be all on the same page</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-04-12 09:03</div><div class="msg">ok</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-12 16:20</div><div class="msg">@patrick771 this is a test build based on my branch:
|
|
|
|
Branch: status-im:experiment/wallet-compatibility
|
|
Android: <a href="https://i.diawi.com/11a5JC">https://i.diawi.com/11a5JC</a>
|
|
iOS: <a href="https://i.diawi.com/HC55DR">https://i.diawi.com/HC55DR</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-12 20:56</div><div class="msg">Thanks for sending over. So I tried to recover my MetaMask wallet in Status using my MM mnuemonic but no luck with recovery. Or at least I was able to log in but my funds were not restored. Let me know if there are other specific steps I need to take to test.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-12 21:28</div><div class="msg">hi @patrick771, in meta mask, are you using ropsten testnet? by default metamask is in mainnet and status in ropsten testnet. if you switch to ropsten, tell me your address and I'll send you some ETH from the faucet (or for privacy you can reinstall it and create a different account and tell me that one)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-12 21:32</div><div class="msg">sorry I didn't specify that before</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-12 21:48</div><div class="msg">Thanks for the ETH! So, this is my restored MM wallet at this point?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-12 21:48</div><div class="msg">in Status</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-12 21:51</div><div class="msg">yeah so it's basically the same address, so you are using the same private key. if you see the same funds and the same address, it's working</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-12 22:34</div><div class="msg">Yup, works!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-17 10:13</div><div class="msg">@chad@patrick771, talking with @andreaf and wdyt about pushing for this idea becoming in progress? that way presentation and knowledge sharing etc could be part of the initial iteration scope</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-17 10:14</div><div class="msg">I'm also thinking about giving a presentation on Mnemonic Wallet before the HD Wallet session, so that we can share the research of Mnemonic Wallets in general, and the way we use it to create/generate accounts, and log in users</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-04-17 10:17</div><div class="msg">:+1:
|
|
First iteration as research/exploration is a great approach for swarms like this</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-17 11:23</div><div class="msg">All for it as well</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2018-04-20 09:19</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-04-20 12:51</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285383092772_62dfbe80e57ef8940bb7_72.jpg" /><div class="message"><div class="username">sergii</div><div class="time">2018-04-20 12:57</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-20 13:57</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-23 08:46</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-23 09:50</div><div class="msg">hi everyone, I added a slide about #142-recovery and #094-compatibility in the Town Hall presentation. please check if you want to change something, and add your name if it wasn't already in the idea on github</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-23 11:42</div><div class="msg">Hi, do we have a project board for the idea in order to track what is ready for testing?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-23 11:50</div><div class="msg">yes in github, let me check</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-23 11:51</div><div class="msg"><a href="https://github.com/status-im/status-go/projects/14">https://github.com/status-im/status-go/projects/14</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-23 11:51</div><div class="msg">I'm going to update it after the town hall</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-04-23 11:57</div><div class="msg">@chad set the channel topic: Idea: <a href="https://github.com/status-im/ideas/pull/142">https://github.com/status-im/ideas/pull/142</a>
|
|
Board: <a href="https://github.com/status-im/status-go/projects/14">https://github.com/status-im/status-go/projects/14</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-04-23 12:59</div><div class="msg">@chad if we want to use real snt and eth in mainnet we need to keep in mind that after this idea will be implemented it'll be impossible to restore accounts</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-23 13:21</div><div class="msg">exactly, that's a good point. but also that if we are receiving eth in accounts created in MIST/MetaMask/MyCrypto etc, we can't use them in Status</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-23 13:22</div><div class="msg">with an old build though you can still open the old account and send tokens to the new address</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-23 13:23</div><div class="msg"><!channel> what do you think about having a call later or tomorrow to discuss about this things and understand what we need to do?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-04-23 13:24</div><div class="msg">sure, i can do it in next 1,5 hours or tomorrow</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-23 13:24</div><div class="msg">tomorrow is great for me</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-23 13:45</div><div class="msg">@chad would you be able to do it tomorrow? maybe around 2pm CET?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-04-23 13:46</div><div class="msg">I have some things, but you can ?find a time? in the google calendar invite to see free spots</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-04-23 14:06</div><div class="msg">Ah I have a conflict then. Didn?t the find a time feature work?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-23 14:28</div><div class="msg">no tomorrow was empty for everyone, is there another slot after 2pm for you?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-23 14:38</div><div class="msg">I created a 30 min meeting for tomorrow, if you are interested and you didn't receive the invite, please ping me</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-24 12:58</div><div class="msg">we can start in 3 minutes :slightly_smiling_face: <a href="https://meet.google.com/gse-ytwi-ibn">https://meet.google.com/gse-ytwi-ibn</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-04-24 13:20</div><div class="msg">In this case only 1 wallet can be used at a time. Default wallet can be selected in Settings</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-24 13:22</div><div class="msg">So even for the first iteration of this swarm, we would still need an `import wallet` UI for a single account?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-04-24 13:24</div><div class="msg">or wallet</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-04-24 13:29</div><div class="msg">```Suppose you used the Import Account capability to import an account. Now, when you click Switch Accounts, you see the word "Loose" with a bright red oval background superimposed on your account avatar.
|
|
|
|
The "Loose" label means that the account is not backed up by your seed phrase. This happened because you imported the account after creating your seed phrase.
|
|
|
|
As a precaution, keep the information you were using to access this "Loose" account backed up outside of MetaMask. (Similar to how you keep your seed phrase backed up somewhere offline.) This way, if something goes wrong, you can recover the account.```</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-04-24 13:32</div><div class="msg">i like the idea of validating the passphrase</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-04-24 13:33</div><div class="msg">what about having autocomplete when you are typing the mnemonic?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-24 13:35</div><div class="msg">@chad that's actually a good idea. especially because the 2048 words valid possible words have been chosen to be uniq in the first 4 letters. so it means that if the list contans `beauty`, it's can't contains `beautiful`, so after the user types `beau` we are 100% sure he's typing `beauty`. but I think we need a lot of UX research on this. and I like it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-24 13:58</div><div class="msg">@chad 1 question about swarm process for this idea. I'm actually the only contributor as go developer. do we still need to have someone else helping in this?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-04-24 13:59</div><div class="msg"><a href="https://github.com/status-im/ideas/blob/master/MANUAL.md#what-does-it-mean-for-a-swarm-to-be-well-defined">https://github.com/status-im/ideas/blob/master/MANUAL.md#what-does-it-mean-for-a-swarm-to-be-well-defined</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-24 14:00</div><div class="msg">yeah that's why I asked because I see it talks about `three contributors`</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-04-24 14:00</div><div class="msg">Needs at least 3 members, so you have that. Sounds like you might need a clojure dev though?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-24 14:01</div><div class="msg">we already have @andrey, and maybe @jeluard is interested too?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-04-24 14:03</div><div class="msg">So you should be good to go now. You can always add people later if you need to. Sounds like the first iteration doesn?t require clojure so giddyup!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-24 14:03</div><div class="msg">@adan @nastya I'm preparing a new build with all the changes from #142-recovery and #094-compatibility to that we can test it. After that I'm going to update the documentation and the steps to test</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-04-24 14:06</div><div class="msg">@andreaf I would but don't have time for now.. If you really need 3 you can count @chad as mixpanel dev? :rick:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-24 16:22</div><div class="msg">I'm still updating the idea description, but for testing I think we don't need a full list now, we can maybe just pick one like metamask or MyCrypto</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-04-24 18:09</div><div class="msg">i would better to take 3-5 major services (metamask, MEW, etc) and let @patrick771 or @hester look at it from UX perspective.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-24 18:10</div><div class="msg">Don't use MEW today they had a problem:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-04-24 18:13</div><div class="msg">@andreaf no worries, i will work on this tomorrow most likely , champions league is soon :slightly_smiling_face: Also we can always focus on metamask and something else</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 10:37</div><div class="msg">@andreaf hi, is the description updated? (I would really like to check all those services which should work instead of checking only 2 of them)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 10:47</div><div class="msg">not finished yet because I was working on a bug yesterday and I didn't have the time to finish. I think 2 of them are enough, the goal is to prove we are using the standard way following BIP39 so that it's compatible in general, not forcing the use of a list of other apps</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 15:28</div><div class="msg">@adan found a very interesting issue that we need to solve.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:28</div><div class="msg">and we need some UX solution for that</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:29</div><div class="msg">the issue is simple:
|
|
1. Restore an account with a passphrase and a password e.g. `onion among jungle arm issue divorce sand keep dust meadow olympic humor`
|
|
2. try to restore the same account with the same passphrase but with a different password
|
|
|
|
Actual Result: the account is not restored and user stays on recovery screen</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:29</div><div class="msg">so the account can be restored only with the password which has been entered for the first time</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:30</div><div class="msg">and we need to change the user flow for recovery before closing the issue</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:31</div><div class="msg">#design-team ^</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-26 15:33</div><div class="msg">what is expected result? @adan</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:34</div><div class="msg">it's hard :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:35</div><div class="msg">I don't know the expected result</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:35</div><div class="msg">maybe an error message `the account is already restored`?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:35</div><div class="msg">if we are using the same passphrase</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:35</div><div class="msg">can we check that? @andreaf</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 15:40</div><div class="msg">good job! I can explain why it works like this and we can decide together the how we can change it.
|
|
|
|
*how it works in the current versions*:
|
|
|
|
* `onion among jungle arm issue divorce sand keep dust meadow olympic humor` + password 123456 generates account A1
|
|
* if I recover an account with the same data, and it's already in the app, then you are logged in with that account A1
|
|
* if you use `onion among jungle arm issue divorce sand keep dust meadow olympic humor` with password 000000 it recovers a different account (mnemonic words + different passphrase = different private key and address)
|
|
|
|
*with the new code, of idea 142, it works like this:*
|
|
|
|
1 - I recover account with words `onion among jungle arm issue divorce sand keep dust meadow olympic humor` and password 123456 (only the mnemonic words are used to generate the private key and the address)
|
|
2 - I recover again with words `onion among jungle arm issue divorce sand keep dust meadow olympic humor` but password 000000. Even if the password is different the final account is the same, because the password doesn't alterate the private key and address. So the app checks if an account with that address exists and it finds it (the one created at step 1)
|
|
3 - the app tries to log in using the first account which has the same address (the address generated is like the username), but it tries to decrypt the key store file with `000000` which is not the right password because it's been encrypted at step 1 with password `123456`
|
|
|
|
A solution could be showing a message saying "The account you are trying to recover is already present in the app" or something like this. so that the user can try the login instead of the recover. but to be honest I'm not sure which solution is the best. I need your help</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-26 15:47</div><div class="msg">Could this message say ?Wrong password??</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:48</div><div class="msg">nope :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:48</div><div class="msg">`The account you are trying to recover is already present in the app with different password`</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 15:49</div><div class="msg">it depends. because if users don't remember that they already recovered the account in that device, they know that there's no right password, when they recover for the first time they can use any password to encrypt the private key</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:50</div><div class="msg">I think we should show only passphrase input on recovery screen, also we need 2 password inputs on the next screen like: `Enter password` and `Confirm password`</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 15:50</div><div class="msg">unless we remove the old one and create the new one. which would be the process to do when users forget the password</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:50</div><div class="msg">and on the second screen we need to notify user that a password has no relation to the passphrase and it will be used only for logging into Status app</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:51</div><div class="msg">or we can show this on single recovery screen :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:52</div><div class="msg">so `forget the password` will remove the account and after will create the new one with new password? LGTM :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 15:56</div><div class="msg">we can also test the current behaviour we have in nightly actually. if you recover an account that you already recovered what happens? does it log you in or does it remove and re-create the account?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-26 15:56</div><div class="msg">I find this user story `User that has account on the device and tries to recover same account` pretty weird</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 15:57</div><div class="msg">I know</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 15:57</div><div class="msg">:slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 15:57</div><div class="msg">but you can still do the same in the current nightly right?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-26 15:57</div><div class="msg">I haven't tried it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 15:57</div><div class="msg">if you use same words + same passwor</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:57</div><div class="msg">I can create new account in actual nightly via using the same passphrase and different password</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:58</div><div class="msg">with new changes I can't do that since password is not related to the recovery flow anymore</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 15:58</div><div class="msg">yes, but to simulate the same behaviour you need to re-create the same address. so you need to use same words + same password</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 15:58</div><div class="msg">so are you logged in or it's re-creating the same account?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-26 15:59</div><div class="msg">and if I am doing the same words + same password in actual nightly I will be logged with the same account</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 15:59</div><div class="msg">I see the "help improve status by sharing usage pattern", like I re-created the account from scratch</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-26 16:00</div><div class="msg">@adan there was Jarrad?s concern about on how to encrypt keystore file then. He believes that only passphrase is not enough</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 16:01</div><div class="msg">the encryption of the keystore didn't change. we are still encrypting the keystore in the same way, only with the password</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 16:02</div><div class="msg">the thing that we changed here is the generation of the seed the generates keys and address. before it was generated with words + password. now with words. we still use the password to encrypt the keys in the same way</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 16:07</div><div class="msg">when you login, you are using the address as username, and the password you used to encrypt the file, as password. when you create an account in nightly you user the same password to encrypt the keystore and to generate the keys and address. if you recover with the same words and different password, you generate a different username, which is a different address. so it generates another keystore file because the account is different.
|
|
with this idea, the password is used to encrypt the keystore, but not to generate the "username". so the 12 words, even with different password, generate the same username. that in this issue, is already present, but encrypted with different password</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-04-26 17:23</div><div class="msg">I tried this about a month ago and it re-created the account, which I wasn't expecting (lost all my messages and contacts)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-26 17:25</div><div class="msg">so maybe we can continue doing the same. I can write some tests to prove this behaviour.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-27 14:50</div><div class="msg">@denis-sharypin do you want to organise another call for next week to talk more about this issue?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-27 14:58</div><div class="msg">@andreaf yes please, on our Weekly Design call we decided that we need to put effort of all design peeps on that to solve this.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-27 14:58</div><div class="msg">thank you @denis-sharypin! ok I will do it</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2018-04-28 13:54</div><div class="msg">Hi here, so how far are we from being able to recover an account from metamask ?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2018-04-28 13:56</div><div class="msg">I'm willing to help test this because I want to play ethergoo on status :smile:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-04-28 14:38</div><div class="msg">do you mean you have progress and want to sign in in status to continue playing?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2018-04-28 14:54</div><div class="msg">Yes :smile: I don't think people who are playing want to start from scratch</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 15:14</div><div class="msg">especially if you bought en expensive cryptokittie :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 15:14</div><div class="msg">Branch: status-im:experiment/wallet-compatibility
|
|
Android: <a href="https://i.diawi.com/sfyNTh">https://i.diawi.com/sfyNTh</a>
|
|
iOS: <a href="https://i.diawi.com/KJ79Y8">https://i.diawi.com/KJ79Y8</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 15:15</div><div class="msg">the only issue to fix is:
|
|
|
|
<a href="https://github.com/status-im/status-go/pull/858#issuecomment-385182134">https://github.com/status-im/status-go/pull/858#issuecomment-385182134</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 15:22</div><div class="msg">@yenda @andrey please tell me if with those builds you can continue playing or if you have any issue</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2018-04-28 15:23</div><div class="msg">I get oops the application is gone</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2018-04-28 15:23</div><div class="msg">I think you have to make another build</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 15:23</div><div class="msg">ah, ok I'll do it now</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 15:24</div><div class="msg">started build 5?79</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-04-28 16:36</div><div class="msg">but to play you need latest status-react @andreaf is your brunch rebased onto latest develop?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 16:36</div><div class="msg">ah, it's not, I'll update it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 16:37</div><div class="msg">the previous build is still running so mine hasn't started yet</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 16:39</div><div class="msg">@andrey do we need only new changes from status-react or something else added in status-go?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-04-28 16:40</div><div class="msg">for ethergoo should be enough status-react</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 17:09</div><div class="msg">looks like 578 it's stuck and mine never starts</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 17:09</div><div class="msg"><a href="https://jenkins.status.im/job/status-react/job/parametrized_build/">https://jenkins.status.im/job/status-react/job/parametrized_build/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 17:10</div><div class="msg">jenkins is so slow that in the meantime I manage to create a bot lib for ruby
|
|
|
|
<a href="https://github.com/pilu/status-bot-rb">https://github.com/pilu/status-bot-rb</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 17:47</div><div class="msg">ok my build is running, I stopped the previous one, it was running for 15 hours</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-28 18:15</div><div class="msg">the new build is also stuck, I think there is a problem with jenkins</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-29 03:36</div><div class="msg">> Yes :smile: I don't think people who are playing want to start from scratch
|
|
|
|
Great point</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-30 08:30</div><div class="msg">@denis-sharypin is today good for this meeting? we can do you after the HD Wallet study session if you can</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-30 08:40</div><div class="msg">Nope, unfortunately. Shall we make it on Wednesday? Today is a bank holiday in some places</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-30 08:40</div><div class="msg">yes Wednesday is good!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-04-30 08:40</div><div class="msg">:+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-30 13:07</div><div class="msg">@andrey @yenda this build works, let me know if you test it please</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-04-30 13:14</div><div class="msg">btw i caught myself that i don't have mnemonic, only json, so for me it would be useful to have import json file functionality</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-30 15:26</div><div class="msg">as we said at today's study session, this idea can be interesting as long as we keep experimenting on the login/recover process to make it better, especially following #152-friends-recovery. I'm organising another call for this Wednesday, please ping me if you are interested. This will be especially focused on deciding how to manage from the UX/UI prospective this issue:
|
|
|
|
<a href="https://github.com/status-im/status-go/pull/858#issuecomment-385182134">https://github.com/status-im/status-go/pull/858#issuecomment-385182134</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-02 12:16</div><div class="msg">thank you everyone for the ideas you had during the meeting, and for your help! :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-02 12:16</div><div class="msg">Branch: status-im:experiment/wallet-compatibility
|
|
Android: <a href="https://i.diawi.com/5fGx3c">https://i.diawi.com/5fGx3c</a>
|
|
iOS: <a href="https://i.diawi.com/oAGuFM">https://i.diawi.com/oAGuFM</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-02 12:16</div><div class="msg">you can test this build :point_up:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-07 11:37</div><div class="msg">I'm going to rename the idea, and as we said maybe merging it with #094-compatibility. is it possible to rename this channel as well?
|
|
I started using "recovery" because initially instead of "Add exisiting account", we had "Recover access"
|
|
|
|
<a href="https://wiki.status.im/images/thumb/4/45/Image_09.png/600px-Image_09.png">https://wiki.status.im/images/thumb/4/45/Image_09.png/600px-Image_09.png</a>
|
|
|
|
but now I understand that it might be confusing because it sounds similar to #152-friends-recovery</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-08 15:24</div><div class="msg">given the new structure for the teams, I would like to finish this idea ASAP. Yesterday we received the audit document and everything on this part of the code is fine. I think as a first iteration we can just merge this after testing and see if we want to change the copy under the password field when we create a new account. what do you think? Otherwise after using mainnet it would be impossible to import old accounts /cc @chad @denis-sharypin @patrick771 @andrey @hester @adan @nastya</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-08 15:24</div><div class="msg">Yes, sure</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-05-08 15:26</div><div class="msg">I would say go fo it. We could adjust flows, copy, and properly announce it a bit later</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-05-08 15:26</div><div class="msg">but what others think</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-08 15:26</div><div class="msg">ok, so I'll prepare a document for testing and clean the ideas</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-05-08 21:52</div><div class="msg">I really support this, because of mainnet most urgently, and also because it will make it easier for beta users to access real funds</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-09 11:43</div><div class="msg">can you please have a look at this PR?
|
|
I added more documentation, merged the ideas 94 and 142, specified that the changes went through the security audit, etc.
|
|
I'm moving the documentation for testing in a separate doc
|
|
<a href="https://github.com/status-im/ideas/pull/256">https://github.com/status-im/ideas/pull/256</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 08:17</div><div class="msg">@andreaf has renamed the channel from "142-recovery" to "142-compatibility"</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 10:10</div><div class="msg">@adan @nastya I'm preparing another build to test because the one I built yesterday has other problems on transactions so I need to update them with the new fixes</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-11 10:10</div><div class="msg">sure</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-11 10:10</div><div class="msg">it would be great to know whats new is in this build</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-11 10:11</div><div class="msg">i am not sure why but it is very difficlut to me personally to track what is going on with this idea/swarm , as we dont have issues, board and so on (maybe no need but anyway) :disappointed:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 10:12</div><div class="msg">we have this one @nastya <a href="https://github.com/status-im/status-go/projects/14">https://github.com/status-im/status-go/projects/14</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-11 10:12</div><div class="msg">yeah it is always empty )</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 10:12</div><div class="msg">but the idea was paused because we had to wait for the audit, and now it's completed</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-11 10:12</div><div class="msg">sure sure</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-11 10:12</div><div class="msg">:cookie:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 10:13</div><div class="msg">we only have an issue that I added in the TODO</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-11 10:14</div><div class="msg">thanks ! i am sorry i got so distracted in last few days :disappointed: thanks Andrea</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 10:14</div><div class="msg">I would like to merge it and then solve that issue, what the best way to do it? shall I write it in a document, or in an issue there? Is it ok to have issues not solved, but to be solved in the next iteration?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 10:15</div><div class="msg">> thanks ! i am sorry i got so distracted in last few days :disappointed: thanks Andrea
|
|
not your fault, the swarm was paused so we didn't do much</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 10:15</div><div class="msg">@nastya but please tell me what I can improve</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-11 10:16</div><div class="msg">i think u can do both options! but personally i want to have the feature to restore account in metamask some day soon in develop so we can check it with #status-everyday</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 10:17</div><div class="msg">yeah that's already in the build I'm doing, the only issue is the one in the TODO column but it can be fixed after merging. merging soon is better because it has breaking changes</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-11 10:17</div><div class="msg">:heart:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 14:01</div><div class="msg">@adan @chad @nastya I created this document describing what happens if you upgrade and how to move your tokens to a new account. Please tell me if something is missing
|
|
<a href="https://docs.google.com/document/d/1DLZCwDsqJZHpGl7JTZQBsPN0o2N5XeN9aDrqZHXGemM/edit#heading=h.z8jn4vo8zd12">https://docs.google.com/document/d/1DLZCwDsqJZHpGl7JTZQBsPN0o2N5XeN9aDrqZHXGemM/edit#heading=h.z8jn4vo8zd12</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 14:06</div><div class="msg">@adan @nastya here a new build of the wallet compatibility. I know we already tested it in the past, but we waited a lot for the audit and I needed to rebase the branch and get all the new features from `develop`. can you test it again please? :heart_eyes_cat:
|
|
|
|
If everything is ok we can merge it and have a new iteration to fix the bug found by @adan.
|
|
|
|
@chad what's the best way to organise this? merging and then a meeting to understand future iterations? or just opening issues on github? I'm asking because after this week I'm joining the p2p team so I'm not sure if new iterations will be part of #core-wallet</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-11 14:07</div><div class="msg">I can do that only on this weekends</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 14:07</div><div class="msg">@denis-sharypin @hester @patrick771 also from UX/UI point of view, I think we have to do some small changes in the next iterations. Feel free to tell me the bst way to do it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 14:08</div><div class="msg">we can also wait and do it on monday!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-11 14:08</div><div class="msg">k</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 14:08</div><div class="msg">@andreaf set the channel topic: Idea: <a href="https://github.com/status-im/ideas/pull/142">https://github.com/status-im/ideas/pull/142</a>
|
|
Board: <a href="https://github.com/status-im/status-go/projects/14">https://github.com/status-im/status-go/projects/14</a>
|
|
|
|
Upgrade: <a href="https://docs.google.com/document/d/1DLZCwDsqJZHpGl7JTZQBsPN0o2N5XeN9aDrqZHXGemM/edit#heading=h.z8jn4vo8zd12">https://docs.google.com/document/d/1DLZCwDsqJZHpGl7JTZQBsPN0o2N5XeN9aDrqZHXGemM/edit#heading=h.z8jn4vo8zd12</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 14:09</div><div class="msg">@andreaf set the channel topic: Idea: <a href="https://github.com/status-im/ideas/pull/142">https://github.com/status-im/ideas/pull/142</a>
|
|
Board: <a href="https://github.com/status-im/status-go/projects/14">https://github.com/status-im/status-go/projects/14</a>
|
|
Upgrade: <a href="https://docs.google.com/document/d/1DLZCwDsqJZHpGl7JTZQBsPN0o2N5XeN9aDrqZHXGemM/edit#heading=h.z8jn4vo8zd12">https://docs.google.com/document/d/1DLZCwDsqJZHpGl7JTZQBsPN0o2N5XeN9aDrqZHXGemM/edit#heading=h.z8jn4vo8zd12</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-05-11 14:09</div><div class="msg">yes we are working on it. Hester sent an invite for a review session with her proposal</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 14:10</div><div class="msg">awesome! thank you!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-05-11 14:33</div><div class="msg">Can you please allow commenting in the doc?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 14:34</div><div class="msg">I updated it to "anyone with the link can edit", does it wotk now?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-05-11 14:37</div><div class="msg">Thanks</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-05-11 14:39</div><div class="msg">Let?s continue discussion in the doc. I'll ping other swarm TO?s to coordinate</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-11 14:48</div><div class="msg">thank you!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-14 07:35</div><div class="msg">@adan @nastya I would like to merge this PR today. do you have time for another test?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-14 07:46</div><div class="msg">i will try , maybe @adan could assist meantime. Anyway i will try to do this today!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-14 07:47</div><div class="msg">about the github project, is there anything I need to change to be ok with the test/merge flow for the test team?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-14 07:48</div><div class="msg">i think making PR is enough!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-14 09:58</div><div class="msg">@andreaf if i created an account a year ago in my ether wallet - will i be able to restore it in status after this PR merged?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-14 10:41</div><div class="msg">I think my ether wallet doesn't give you a 12 mnemonic words so you won't be able. MyCrypto beta instead allows you to create a mnemonic wallet, so you would be able to do it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-14 10:45</div><div class="msg">It does</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-14 11:03</div><div class="msg">@nastya ah maybe I missed it. If I goo to my ether wallet I only see a way to create wallet and download the keystore file. where can I go to create a mnemonic wallet</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-14 11:03</div><div class="msg">?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-14 11:12</div><div class="msg">Or i missed that!:) lets double check</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-14 11:49</div><div class="msg"><a href="http://prntscr.com/jhnnal">http://prntscr.com/jhnnal</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-14 11:53</div><div class="msg">that part is more for importing it to my ether wallet, more than creating a new one. Mostly because it doesn't generate the words for you, and you should't pick the 12 random words by yoursel, but use a wallet that create them.
|
|
but anyway it works, so the final answer is yes, you can import it as long as you specify the words leaving empty the password field</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-14 11:53</div><div class="msg">:heart:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-14 11:54</div><div class="msg">if you try the beta version of my crypto, it allows you to generate a new mnemonic wallet where it generates those words for you:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-14 11:54</div><div class="msg">asking because a lot of people in status now are using real ETH for testing and it won't be good if we can't access our accounts (</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-14 11:54</div><div class="msg">yeah my crypto is more friendly )</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-14 11:55</div><div class="msg"><a href="https://prnt.sc/jhnqja">https://prnt.sc/jhnqja</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-14 11:56</div><div class="msg">you are right @nastya, check also this document about that <a href="https://docs.google.com/document/d/1DLZCwDsqJZHpGl7JTZQBsPN0o2N5XeN9aDrqZHXGemM/edit">https://docs.google.com/document/d/1DLZCwDsqJZHpGl7JTZQBsPN0o2N5XeN9aDrqZHXGemM/edit</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-14 11:57</div><div class="msg">:+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-14 17:14</div><div class="msg">I merged the PR, I'm going to open one for status-react to use these changes</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-14 22:12</div><div class="msg">@adan PR opened in `status-react` <a href="https://github.com/status-im/status-react/pull/4262">https://github.com/status-im/status-react/pull/4262</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-05-15 06:37</div><div class="msg">hey @andreaf great job! i have one question from security pov, before, if someone stole my 12 words he couldn't recover account, but after this change he can? do we have plans for the future to keep this incompatible but more secure way with password? for example i can choose when generate account, i want more secure but not compatible or compatible but less secure, wdyt ?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 07:53</div><div class="msg">yes we can add the option to use a password to generate the seed. though the 12 words should be used and saved like you would do for a password.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 09:01</div><div class="msg">@nastya is there anything else I can do to improve the testing flow?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-15 09:02</div><div class="msg">it is good! we will pick it up once reviewed! thanks @andreaf</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 13:57</div><div class="msg">is there anything I can do to help for the testing part @adan?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 13:57</div><div class="msg">no worries, I am fine :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 13:58</div><div class="msg">I will update the PR with changes for automated tests in an hour and we are good to merge the PR</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 13:58</div><div class="msg">thank you, did you manage to re-create all those test accounts :sweat_smile: ?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 13:58</div><div class="msg">awesome!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 13:58</div><div class="msg">~7 left</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:15</div><div class="msg">additional issue in recovery logic is found. there is a PR
|
|
There is a pr <a href="https://github.com/status-im/status-react/pull/4058">https://github.com/status-im/status-react/pull/4058</a>
|
|
Wallet onboarding was added in scope of the PR, but we are not showing the onboarding for recovered users since we assume that they already created an account within Status</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:16</div><div class="msg">however with #142-compatibility we potentially may get users with recovered accounts from other products</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:17</div><div class="msg">right, so you mean we should always show it because the account could have been created in metamask for example</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:17</div><div class="msg">as result we are not showing the wallet onboarding to them, but we should :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:17</div><div class="msg">yeah I was asking the same in the thread</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:17</div><div class="msg">sorry, missed that</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:17</div><div class="msg">:disappointed:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:17</div><div class="msg">yes we can create an issue and start thinking about it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:17</div><div class="msg">don't worry :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:18</div><div class="msg">anyway @adan thank you for this tests, I know it's been long to do it :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:19</div><div class="msg">nw :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:20</div><div class="msg">what's the next step? waiting for jenkins in the PR?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:22</div><div class="msg">nope, we are fine, we got the result from automated tests and all transaction users are added in the right way</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:22</div><div class="msg">we had 1 infra issue and 2 issues in group chats</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:23</div><div class="msg">do we have any changes in latest go version related to group chats, should I retest them manually?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:23</div><div class="msg">I am assuming that updating go means that we are updating to the latest go version which includes more changes</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:23</div><div class="msg">not in our commits but it might be that `develop` had something new</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:23</div><div class="msg">yep</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:23</div><div class="msg">yeah exactly</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:23</div><div class="msg">so I need to recheck group chats</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:24</div><div class="msg">and I will rerun extended set of tests to be sure that no new issues there</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:26</div><div class="msg">so we are waiting for <a href="https://jenkins.status.im/job/end-to-end-tests/job/status-app-nightly/">https://jenkins.status.im/job/end-to-end-tests/job/status-app-nightly/</a> to run all tests</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:26</div><div class="msg">results will be in <a href="https://ethstatus.testrail.net/index.php?/runs/view/235&group_by=cases:section_id&group_order=asc">https://ethstatus.testrail.net/index.php?/runs/view/235&group_by=cases:section_id&group_order=asc</a> (guest account in LastPass, just in case)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:42</div><div class="msg">so we are fine to merge now</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:42</div><div class="msg">cool, so was it all good?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:42</div><div class="msg">no new issues found, only known issues</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:43</div><div class="msg">nice thank you!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:43</div><div class="msg">you told several times that you are going to create an issue regarding the behavior with different passwords for 1 passphrase, can you link me the issue if it's already created?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:44</div><div class="msg">please :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:44</div><div class="msg">I have it in my notes but not created in github because it wouldn't make sense without merging</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:44</div><div class="msg">I'm merging now, and create it :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:44</div><div class="msg">stop</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:44</div><div class="msg">don't merge</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:44</div><div class="msg">one last thing left</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:45</div><div class="msg">ok</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:45</div><div class="msg">we need to inform #status-everyday</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 15:45</div><div class="msg">yes</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:53</div><div class="msg">so I see no blockers for merging the feature</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-05-15 15:53</div><div class="msg">:tada:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 16:09</div><div class="msg">@adan I created the PR <a href="https://github.com/status-im/status-react/issues/4284">https://github.com/status-im/status-react/issues/4284</a> :sweat_smile:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-15 22:04</div><div class="msg">there was also a discussion here, just recap where we started <a href="https://status-im.slack.com/archives/C93KX711U/p1520844236000228?thread_ts=1520787585.000011&cid=C93KX711U">https://status-im.slack.com/archives/C93KX711U/p1520844236000228?thread_ts=1520787585.000011&cid=C93KX711U</a></div></div></div><br/>
|
|
<div><img src="" /><div class="message"><div class="username"></div><div class="time">2018-05-16 14:28</div><div class="msg">@hester commented on @hester?s file <a href="https://status-im.slack.com/files/U8DN8BUKG/FARSFQA6T/Design_review_of_the_Wallet_recovery_compatibility_flow">https://status-im.slack.com/files/U8DN8BUKG/FARSFQA6T/Design_review_of_the_Wallet_recovery_compatibility_flow</a>: cc @goranjovic @chad</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-17 06:55</div><div class="msg">kudos @adan for helping with all the testing the other day</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-17 06:56</div><div class="msg">kudos @nastya for helping testing in the first iteration before the audit</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-17 06:56</div><div class="msg">:rocket:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-17 06:57</div><div class="msg">@chad do you think we can close this swarm and update the idea if we are sure all the new issues are managed by wallet team?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-05-17 06:58</div><div class="msg">Yes. @goranjovic happy to take this baby?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-17 07:14</div><div class="msg">I'm off course open to help if need so please tell me @goranjovic</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2018-05-17 07:19</div><div class="msg">@chad @andreaf Works for me guys :beers:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-05-17 07:20</div><div class="msg">Just to confirm, have all the post merge issues been created? If not can we document before we forget?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-17 07:20</div><div class="msg">for now we only have this issue: <a href="https://github.com/status-im/status-react/issues/4284">https://github.com/status-im/status-react/issues/4284</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-17 07:21</div><div class="msg">we don't have anything else. and then the design review <a href="https://status-im.slack.com/files/U8DN8BUKG/FARSFQA6T/Design_review_of_the_Wallet_recovery_compatibility_flow">https://status-im.slack.com/files/U8DN8BUKG/FARSFQA6T/Design_review_of_the_Wallet_recovery_compatibility_flow</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-17 07:50</div><div class="msg">@andreaf just moved all funds from my old status account to MyCrypto and was able to restore it in nightly! :partyparrot:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-05-23 07:51</div><div class="msg">@andreaf @nastya thats interesting, today i tried to recover my account, but it was different, and i tried second time and it was mine account is it known?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-05-23 07:58</div><div class="msg">Which build?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-05-23 08:02</div><div class="msg">c0bad8f8</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-23 08:15</div><div class="msg">Are you 100% sure you used the 12 words? I had the same problem in the past but I wrote the wrong words but we don't have validation on those</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-05-23 08:16</div><div class="msg">i copy pasted same words</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-05-23 08:16</div><div class="msg">so no mistake for sure</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-05-23 08:16</div><div class="msg">only if i some how added symbol by mistake</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-05-23 08:19</div><div class="msg">Yeah exactly. Also because the generation of the seed is deterministic, so it can't change. But try again when you have time just to see if it happens again</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/a4ec07f3ff1139a4880345d1da1995bc.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0011-72.png" /><div class="message"><div class="username">youngwook</div><div class="time">2018-08-13 05:26</div><div class="msg">has joined #142-compatibility</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-10-08 11:06</div><div class="msg">@naghdy archived the channel</div></div></div><br/>
|
|
</div></body></html> |