Open bb111189 opened 1 year ago
The above txn from a content extension (that we are working on) that I suspect was sending double txn. However, on a deeper investigation, there is more than that
For example, I use metamask to send some native token and it appear as double transaction on blockscout https://devnet-explorer.altlayer.io/tx/0xf9ac7fa5219b35039b9a08db870917495d5c5b47ae6da44cf37e9148cd31d2b8 https://devnet-explorer.altlayer.io/tx/0x1081da6737bb34073737e1eb69a5a1ca835f84499331f447c9cf419b57191cd8
Note: tx is different but the payload is the same.
Only 3 txns was sent from metamask.
Note:
Describe your issue here.
These two transactions are submitted from the same address and have same nonce. https://devnet-explorer.altlayer.io/tx/0x1e9c2741d53d301ea1a0ff22523b85375ddde2935c858c56436b70e5b17a8f2d https://devnet-explorer.altlayer.io/tx/0xba9d5cb1f6dbb231c5515c58f8c5563b56e63d0036dbef9f633ba0abda26a959
One txn is accepted, while the second txn will be dropped as the nonce has been used. However, on the explorer, it is showing
This transaction is pending confirmation.
Ref: https://devnet-explorer.altlayer.io/tx/0x1e9c2741d53d301ea1a0ff22523b85375ddde2935c858c56436b70e5b17a8f2d
Environment
elixir -version
):Steps to reproduce
Tell us how to reproduce this issue. ❤️ if you can push up a branch to your fork with a regression test we can run to reproduce locally.
Expected behaviour
Tell us what should happen.
Actual behaviour
Tell us what happens instead.