Unable to update when a transaction fails and is re-sent

[emansipater]

I've come across a minor issue. When I first went to deposit my validator, I took too long getting into my hardware wallet and timed out, so the wallet and launchpad marked the transaction as failed. Best practice at this point (in my view) is to retry the same transaction from within my wallet since it handles the nonces and will re-send with the same nonce rather than creating an opportunity to accidentally double up, as client pages sometimes do.

So I did that, but then the launchpad was unable to detect that I had re-sent the transaction, so it just left it marked as failed even after the transaction confirmed. This definitely creates a danger for double-sending via the "try again" button.

[delbonis]

I think this might also happen if the transaction takes longer than expected to confirm as well. When going through the steps it shows the warning sign and that there's already a deposit submitted and refuses to allow proceeding to the "congratulations" page to show that it worked properly.

Not sure if this happens on mainnet as well, I only tested it on medalla.

[emansipater]

My example was on mainnet, but I expect the results are similar.

[stoven91]

This might be comically unfortunate, but I'm also having this problem. Not 100% on how to "retry the same transaction from within my wallet," so I might just generate new seed phrases and repeat the process, just to be safe.

The weird thing is that the "try again" link in the launchpad is broken. Figured I'd bring this to someone's attention. Is this intentional to stop people from people potential accidentally dangerous double-sends that would only create one validator?

I guess the important question is: does anything important happen on the congratulations page?