-
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
senderAddress should automatically convert hex format to base58 #2
Comments
@hayeah hey man, did you fix the bug? Can it deal with overloaded methods now? |
the qtumd core team is adding hex address support, I am waiting on that. what do you mean by overloaded methods? |
Suppose I have two methods share the same name in my abi, i.e. Lines 195 to 204 in dea61dd
|
And another issue, I don't know why some events are decoded to |
can you give me the Solidity example where the events are decoded to null? I'll debug it. I've created an issue for this problem: #4 |
@pplam method overloading support is added. see: https://qtumproject.github.io/qtumjs-doc/#method-overloading i'll close this issue in favour of #4 |
actually this problem is not solved |
perhaps a stop-gap solution is to detect hex address and implicitly make an RPC call to convert it to base58 format |
The qtumd RPC does not support senderAddress in hexadecimal format. This makes the qtumjs API rather awkward when senderAddress is involved.
Should detect hex address and convert that automatically to base58 format.
The text was updated successfully, but these errors were encountered: