We’re rewarding the question askers & reputations are being recalculated! Read more.

Hot answers tagged

2

If you're using Web3 v1 then you can use web3.eth.getTransactionReceipt(tx). It returns logs property as a part of a result. You can categorize events by looking at their topics property. Sample getTransactionReceipt result: { "transactionHash": "0x7e2e90d913246933b30049c568d9a9768eca5be6fed331656458c2a479f30908", "transactionIndex": 0, "...


1

Using remix.ethereum.org, here is an example that can help. The input, which is the same as calldata, is 0x29ae811475944220b52381f169021a7c3f2947dfd0d2b1fb95e6cd92358e0a7997c8a9a1000000000000000000000000000000000000000000000000000000000000000f. (This is calling file( 0x75944220b52381f169021a7c3f2947dfd0d2b1fb95e6cd92358e0a7997c8a9a1, 15)) calldataload is ...


1

When calculating the signature of an event that uses structs, each struct is represented as a tuple of the types of the variables it contains. To create the tuple for your question, we need to look at the source of SoloMargin. Based on the source published to Etherscan, I extracted the code needed to create the event: pragma solidity 0.5.7; pragma ...


1

This event's signature is: 0x2bad8bc95088af2c247b30fa2b2e6a0886f88625e0945cd3051008e0e270198f This is keccak256 hash of the following string: LogDeposit(address,uint256,uint256,((bool,uint256),(bool,uint128)),address)


1

When logged event is stored in transaction receipt, the type of event is stored as a keccak256 hash of event signature. The signature is a string looking like this: Transfer(address,address,uint256). You may query hashes of all event signatures, but in general there is no way to decode these hashes into plain text signatures. All the signature hashes may be ...


Only top voted, non community-wiki answers of a minimum length are eligible