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
Hi @mgarbs, thanks for sending this. We managed to reproduce the error locally, and verify the error didn't happen on an Ethereum network, e.g., Sepolia. At the moment, the issue seems to boil down to contracts after selfdestruct still have bytecode attached.
We continue investigating the root cause of the issue.
After further investigation, we managed to find the root cause. The issue is how selfdestruct handles deletion within the same transaction. More details can be found in tracking issue hashgraph/hedera-services#14835. We expect to have a fix for this soon.
Description
It appears some events are not emitted for the following tests within Axelargateway:
should allow the operators to burn external tokens
should allow the operators to burn external tokens even if the deposit address has ether
should allow the operators to burn the external token multiple times from the same address
All fail with:
AssertionError: Expected event "Transfer" to be emitted, but it wasn't
Sample Transaction Hashes for Tests:
should allow the operators to burn the external token multiple times from the same address: https://hashscan.io/testnet/transaction/1723125697.573982315
should allow the operators to burn external tokens: https://hashscan.io/testnet/transaction/1723125656.258025003
One of their partners faced similar issues, which was related to
selfdestruct
. Comment for reference: onflow/flow-evm-gateway#404 (comment)Steps to reproduce
Additional context
No response
Hedera network
testnet
Version
v0.52
Operating system
None
The text was updated successfully, but these errors were encountered: