-
Notifications
You must be signed in to change notification settings - Fork 0
Transfer event #13
Comments
it isn't really clear what the issue is and what work has been done here. by clicking around and reading, i see you made a request to web3 to return transfer events for the fallback case. my open question to you is how does this impact us. eg, here #11 (comment) just a short comment explaining may be enough. |
@carchrae I think this issue should be opened and wait until somebody respond on web3.js or implement stuff in web3.js. The problem is: we can execute mint in 2 ways: explicit (tokenContract.methods.mint.send()) and implicit (send plain transfer to the tokenContract and call mint by falling into fallback function). From what I see, there is no way we can handle raised events if we use the second way. It basically means that: if we want to handle events raised by minting tokens, we should use explicit approach. |
If a contract contains payable fallback function, there could be events — for example, "token minted".
However, the current implementation of the transfer does not allow to handle events.
The text was updated successfully, but these errors were encountered: