Safe transaction handling
Feature Description
Transactions should be saved in state, so that when the user wants to trigger a new tx, we can warn him that his previous tx has not yet been mined.
While a transaction is being mined, we should display a spinner or loading item, indicating that:
- it has been sent
- it is being confirmed
- it has failed
[update:] This could look like the notifications fired by remix.org.
After, clicking on a button that triggers a tx, a yellowish-window pops up that displays sent/confirmed/failed with a link to etherscan. The window has a small 'x' on the top to close it.
Motivation and Context
As we want to trigger transactions in a bunch of places, it'd make sense to have a standardized way of dealing with them.
Edited by dju