Currently, we are using the standard browser alert messages. We need to create and use our own.

• ui
• generalize usage - pass payload ( json ) with info about the message

Call the claim() function on the tipping contract providing the domain name that the user want to verify.

See waellet-contracts

Extension broke when you click on the title of modal window

UI improvements on current account routes

• unify color scheme
• unify buttons used
• responsive

another view allowing the user to repeat his phrase in order for us to be sure he saved it.

Here is some feedback,

1. UI - When clicking on “generate new wallet” the “loading sign” is a bit to the left (not in the center)

2. UI - The three dots here don’t do anyting:
   

3. UI - I am not sure if this “copy button” does anything:

4. UI - If I go to “send” - I can’t go back to the main screen (I have to close the extension and re-open)

5. UI - Closing the extension and opening it selects Testnet automatically.

6. UI - Send-to address is displayed in a weird way:
   

7. Sending of the full amount that is available on the account does not work. The “loading sign” never disappears. Maybe a warning should be added that states the maximum amount that can actually be sent.

https://forum.aeternity.com/t/update-week-18-waellet-browser-wallet-extension/3362/3?u=ae-vlad

Validate all fields on import view

Similar to metamask UI

We need to implement build script for firefox.

Some modifications to the code might be necessary in order to support other browsers than chrome as well.

Further readings:
https://medium.com/@yorkxin/things-i-learned-from-migrating-a-chrome-extension-to-firefox-using-webextensions-975474d4fa77

Put every string from the UI in the locales configuration file in order for an easier transition in different language support.

We also want the user to be able to import a keystore.json file to access his wallet

Configure system contract details for tipping functionality.

We need a view to present the generated seedphrase for the users wallet.

Allow the user to sign and confirm the tx that a website/aepp is asking.

When keystore used in from the sdk the webpack build procedure is failing.

See here

For now, the import only works with a plain secret key. We need support for importing seed phrase as well

Navigation bar UI

seed phrase generate [generate waellet screen]

Two steps:

• generate seed phrase
• confirm seed phrase

connect to aeblockchain via the sdk in the extension

Advice people to use stronger password for encrypting their private key.

We can add also a "password strength meter"

We can improve the transaction history with the ability to filter tx in various ways:

• type of transaction (spendtx and other)
• sent/received
• amount
• by specific address

We need abillity to change main account name, manage subaccounts or simply add new subaccount

Ability to derive multiple addresses from the same private key.

basic ui showing the address balance

Ability to sign and send a transaction (spendtx)

Define and design the UI of the navigation bar account section

The functionality that I intended to bring into the waellet - broadcasting a signed transaction, may not be a good option due following (just thinking out loud):

• transaction history (currently planned) won't be able to display it since the tx doesn't necessarily need to be signed by the active account.

I'm wondering if it's proper to implement it this way.

View with tx details on click.

Generate a QR code which can be used for receiving ae.

• Create config with all possible errors and descriptions

Check metamask . First page a user sees after reopening the extension should be prompting him to unlock his waellet.

Ability to choose the import method:

• plain private key
• keystore.json [keystore format according to aex-3]
• seed phrase [Check base-aepp seed import view]

===

view for tipping website functionality

We need to have ability to switch and select different UI language.

Notifications modal for confirming user actions

Provide test cases for each view.

We should add the ability for the website to communicate with the extension via postmessages - see aex-2 & identity poc

When generating wallet you are given the seed phrase, then you are on the next view which requires you to confirm the phrase - the order of the words given there should be scrambled. Currently, they are ordered the same as shown previously.

generate wallet functionality