<p>I am trying to understand how bitcoin works internally in solo minning, and i am a little confused with the submitblock method:</p>
<pre><code>
version:     The current version
prev block:  The previous block
merkle root: The merkle root (Double SHA of the coinbase transaction)
timestamp:   The middle time
bits:        The difficulty
nonce        The valid nonce
num txs:     Number of the transaction (01 if it contains only coinbase transaction)
tx1:         The coinbase transaction (Built from the createrawtransaction method)

</code></pre>
<p>Is that correct?</p>
<p>Thank you for your help</p>

CC BY-SA 4.0
2020-07-07T04:20:50.653Z
I want add a fix at your post, the Merkle root is built with all transactions inside the block, so in other words the merkle tree is not a normal binary tree but it is built from the left. The merkle tree root is the result of some process that include all transactions
vincenzopalazzo
CC BY-SA 4.0
2020-07-07T16:00:40.923Z
@vincenzopalazzo Yes, but if the block contains only the coinbase transaction, the merkle root will be only the double sha256 of the coinbase transaction (Little endian)? Or i am wrong?
Hamita
<bitcoin-core><bitcoin-core-development><solo-mining>
How data should be build in submitblock
Hamita
# How data should be build in submitblock

(Asked by: username_0 on 2020-07-06)

I am trying to understand how bitcoin works internally in solo minning, and i am a little confused with the submitblock method:

version:     The current version
prev block:  The previous block
merkle root: The merkle root (Double SHA of the coinbase transaction)
timestamp:   The middle time
bits:        The difficulty
nonce        The valid nonce
num txs:     Number of the transaction (01 if it contains only coinbase transaction)
tx1:         The coinbase transaction (Built from the createrawtransaction method)


Is that correct?
Thank you for your help

**Tags:** bitcoin-core, bitcoin-core-development, solo-mining

> **Comments:**
> **username_1**: I want add a fix at your post, the Merkle root is built with all transactions inside the block, so in other words the merkle tree is not a normal binary tree but it is built from the left. The merkle tree root is the result of some process that include all transactions  
> **username_0**: @username_1 Yes, but if the block contains only the coinbase transaction, the merkle root will be only the double sha256 of the coinbase transaction (Little endian)? Or i am wrong?  

---

## 0 answers

