Describe the bug:
Accepting a transfer doesn't remove the "Incoming point" message, so the user might think that the transfer was not successful, click multiple times, which will send extra L2 txs that will later fail (and show up as such in the tx history). Note here that one of them will go through, and the others will fail—nonce here is probably reused—so this is only confusing UX/UI rather than an actual bug.
To reproduce:
Steps to reproduce the behavior:
Transfer a planet to an ETH address
Log in with that ETH address
Click on Accept multiple times
Click on History to see the Tx failures
Expected behavior:
After clicking on Accept, the "Incoming point" message should go away, after checking with the Roller that the TX is now in pending
Screenshot or console log:
Ethereum network:
Ropsten
Desktop (please complete the following information):
Describe the bug: Accepting a transfer doesn't remove the "Incoming point" message, so the user might think that the transfer was not successful, click multiple times, which will send extra L2 txs that will later fail (and show up as such in the tx history). Note here that one of them will go through, and the others will fail—nonce here is probably reused—so this is only confusing UX/UI rather than an actual bug.
To reproduce: Steps to reproduce the behavior:
Expected behavior: After clicking on Accept, the "Incoming point" message should go away, after checking with the Roller that the TX is now in pending
Screenshot or console log:
Ethereum network: Ropsten
Desktop (please complete the following information):
Login method: Master Ticket