-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
some events are decoded as null #4
Comments
The case is, I have two contracts, i.e. |
hmmmm... ok. I don't really have a nice API in mind to handle this case automatically. Maybe you could suggest one. To fix this problem manually, you can consider merging ContractA and ContractB's ABI arrays:
you could also add only ContractB's events:
|
@pplam hi, this issue is resolved in version 1.7.1 A new API is created so that Contract instances are configured with a log decoder that can parse all known event types. For details, see: https://qtumproject.github.io/qtumjs-doc/#contract This version introduced minor backward incompatible changes with 1.6.*. The only user-visible change should be that the hexadecimal output are now all consistently without the |
Good job, congratulate! |
see: #2 (comment)
The text was updated successfully, but these errors were encountered: