You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've implemented a workaround to revert transactions in case the precompile is called with 21000 gas but the caller (ERC20) contract was not whitelisted. In the above case, however, ZUSDT was whitelisted in the proto-mainnet config file, so the interop call should have worked with 21000 gas: 0x2274005778063684fbB1BfA96a2b725dC37D75f9
The precompile failed, the relevant section of the trace says:
Here's an example of a transaction that involves an ERC20 -> ZRC2 interop call. The transaction succeeded but the ZRC2 transfer did not happen: https://explorer.zq2-protomainnet.zilliqa.com/tx/0xa86cfe1c38d6744eda04a62eac3119b54f562c575f7f1feac395a69e57da927e
The involved ZUSDT (ERC20) contract imported from ZQ1 calls the precompile with 21000 gas: https://github.com/Plunderswap/zrc2proxy/blob/3cefaae8c4e4c47647263a959cebd29183a8f336/contracts/EIP20ZRC2Proxy.sol
We've implemented a workaround to revert transactions in case the precompile is called with 21000 gas but the caller (ERC20) contract was not whitelisted. In the above case, however, ZUSDT was whitelisted in the proto-mainnet config file, so the interop call should have worked with 21000 gas: 0x2274005778063684fbB1BfA96a2b725dC37D75f9
The precompile failed, the relevant section of the trace says:
The text was updated successfully, but these errors were encountered: