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
Is your feature request related to a problem? Please describe.
When a user sends native L1 assets (NFT, native tokens) on the EVM through the magic contract an additional transaction is created from the 0x0 address. The amount of gas used by the is put on the transaction of the 0x0 address instead of the user's transaction. This means that the transaction receipt returns that gasUsed is 0. This is misleading.
Describe the solution you'd like
Instead of putting gasUsed on the transaction from the 0x0 address, we would like to have it on the transaction from the orginal caller.
Describe alternatives you've considered
Use the blocks cumulativeGasUsed property, but this can be wrong if multiple transactions are included in a block.
Is your feature request related to a problem? Please describe.
When a user sends native L1 assets (NFT, native tokens) on the EVM through the magic contract an additional transaction is created from the 0x0 address. The amount of gas used by the is put on the transaction of the 0x0 address instead of the user's transaction. This means that the transaction receipt returns that
gasUsed
is 0. This is misleading.Describe the solution you'd like
Instead of putting gasUsed on the transaction from the 0x0 address, we would like to have it on the transaction from the orginal caller.
Describe alternatives you've considered
Use the blocks
cumulativeGasUsed
property, but this can be wrong if multiple transactions are included in a block.Additional context
Sending a wrapped L1 NFT on the EVM network.
Block: https://explorer.evm.testnet.shimmer.network/block/39449?tab=txs
Tx from 0x0 address (left) and Tx from user (right)
The text was updated successfully, but these errors were encountered: