-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
maker failed PLG20 swap saying that tx was not found on RPC node #1630
Comments
We use Should be easy, so it looks like a good test task. |
i had a very similar issue and it sounds like the above solution will solve this problem too
just that the tx https://polygonscan.com/tx/0x31c91001eb35c9f80e1f56ab416c4425fea87b8d59663f27c5e140361f29c6a9 is nowhere to be found |
Although this is a good issue for a test task, it's better to fix this bug as soon as possible since it leads to failed swaps. Will work on it this week. |
@cipig Did you encounter these errors again? If not, I guess this issue can be closed. |
saw it once in the last time https://dexapi.cipig.net/public/error.php?uuid=f691a5f1-e639-47c2-8ec5-cd7bdb224d17 |
maker failed a PLG20 swap because tx sent by taker was not found on the RPC node
the relevant part in maker's swap json:
the console on maker showed this while it failed the swap:
the tx in question is this one: https://polygonscan.com/tx/0x74e4e262f31906d64b8733245062ace84250638100742e42d303214a3721d92c
it was mined just fine
maker was using https://polygon-rpc.com RPC node while taker was using the ones defined in https://github.com/KomodoPlatform/coins/blob/master/ethereum/MATIC, which are more
it's a bit strange that maker said that he found the tx (
[OCEAN-PLG20] Waiting for confirmations… Confirmed
) but failed the swapboth maker and taker were using the same mm2 from dev branch: http://195.201.0.6/dev/mm2-7201146b3-Linux-CI.zip
what can be the cause? sync issues between the different RPC nodes that taker was using? if so, can we make a change so that mm2 tries a second time couple seconds later?
The text was updated successfully, but these errors were encountered: