Signer - Githubissues

The signer should -

[ ] enumerate or timestamp when they arrive in the signer
[ ] bulk approve all from an account? (not sure about that one... maybe just have a think about
[ ] blacklist, whitelists, graylists, time limits
[ ] notifications via extension to the user - different icons (extension)
[ ] recipient address needs to be checked in a couple of places so we can do some semantic analysis. these could be contracts (like the token reg) or local (like a list of smart wallets owned by the user). If the recipient is 'recognised' then we can figure out what the transaction is doing and display that underneath. MVP is recognising a token transfer.

Completed -

[x] pull in signer, get operational as part of structure
[x] align styling with the overall theme
[x] sender, recipient (named) and amount of eth should always be displayed
[x] re-use main components such as Container to get a consistent L&F
[x] split pending & finished into 2 Containers, pending first
[x] order by latest (greatest id) on-top
[x] offline status never recovers back into online status how it would work as certain dapp functions will need multiple transactions sending)
[x] remove the toastr and replace it with the error handler
[x] on unlock errors, since toastr removal, submit button state doesn't recover

Split -

~~throw out web3 api, bring in our api~~
~~password hint to be displayed (if available)~~ https://github.com/ethcore/parity/issues/2150
~~keep track of attempts, cool-down after 3~~ https://github.com/ethcore/parity/issues/2150

...

openethereum / parity-ethereum