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
Steps to reproduce:
Dump the private key: kevacoin-cli dumpprivkey <V_pub_key>
kevacoin-cli dumpprivkey <V_pub_key>
Sign a message with private key: `kevacoin-cli signmessagewithprivkey M_priv_key "test_message"
Verify the message: kevacoin-cli verifymessage <V_pub_key> <signed_msg> test_message
kevacoin-cli verifymessage <V_pub_key> <signed_msg> test_message
Step 3 returns an error message:
error code: -3 error message: Address does not refer to key
The text was updated successfully, but these errors were encountered:
This is a known issue in Bitcoin-core: bitcoin#10542
Kevacoin by default uses SegWit address, but SegWit address does not support message signing/verification yet.
There is a PR to solve this issue, but it has not been merged into Bitcoin-core yet: bitcoin#16440
Sorry, something went wrong.
No branches or pull requests
Steps to reproduce:
Dump the private key:
kevacoin-cli dumpprivkey <V_pub_key>
Sign a message with private key:
`kevacoin-cli signmessagewithprivkey M_priv_key "test_message"
Verify the message:
kevacoin-cli verifymessage <V_pub_key> <signed_msg> test_message
Step 3 returns an error message:
The text was updated successfully, but these errors were encountered: