Add test transaction ability

[pmespresso]

It's best practice before sending any transactions to send a test transaction of a minimum unit of whatever token first to confirm the user entered the correct destination address.

We could make this easier (and less nerve-wracking) by adding a button "Send Test Txn" to an unrecognized (not in Address Book) address. #344

I was thinking the user can verify the txn went through as expected then it'd "qualify" to be added to the Address Book.

By codifying this process we'd minimize the risk of human error and also streamline it a bit.

(needs #344)

[pmespresso]

As far as UI, it'd be most intuitive to have a Min toggle next to the Max toggle.

What it would do in the background would be:

set a flag on the recipient address somewhere - likely in localstorage - and pop up a warning in menu about confirming that address (or set of addresses) that those txn's went through as expected.

When user confirms, the address gets added to Address Book

If user says it failed, then remove the warning but don't add the address to Address Book.

[Tbaut]

I like the idea to have a test transaction ability, but I think adding a "min" button that has a very different behaviour than the "max" would be very confusing.

set a flag on the recipient address somewhere - likely in localstorage - and pop up a warning in menu about confirming that address (or set of addresses) that those txn's went through as expected.

I couldn't follow you :)

It could be great in combination with an address book (https://github.com/paritytech/fether/issues/344) where you could have a button to "send a test transaction [to the selected address book account]" and then a flow would let you chose from which account you send it, unlock this account and let you know when it's done. Is that what you proposed?