I am sending this json to bitcoind server working in regtest mode:
{"jsonrpc": 2.0,
"id": "cumainer",
"methodology": "submitblock",
"params": ["000000200f9188f13cb7b2c71f2a335e3a4fc328bf5beb436012afca590b1a11466e2206a2db7dd515bcb1592ad65c2d5963e217120876d742f7b10d77d1a481017f4fb1ffff7f20a228fa6462a200000101000000010000000000000000000000000000000000000000000000000000000000000000ffffffff00000000010000000000000001000000000000000000000000a228fa64"]
}
First 80 bytes are my block header, 1 that means the variety of transactions and my coinbase transaction in uncooked hex.
My regtest server is contemporary and it has just one block.
For some purpose I at all times get “high-hash” end result from the server.
Nonetheless if I take first 80 bytes (block header measurement) of my “params” string and double hash it I get a string with few zeros on the beggining. getblocktemplate request provides me the primary issue (0x207fffff = the best one) and I am sending it again in little endian order as acknowledged on submitblock reference (I really tried sending in big-endian too).
So the double sha256 hash of my block header is clearly smaller than the goal.
What does this error imply then ? What I’m doing mistaken ? Is it the byte order? Possibly the issue is definitely with the merkle root hash ?