Bitcoin Forum
May 27, 2024, 04:40:53 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: I didn't get something  (Read 229 times)
9017.exe (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 6


View Profile
December 07, 2022, 04:50:41 PM
 #21

Great ! Thank you everyone. Everything is "clear" now  Grin
o_e_l_e_o
In memoriam
Legendary
*
Offline Offline

Activity: 2268
Merit: 18565


View Profile
December 07, 2022, 09:06:02 PM
Merited by LoyceV (4), BlackHatCoiner (4), ABCbits (3), hosseinimr93 (2), DdmrDdmr (1), FatFork (1)
 #22

I can't find other examples, I thought they exist.
They do not.

Every block must have exactly one coinbase transaction, and that coinbase transaction must be the first transaction in the block. The coinbase transaction may collect the block subsidy and the block fees, or any portion thereof, but it doesn't have to. The coinbase transaction must also contain the block height as the first entry in its scriptsig (4 bytes) with a further 96 bytes of arbitrary data, which is how pools tag blocks as being found by them.

Blockchair makes it look like an OP_RETURN transaction.
It's supposed to be, but it isn't, because the miner clearly messed up. If you pull the hex script from that output, you'll get the following:
Code:
52534b424c4f434b3addbf517adf8ffd4bca7751505b39c9013a0d1fd479fc4e901b39dd57b347c624

The start of that - 52534b424c4f434b - decodes to RSKBLOCK. If you look at any other recent block which has an RSKBLOCK OP_RETURN output, you'll see the same string in its coinbase transaction. However, in this case, the miner has neglected to include the necessary OP_RETURN bytes at the start of the script (0x6a29).
Pages: « 1 [2]  All
  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!