Re: Generate coinbase from to send to miner (ckpool source code question)
⭐ Merited by ETFbitcoin (1)
You are awesome. Thanks for taking time and explain each parts.
I highly suggest that you read Bitcoin.org's documentation on the raw transaction format as that is basically what you are being given by the stratum protocol. All it is giving you is the entire coinbase transaction with some parts missing that the miner needs to fill out. Those are the nonce and extra nonce which are part of the coinbase.Coinbase1
----------------
Header | 01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff
This is not a header. This consists of 4 different fields. The first 4 bytes are the transaction version number, the next byte is the number of inputs. The next 32 bytes are the transaction id of the transaction the input spends from. The 4 bytes after that are the index of the output that is being spent. In a coinbase transaction, the previous txid must be all 0's, and the output index must be 0xffffffff.----------------
Header | 01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff
Length | 35 (<= this is 53 decimal length counts till signature part 
)
Yes, that is the length. It is the length of the scriptSig, which in a coinbase transaction, is known as the coinbase. )Height | 0371bb07
The first byte is a length specifier. The next 3 bytes are the block height. This is pursuant to BIP 34 | ffffffff (<= is this separator between tx in and tx out ?)
No, this is not a separator. It is the sequence number. Every input has a 4 byte sequence number.end | 00000000
That's the transaction lock time, not "end".