Help! Warning! Error encountered during contract execution [Reverted]

[Jormoar]

Hi everybody. I have a big problem. I made a SLP transaction from the Ronin Bridge (in Axie Infinity) to my Binance wallet and it gave me an error: Warning! Error encountered during contract execution [Reverted].
The SLP has disappeared from Ronin wallet.

The transaction is this: https://etherscan.io/tx/0xb41c3e3ca3cf96712675fadf99b4a260a760be507cc8fbb1a6b744538bfa5481


I have searched a lot and have not found a solution.
Could someone tell me what I can do?

Thank you very much for your attention and excuse my English.

[amishmanish]

A reverted transaction should ideally be appearing back into your wallet. This seems to be a case of you using the platform wallet of some sort where you don't, have the private key. So this would appear in your platform wallet after some time.

Its a bridge and I believe these things are generally custodial in nature on Ethereum. There shouldn't be a problem and contacting the support with this failed transaction would probably solve your problem.

[Jormoar]

A reverted transaction should ideally be appearing back into your wallet. This seems to be a case of you using the platform wallet of some sort where you don't, have the private key. So this would appear in your platform wallet after some time.

Its a bridge and I believe these things are generally custodial in nature on Ethereum. There shouldn't be a problem and contacting the support with this failed transaction would probably solve your problem.

Thank you so much for your answer.
You mean I must contact the Ronin wallet support?

[noorman0]

Just found people who had the same problem recently in the metamask community. There is an answer that might work.

i found the solution, must remove the ronin extension then put it back then relog in that way your new ronin will reflect the slp in your axie account wish it could help slight

Note: I've never used a roninbridge. Make any necessary backups including seeds, passwords, privkeys, or whatever before unisntalling the extension.
DWYOR and good luck.

[Jawhead999]

You mean I must contact the Ronin wallet support?

Yes.

It's either the contract is wrong or you using very low gas fee and can't be proceed, IMO your transaction is using low gas fee (10 Gwei) while etherscan was recommend to use around 22 Gwei [1] Try to send with higher fees.

Your old transaction will be revert/comeback but you will loss the fee.
[1] https://etherscan.io/gastracker

[Jormoar]

Just found people who had the same problem recently in the metamask community. There is an answer that might work.

i found the solution, must remove the ronin extension then put it back then relog in that way your new ronin will reflect the slp in your axie account wish it could help slight

Note: I've never used a roninbridge. Make any necessary backups including seeds, passwords, privkeys, or whatever before unisntalling the extension.
DWYOR and good luck.

Thank you very much, but I,ve already try. I found the same entry when I searched info. It didn't work for me.

[Jormoar]

You mean I must contact the Ronin wallet support?

Yes.

It's either the contract is wrong or you using very low gas fee and can't be proceed, IMO your transaction is using low gas fee (10 Gwei) while etherscan was recommend to use around 22 Gwei [1] Try to send with higher fees.

Your old transaction will be revert/comeback but you will loss the fee.
[1] https://etherscan.io/gastracker

You meam to make another transaction? My main problem is that my funds are gone.

Thanks for your time.

[livingfree]

Mind you that Ronin bridge transfer to an Ethereum address when you withdraw requires a higher fee, literally higher than ETH suggested fee. That's how the Sky Mavis earns and if you haven't paid the suggested fee coming from them when you withdraw and you've modified it into a cheaper amount.

This error is likely to result or your withdrawal is going to be stuck. That's what happened to me.

[Jormoar]

This issue has been fixed. Actually, I don't know how. The SLP was in Binance's wallet for hours. When I saw the error, I looked in my Ronin wallet and there was nothing. I couldn't imagine that the transaction had gone through. It took about 45 minutes.
Thank you all very much for your kindness.
All the best.

[livingfree]

This issue has been fixed. Actually, I don't know how. The SLP was in Binance's wallet for hours. When I saw the error, I looked in my Ronin wallet and there was nothing. I couldn't imagine that the transaction had gone through. It took about 45 minutes.
Thank you all very much for your kindness.
All the best.

Good to know that despite the error, it got pushed through.

If the issue has been fixed and you're already good as it's already reflected in your Binance wallet then you can finally close this thread as there's no need to go more with the discussion.

I hope that people that will encounter the same problem might find this thread helpful and just wait for the reflection of their SLPs on their wallets.

[Jormoar]

This issue has been fixed. Actually, I don't know how. The SLP was in Binance's wallet for hours. When I saw the error, I looked in my Ronin wallet and there was nothing. I couldn't imagine that the transaction had gone through. It took about 45 minutes.
Thank you all very much for your kindness.
All the best.

Good to know that despite the error, it got pushed through.

If the issue has been fixed and you're already good as it's already reflected in your Binance wallet then you can finally close this thread as there's no need to go more with the discussion.

I hope that people that will encounter the same problem might find this thread helpful and just wait for the reflection of their SLPs on their wallets.

Should I close this thread? Can you tell me how to do it?

[Bttzed03]

~
Should I close this thread? Can you tell me how to do it?

Yes you should since your issue has been solved.

You can see the option to lock topic at the bottom left (facing your screen).

[Jormoar]

~
Should I close this thread? Can you tell me how to do it?

Yes you should since your issue has been solved.

You can see the option to lock topic at the bottom left (facing your screen).

Ok! Thank you all.