It would be great if we had a dialog that asks for user consent to collect anonymized usage data. This data would be great to have for our own analysis.

The total balance of all the addresses for an account is displayed next to an Account label. Keep in mind that Tezos balances can have up to 6 decimal places. We are rounding the number to two decimal places and showing that it's approximate by adding "~" in front of the number. On hover, we should display the full balance and a copy button.

Design:
https://zpl.io/2EAReXY

As part of the move to the latest back end Tezos interface, the return types of sendTransactionOperation and sendDelegationOperation() have been rationalized. If there is an error, an explicit Error is thrown. If there is not an error, the operation ID and the results are returned. The operation ID should be shown to the user after a successful operation send in a snackbar. Otherwise, the error should be shown in the snackbar.

As reference, here is the TypeScript definition of the result object:

/**
 * Result of a successfully sent operation
 */
export interface OperationResult {
    results: TezosTypes.AlphaOperationsWithMetadata,
    operationGroupID: String
}

export interface AlphaOperationsWithMetadata {
    contents: AlphaOperationContentsAndResult[],
    signature: string,
    kind: string, //only if error
    id: string, //only if error
    contract: string //only if error
}

export interface AlphaOperationContentsAndResult {
    kind: string,
    metadata: AlphaOperationResult
}

export interface AlphaOperationResult {
    status: string,
    originated_contracts: string[]
    errors: string[]
}

If we require the password to me at least 8 characters long we need to message this to the user and let them know if they had or had not satisfied the requirement.

We need to add a field to confirm wallet password. We also need to show messaging if the passwords match or error messaging if they don't match. Ideally, we'll show that the passwords don't match as soon as the user makes a mistake during typing.

Ask me if you have any questions about messaging for passwords matching or not matching.

At the moment, amounts entered for transactions and account creation are not validated. We should ensure only valid numbers conforming to a regular expression are accepted.

Similarly, Tezos addresses ('tz1...' or 'TZ1..') should also be validated with a regular expression to ensure they are of a valid form.

When a new identity is imported or created, getAccount() is used to get the details of the identity, specifically its balance. A second call is then made to getAccounts() to get the child accounts of the identity in order to get the addresses and balances of the child accounts. Unfortunately, if an identity (even if valid) has not been activated on the blockchain then getAccount() will fail. In this case, the UI simply doesn't show the identity which might cause panic for users if they think that identity has failed. Instead, when the call fails, we should still show the identity and show the balance as 'Unknown'.

Similar to the above, when a new child account is created using sendOriginationOperation, there is some lag before the account is actually available on the blockchain. Again in this case, the getAccount() for getting the account balance will fail and the new account will not appear on the left. Instead, a fix should be made so that when a new account is created, it is added the list on the left with its balance set to 'Unknown'.

Eventually, when the wallet periodically refreshes its data, the correct balance will show up for all identities and accounts.

The best practices for Electron security are listed at https://github.com/electron/electron/blob/master/docs/tutorial/security.md. We should ensure all steps listed there are followed in the wallet code.

Currently, the user is stranded at this step with no way to get accept quitting the app.

• Show authenticated wallet header with wallet name and logout option
• Display the import and create new tabs module on the plain grey background

Zeplin:
https://zpl.io/blpj4o0

• Remove mnemonic and key pair tabs from Add an Account screen.
• Rename "Import Fundraiser" tab to "Import Fundraiser Wallet"
• Change Import fundraiser instructional text to "Please refer to the PDF document that you created during the Fundraiser."
• Use proper field labels: 15 Word Secret Key, Fundraiser Password, Fundraiser Email Address, KYC/AML Activation Code.
• Add tooltips to Fundraiser Password, Fundraiser Email Address, and KYC/AML Activation Code. (text provided below)

Fundraiser Password Tooltip:
This is the password that you used when generating a Tezos paper wallet to participate in the Fundraiser.
Email Tooltip:
This is the email address that you used when generating a Tezos paper wallet to participate in the Fundraiser.
KYC/AML Activation Code Tooltip:
This is the activation code that you received after completing the KYC/AML process. An activation code corresponds to a public key hash and is required if you participated in the Fundraiser. You may complete the process at verification.tezos.com if you have not done so already.

Designs:
https://zpl.io/blpj4o0
https://zpl.io/2ZJDxYE

The 'Create' panel of the wallet app displays the password the user is typing in clear text. This should be masked as stars and the user asked to type the same password twice as a security precaution.

Make password optional

Let's drop the pw for now

When a user creates a new wallet, there is no constraint on the length of the password. They should be asked for a minimum of eight characters instead.

We will be programmatically generating labels for Accounts, Manager Address, and Smart Addresses.

Account Labels
Account n+1 (n=0) [ first account will be labeled Account 1, second Account 2, and etc.]

Manager Address Label
Each account's identity will be labeled as "Manager Address"

Smart Address Labels
Each "TZ1" Smart Address will be labeled using the same approach as Accounts (Smart Address 1, Smart Address 2, etc).

Labels should be displayed in the sidebar and on each Address detail pane.

We currently refresh every minute. Add timestamp next to refresh icon to show the time of the last refresh in the following format:
"Last updated 11:22 PM"

Design:
https://zpl.io/2ZJDgP4

As Linux paths are case sensitive, capitalization in the package imports causes missing file errors. Where needed, imports should be changed to lower case.

Since prototype didn't test any data entry, we should follow best practices for entering seed words:

1. Provide autocomplete selection for each word to avoid spelling arrows or use of the words that are not on the list
2. Provide numbering of words so that user can easily cross-reference the entry.

Explain that:

• the password is the one they created during the fundraiser
  (Majority of users are not sure if the password is something they have from the fundraiser or the one they just created.)
• email is tied to their fundraiser account
• activation code is the KYC code

The wallet currently loads account information, e.g. balances, only once and only updates the information when the user hits the refresh button. It should also automatically reload balances every five minutes.

We need to add something like:
"You'll need this password to open your wallet, confirm transactions, or any time you will need to install this wallet and access your wallet from another computer"

• Disable "+" button for Adding an Account
• Add tooltip with "Coming Soon" message

Design:
https://zpl.io/2ZJDgP4

Change the copy to match the design and add a note about fundraiser with "creare wallet" link underneath "create wallet" button:

Zeplin:
https://zpl.io/29ZOgry

On the Delegate tab, the user is able to specify a delegate, hit the update button and then confirm the operation by entering their wallet password. However, this does not actually perform the operation as sendDelegationOperation() is never called. Just as the Send tab calls sendTransactionOperation() to perform the send operation, the Delegate tab should call sendDelegationOperation() to perform the delegation operation.

When the user clicks on Create Wallet, they are asked for a file location, wallet name and password. Instead, they should only be asked for a filename (using a file picker) and a password. The default extension used for the wallet file should be .tezwallet.

When a user decides to create a smart address (child) for a manager address (parent), the wallet code calls sendOriginationOperation() from TezosOperations. However, as smart addresses don't have their own public and private key and rely on the keys of their parents, a key reveal operation must also be performed on the blockchain so the rest of the participants know the public key of the parent of the new child. The new flow for creating a new smart address should be:

1. Call sendOriginationOperation() from TezosOperations
2. If the above operation is successful, the returned object will contain a value for originated_contracts. This gives the address of the new child account.
3. Wait one minute and inform the user during that time that the account is being created
4. Call sendKeyRevealOperation() from TezosOperations
5. Show the user the operationGroupID from the result object of both calls.
6. Add the new child to the list of the parent's children.

Here is an example of a result object returned by TezosOperations showing how the value of originated_contracts can be obtained:

{
   "results":{
      "contents":[
         {
            "kind":"origination",
            "source":"tz1aj32NRPg49jtvSDhkpruQAFevjaewaLew",
            "fee":"1",
            "counter":"102",
            "gas_limit":"120",
            "storage_limit":"0",
            "managerPubkey":"tz1aj32NRPg49jtvSDhkpruQAFevjaewaLew",
            "balance":"100",
            "delegate":"tz1aj32NRPg49jtvSDhkpruQAFevjaewaLew",
            "metadata":{
               "balance_updates":[
                  {
                     "kind":"contract",
                     "contract":"tz1aj32NRPg49jtvSDhkpruQAFevjaewaLew",
                     "change":"-1"
                  }
               ],
               "operation_result":{
                  "status":"applied",
                  "balance_updates":[
                     {
                        "kind":"contract",
                        "contract":"tz1aj32NRPg49jtvSDhkpruQAFevjaewaLew",
                        "change":"-100"
                     },
                     {
                        "kind":"contract",
                        "contract":"TZ1gN9JSgWeGWB47bY8g3K9xQHysTwBrLPy6",
                        "change":"100"
                     }
                  ],
                  "originated_contracts":[
                     "TZ1gN9JSgWeGWB47bY8g3K9xQHysTwBrLPy6"
                  ]
               }
            }
         }
      ],
      "signature":"edsigu34SShkDWpfMeQkBoyiBkFjjFWPCnk6KzeW3gjTFzj2oxrSTiVGT15S1b9xi9gmPycgX1ESYXVf1AtDq6K6Vra5diY1CDb"
   },
   "operationGroupID":"op1.."
}

Passwords should be validated in the front end code first before they are passed to ConseilJS.

When the user clicks Import Wallet and enters a filename and password to import, there is no error message if the password is incorrect or the file is invalid. The interaction just fails silently. There should instead be an error message in red stating there was a failure and, where possible, the reason for the failure.

All Smart Addresses should be grouped under "Smart Addresses" heading from which the user can always add another Smart address.

The wallet currently allows the user to import the same identity more than once in the same wallet. Instead, the user should be shown an error if they import an identity which has already been imported.

The current flow with "select file" could be confusing to the user. We need a different flow that makes it clear that the new file will be generated and what it is for. At the same time, we need to comply with security audit requirements.

We also need to provide messaging around password creation, so that the user is aware of what it is for.

Please use a slug library to ensure that regardless of what the user inputs into "Name Your Wallet File" field we can transform it into a proper file name.

However, if the part where a user names the file and then picks a directory becomes too complicated implementation wise please let me know and we can scale back the design.

Zeplin Designs:
https://app.zeplin.io/project/5b1752dd44fc7a0363cd9dc8/dashboard?seid=5b2c8d534b04d64da0bc8e78

All tez amounts in the wallet are huge as they are denominated in µtez. Instead, they should be displayed in tez. One tez is one million µtez.

Let's keep amounts to two decimal places rounded up or down with "~" in front in three places:

• Total Wallet Balance
• Total Account Balance
• Address Balance Detail View
  For these three places, on hover, the user should be able to view the full amount in the tooltip and copy the accurate number.

We can display all 6 decimal places for each address in the sidebar as we have plenty of space there.

When a user tries to send a transaction, they are prompted for the wallet password as a security measure. Howerver, this is not done when they try to create a new child account. This should be fixed and the same security measure should be consistently in place for transactions, account creations and delegations.

• Change labels to match the design
• Add tooltip for "Delegate Address" field
• Remove confirm passphrase field
• Do not set the user's Manager Address as the default. Keep that field empty and just don't let them create an address unless they set it to something.

Designs:
https://zpl.io/blpMnKG
https://zpl.io/aMqpYKo

For now, let's change a passphrase to password as it looks like it's the convention that some of the most frequently used wallets (of our small user sample group).

Regardless of which way we go, we do need a confirmation field.

The Tezos RPC interface has changed significantly in the last two weeks. Conseil and Conseil.js have already been changed to make them compatible. The wallet must now pull in the right version of the Conseil.js NPM package and correctly invoke the operations.

The following dependencies are outdated: classnames, eletron-debug, react, react-dom, react-hot-loader, react-router, react-router-reduce, source-map-support (excluding dev dependencies). These should be updated to the latest stable version.

The prototype on which this wallet is based is located at https://thebrigade.invisionapp.com/share/P3JK0PTJ9F6#/screens/298932393_Wallet_-_Transactios. The look and feel of the wallet should be modified to match it.

50% of users still go first to "Open Wallet" when trying to use the wallet first-time to import their fundraiser holdings. This misconception is based on the following:

1. Tezos fundraiser PDF is a paper wallet (the words wallet are at the top of the PDF) so people think that they already have a wallet.
2. Users are not accustomed to using desktop wallets and saving their wallets to file.

Users go to 'Import from fundraiser' in the 'Add an Address' screen when they want to import tez they received in recognition of their contribution to the Tezos fundraiser. By default, these accounts are in an inactive state and are not usable. They must be explicitly activated to be usable. Unfortunately, the wallet does not yet perform the activation operation.

The current approach is:

• Call unlockFundraiserIdentity() from TezosWallet
• Call getAccount() from TezosConseilQuery
• Call getOperationGroupsForAccount() from TezosConseilQuery
• Call getAccountsForIdentity() from TezosConseilQuery

The new approach should be:

• Call unlockFundraiserIdentity() from TezosWallet
• Call getAccount() from TezosConseilQuery
• If the getAccount() call returns an error:
  • Call sendIdentityActivationOperation() from TezosOperations using the activation code provided by the user.
  • If the above call is successful, call getAccount again after a one minute delay. During this delay, the user should be explicitly asked to wait for a minute for activation.
  • If the above call is unsuccessful, display the account as 'uninitialized' on the left side of the wallet.
• Call getOperationGroupsForAccount() from TezosConseilQuery
• Call getAccountsForIdentity() from TezosConseilQuery

This logic can be tested by getting accounts from https://faucet.tzalpha.net/.

We need to provide some messaging that explains why we need the seed phrase and what we'll do with it:
"We use seed phrase to display your account in the wallet. We don't have access to your seed phrase and never will!"

We need to include backup verification for newly generated seed phrases. We can do by asking the user to type in the n-th word from the seed phrase after it was generated. The number of values for n depends on the level of security we want (2-word minimum and maximum entire phrase).

Let's do 4 words verification.

Design:
https://app.zeplin.io/project/5b1752dd44fc7a0363cd9dc8/dashboard?seid=5b2c9c408eac4a6376e1d194

Before going live we should stop storing passwords and keys in memory during wallet session and therefore we'll need the user to enter wallet password to save the new key-pair to file.

• Add messaging under the headline.
• Change the copy for "Select File" button to "Create Wallet File"
• Change "Create Password" label to "Create Password (At least 8 characters)"

Zeplin:
https://zpl.io/VYBXP6e

At the moment, the public and private keys of child accounts are set to null when operations are initiated. The Redux data model should be changed so child accounts inherit the public and private keys (but not the public key hashes) or their parent identities.

We are implementing a new information architecture for displaying what we currently call "addresses" and "accounts". In our new design the terms are reversed:

An account - is a grouping of a single "tz1" address with all "TZ1" addresses it manages

An address - refers to any address in an account.

Manager address - "tz1" address
Smart address - "TZ1" address

Designs:
Version 1: https://app.zeplin.io/project/5b1752dd44fc7a0363cd9dc8?seid=5b286ad46af9a4fe7f6d724a

Currently, we just show a space-delimited string, but that will cause a lot of mistakes when people will be writing it down. Human eye frequently loses track of the last word. This way the user is prone to miss a word or mix up the order.

We should display the seed phrase in easy to read numbered grid.

• Display Seed Phrase in a grid
• Allow the user to generate a different one

Designs:
https://app.zeplin.io/project/5b1752dd44fc7a0363cd9dc8/dashboard?seid=5b2c9c408eac4a6376e1d194