How to handle the transaction in a good UX? #2193
Unanswered
Albert-Gao
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Depending on your application, you may want to track the transaction, if you have a transaction that depends on another. With EIP-1559 on mainnet, as long as reasonable values are chosen for the fee (defaults are populated), transactions generally get in within the next block. I know it's not a great answer, but it really depends. :s |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am asking this because after sending the crypto, my current way is to do a
await transaction.wait()
, after it returns, I will go to the result outcome page, I guess iftransaction.wait()
resolves, that means the transaction is mined already on chain.So here is my question, currently on
Kovan
, it just takes like seconds, like 10secs at most to resolve. What about themainnet
? is this approach good enough to be used on mainnet as well? If not, i might need to log transaction hash andprovider.getTransaction()
to self-check the mine. But that sounds a similar approach totransaction.wait()
So, what is the proper way to handle the waiting period after sending the transaction? Is just
transaction.wait()
enough? ThanksBeta Was this translation helpful? Give feedback.
All reactions