Bitcoin Forum
May 05, 2024, 01:15:30 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: mining.notify/Generation transaction parts questions  (Read 150 times)
Volvagia (OP)
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
September 29, 2019, 08:28:53 PM
 #1

Hello. Hard to decide for a Board/Subboard, hope I'm right. Smiley
I stuck on understanding the whole process of mining, I'm confused about the "mining.notify" command for pool clients. I think, I miss out something elementary.

Job ID and prev. block hash params seems to be simple but I have no idea and found not even in the BIP a clear description of "Generation transaction (Part...)".
The Generation alias the Coinbase is the first transaction of a block and contains just a single output, to act like an adapter to have an output for the block reward, if I'm right.
When I subscript to a pool, the data sent doesn't seem to be a real transaction:

Code:
01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4503181c09fabe6d6d5a8f50564fcd22bfb59d80e7b25b4dc6c5b299886315be62daf7ac2b06bfeecd0100000000000000

01 00 00 00: Transaction version 1
01 00: Flag - Transaction contains witness data
00: Varint 0, no inputs
(No input transactions)
00: Varint 0, no outputs Huh
(No output transactions)
(No witnesses, since there are no inputs)

I assume ffffffff is the lock_time, so I don't understand where the zeros between come from, why there are still the data 4503...eecd after lock_time, which is the last field of a transaction and I don't figured out, which condition splits the both transaction parts.


Thank you Smiley
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!