We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Shouldn't this be an array since transaction output can be spent by multiple addresses in the case of multi-sig?
bchd/bchrpc/bchrpc.proto
Line 351 in 9b70419
The text was updated successfully, but these errors were encountered:
Good question. The ExtractPkScriptAddrs does return a slice of pubkeyaddresses for a bare multisig, but does anyone use this?
ExtractPkScriptAddrs
It also seems to not convey much without the required number of signatures parameter along with it.
I'm also not sure this counts as an "address" as we really don't have an address format for bare multisig.
Sorry, something went wrong.
Perhaps we should add another field to the response for this case? That way the contract for existing apps doesn't change?
I'd say addresses should be added and address can be kept as it is for backward compatibility.
addresses
address
No branches or pull requests
Shouldn't this be an array since transaction output can be spent by multiple addresses in the case of multi-sig?
bchd/bchrpc/bchrpc.proto
Line 351 in 9b70419
The text was updated successfully, but these errors were encountered: