@as-dr do we have a catch all loading indicator?

Also, if you click the ledger buttons really fast one after another, it causes a ledger busy error

This didn't seem to break anything, but I got this when sending a message.

1. Open up wallet main screen
2. navigate to switch accounts
3. switch from testnet to mainnet accounts
4. while mainnet accounts are loading, click "show address on ledger device"
5. broken

The "show address on ledger device" option should only be available when there is a selected wallet (with a path) in redux.

This could cause security concerns. I think we can achieve the same goal without putting the actual store on the window...

See /lib/with-redux-store.jsx

1. Plug in ledger device, unlock it, open it to dashboard
2. Attempt to call GetVersion, call should fail ("App doesn't seem to be open")
3. Do not refresh page
4. Open Filecoin app on ledger
5. Click try again
6. DisconnectedDeviceDuringOperation: The device was disconnected.

• this should involve showing a ? for gasUsed in a pending transaction
• show gasUsed > gas price and limit in the component (how can we fetch the transaction receipt from the message with the information we have from chainwatch pg db)?

1. start on an account with fil
2. switch accounts
3. go home
4. old transaction table exists

Sometimes calls to the node hang, so we should tell the user to refresh the page if this happens (misc error handling)

will wait for @listenaddress ' filecoin-address module

I selected an account from account select, let app sit for a couple mins, then tried to view accounts again but got this.

Right now everyhting is rounded down, how can a user see their exact filecoin balance?

• when we add a new message to the pending message array, also cache it in local storage
• when we confirm a message, remove the associated message from local storage (see caveat below)
• when we initialize the page, populate the pending message array with messages in localstorage

We should also mark a localstorage message as "pending" or "confirmed", so that messages that were found on chain, that have not yet made it to the chainwatch db don't disappear. So the only time we should remove a msg from local storage is once it comes back from the rest API with the same hash.

Must wait until the network reset to make this work

This also needs to exist inside the switch account screen, so that the user can refresh all the balances of all the wallets in redux at one time

Need to make clear who is making the app/who to contact if needed.

1. attempt to send tx while ledger device is busy
2. click "try again"

• terms of use
• warnings about mnemonic / imported keys
• limitations of liability clause

We may want to follow this error up with something like "If it's not busy, try unplugging and re-plugging your Ledger in".

Make sure that the error we catch that triggers a recursive poll is a gateway timeout and not any other errors

Right now for some reason, each nextjs page scrolls when there isn't enough content to warrant scrolling. This normally wouldn't matter, but it has bad side effects for the FloatingContainer on the send screen.

"Hidden" floating buttons (bc it's 8px off "bottom", which you need to scroll to see):

This was a "TODO" in the IconButtonBase above the transition property

Will check if I'm able to reproduce.

We may want to add something like "Check to see if your Ledger device is being used in another app."