Problem : Handle transactions time-out during broadcast about chain-desktop-wallet HOT 4 CLOSED

From the previous study there seems to be no way one can adjust the timeout of Tendermint broadcast. So we may want to do our own polling of transaction status to extend the timeout.

from chain-desktop-wallet.

The tricky part with this is we can't poll transaction state later because we don't even get a transaction hash that we could use later to fetch whether the transaction state.

I remember I worked on cosmos integration for the Trust Wallet back at Binance, and there was a broadcast async API that I ended up using since it didn't have time out issues. Not sure if that API is supported yet by cro chain.

So we'd broadcast transactions and consider them as pending and then later we'd poll the state via the transaction hash to check if they finally got confirmed in the block.

from chain-desktop-wallet.

The approach I'm planning to implement is to let the user know that the transaction timed out when it occurs and inform them that it will be included in subsequent blocks.

When we already have the chain index data in place, we can always fetch the latest transactions from that endpoint and it would show up

from chain-desktop-wallet.

Fixed here #111

from chain-desktop-wallet.