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
During execution, these logs are built up when LOG opcodes (LOG0, LOG1, ...) are executed.
Logs are incldued as part of the tx receipt in the block and stored off-chain but
indexed and retrievable by EVM nodes and APIs via "eth_getLogs" and
"eth_getTransactionReceipt".
Problem / Abstract
Precompile contracts are a bit opaque in that they can execute loads of
operations across Nibiru modules without revealing the underlying behavior in EVM
explorers. It is however possible to emit events like normal smart contracts
would using the "go-ethereum/accounts/abi" types directly.
The goal of this ticket is to emit useful ABCI events on the EVM side during
state-changing precompiled contract calls.
The text was updated successfully, but these errors were encountered:
Emitting EVM Events
Ethereum logs are emitted at the end of an EVM transaction by reading the logs
stored in the
StateDB
during transaction execution.This happens in the
applyTransaction
function from"go-ethereum/core/state_processor.go":
During execution, these logs are built up when
LOG
opcodes (LOG0
,LOG1
, ...) are executed.Logs are incldued as part of the tx receipt in the block and stored off-chain but
indexed and retrievable by EVM nodes and APIs via "eth_getLogs" and
"eth_getTransactionReceipt".
Problem / Abstract
Precompile contracts are a bit opaque in that they can execute loads of
operations across Nibiru modules without revealing the underlying behavior in EVM
explorers. It is however possible to emit events like normal smart contracts
would using the "go-ethereum/accounts/abi" types directly.
The goal of this ticket is to emit useful ABCI events on the EVM side during
state-changing precompiled contract calls.
The text was updated successfully, but these errors were encountered: