CCTX from BNB to ZetaChain fails due to "out of gas"
BNB:
https://bscscan.com/tx/0x215e8c43a335d520aec5af90cfe350c8f0c0e9d1ff7b05fa3e7232ceadd95338
ZetaChain:
https://zetachain.blockscout.com/tx/0x4a5cc0ca37e714c3dbebefb8f5fca7a467833981ad05cb507bb6809e1391213b
Gas usage & limit by txn: 991,172 | 991,172
Isn't the gas limit 2.5M?
https://github.com/zeta-chain/node/blob/33a70df096afc59a6509fe8b64af239261408543/zetaclient/chains/evm/signer/gas.go#L15
It was set to 1.5M in the protocol, but for some reasons with the EVM module, it will be less than that in practice
@lumtis are we planning on increasing the gas limit?
Let's look into it for this coming release
@rohatin-codemelt hey, can you provide an end-to-end example of a cross-chain call-data (decoded) that uses 1M gas on Zeta?
As @skosito confirmed, the out of gas looked to be more of a bug in the protocol to map the tx attribute in the emitted events.
The cctx: https://athens.explorer.zetachain.com/cc/tx/0x64fdacb6e242918c83e8ba503d3bea22631705b197d26819b504332a74b90622
The depositAndCall seems to be failing with the reason execution reverted: ret 0x10bad147
Closing this one as we fixed the issue with the gas limit logging