search

matthewwoo-zz / bot_2

0 stars 0 forks source link

BUG: ETH Address confusion with dApp #31

Open matthewwoo-zz opened 6 years ago

matthewwoo-zz commented 6 years ago

┆Attachments: Mismatch wallet address shows STO.png | Matching wallet addresses redirects to account creation.png

matthewwoo-zz commented 6 years ago

➤ Boris Shevchenko commented:

Shannon Clarke can be assigned for this one

matthewwoo-zz commented 6 years ago

➤ Thomas Borrel commented:

If you look at "Mismatch wallet address shows STO.png", you can see that if wallet addresses are different, the dApp shows the token information, BUT the Symbol Registration Transaction is unavailable.

Changing the metamask to use the wallet address that was used to create the token get the Issuer redirected to the account creation page, as you can see in "Matching wallet addresses redirects to account creation.png"

This issue seems to be related to the fact that the original STO was created on a different computer. Even though both have access to the same wallets via metamask.

If the issuer returns to the original computer and clears the cache, pointing to the STO's link takes the user right back to the "Create Your Account" screen, no matter what wallet is selected in Metamask.

matthewwoo-zz commented 6 years ago

➤ Thomas Borrel commented:

Shannon Clarke, Boris Shevchenko, clearing the cache seems to have a dramatic effect on what Issuers can do. Definitely something we need to explore. We cannot have the Issuers locked out of their STO pages if they clear cache or change computer.

matthewwoo-zz commented 6 years ago

➤ Shannon Clarke commented:

After a brief conversation with Thomas Borrel we identified that the issue is two-fold:

  1. Users can currently view STO details for tokens which they do not own
  2. Issuers who have cleared cache during the token creation or issuance process are redirected to the "sign up" page which can be confusing

For each issue, I suggest the following: 1) Users who try to view tokens which they do not own should only see limited information (or the buttons and form fields should be disabled)

2) The "Sign up" page should include a clear call-to-action instructing returning issuers to reconfirm/verify their email in order to assess their dashboard

matthewwoo-zz commented 6 years ago

➤ Boris Shevchenko commented:

Shannon Clarke 2) We can grab user's email and name from the API storage by his address. In this case page won't be dependant on cache. This is something that I'm going to do as a part of the Reconsider, refactor and refine email flow

matthewwoo-zz commented 6 years ago

➤ Thomas Borrel commented:

Event better - Thank you Boris Shevchenko

matthewwoo-zz commented 6 years ago

➤ Shannon Clarke commented:

Maybe this task needs to be made dependent on the other and reassigned to Boris Thomas Borrel?