Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

New answers tagged


Transfer is an event of ERC-20 token having declaration as: event Transfer(address indexed from, address indexed to, uint tokens); You need to fire Transfer event by passing these three parameteres also.


You are using event log overloading and arrays in the event log. From superficial testing, I found it works as expected if you drop either of those features. If you comment out the logs that aren't actually used in this test then things improve. pragma solidity >=0.5.6; contract EventTest { //event marketCreated(address[] virtualShareAddresses, ...


It is server-based and topologically similar to a caching strategy. A purist might disagree, but an argument can be made that it is perfectly fine to use any sort of caching strategy (e.g. etherscan) subject to a few conditions. Users should be able to verify results independently, if they want to. This implies transparency. The cache should emit ...


throw rolls back the whole transaction, so it not only prevents event2 from being emitted, but also rolls back emission of event1. The final effect will be as if no events were logged at all, so you will see neither event1 nor event2 in transaction.


The problem is that there are different type of Transfer events which share the same signature. The ERC20 transfer event is defined as: Transfer(address indexed _from, address indexed _to, uint256 _value) And the ERC721 (the standard for non-fungible/unique assets on the Ethereum blockchain) defines the transfer event as: Transfer(address indexed _from, ...

Top 50 recent answers are included