-
Notifications
You must be signed in to change notification settings - Fork 811
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
regtest: submitblock #1161
Comments
can you elaborate the issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I've tried to add a new block through the api
curl -XPOST --data '{ "method": "submitblock", "params": ["20000000e8c2c3aaaa31056e81e95467ffbd9ec032a103cdcaac52f3dd5b54876622c4eb99cc6825b4829f75f703f8e96cabdc0082e182df7d295180883fdc1ea47ef5cf64a716da207fffff00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000"] }' http://127.0.0.1:48332/
,I got message error in the log
[D:2023-07-06T19:32:42Z] (node-rpc) Handling RPC call: submitblock.
[I:2023-07-06T19:32:42Z] (node-rpc) Handling submitted block: 6a1cbe23562817b7dd5c66e8bbc7ea17a59171fa3eb59bef548b33f6b6d72c0f.
[W:2023-07-06T19:32:42Z] (node-rpc) RPC block rejected: 6a1cbe23562817b7dd5c66e8bbc7ea17a59171fa3eb59bef548b33f6b6d72c0f (high-hash).
and json response
{"result":"rejected: high-hash","error":null,"id":null}
But, when I checking the block header manually - it looks good
What is that mean? Why are the hashes in the logs and in the tool different?
The text was updated successfully, but these errors were encountered: