|
Title: Is this a legit bug in Blockchain.info Block #1 ? (and other explorer ?) Post by: theochino on March 04, 2017, 08:59:50 AM Is it me or am I going crazy.
To prepare for a lawsuit against New York Department on Financial Services on 3/17/2017 (http://www.article78againstNYDFS.com) I need to understand the blockchain technology down to the core. After two years of on and off writen my own parser just came to the understanding that the Coinbase Input Address is "simply" (I write simply the Public key ECDSA and I spent hours trying to figure out OPScripting .....) the public key. When I manually compute the ECDSA key of the genesis block I get this address: 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa Then when I manually compute the one for the next block (block #2) I get: 12c6DSiU4Rq3P4ZxziKxzrL5LmMBrzjrJX (which is reported as Block #1 in https://blockchain.info or https://blockexplorer.com) Why is the Genesis address reported by itself and not in block #1 ? https://blockchain.info/tx/4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b The first thing someone does when learning is to read the first byte on block0000.dat and the first byte is block #1. Regards, Theo Chino @TheoBitcoin http://www.article78againstNYDFS.com Title: Re: Is this a legit bug in Blockchain.info Block #1 ? (and other explorer ?) Post by: amaclin on March 04, 2017, 01:15:35 PM genesis block is #0
Title: Re: Is this a legit bug in Blockchain.info Block #1 ? (and other explorer ?) Post by: theochino on March 04, 2017, 02:58:54 PM genesis block is #0 The index of what you call the Genesis block doesn't change. The first output from the first coinbase is to 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa so why blockchain is reporting the address from the next block (Two hundred something bytes later.) http://article78againstnydfs.com/GenesisBlock.jpg Title: Re: Is this a legit bug in Blockchain.info Block #1 ? (and other explorer ?) Post by: amaclin on March 04, 2017, 03:17:58 PM The first thing someone does when learning is to read the first byte on block0000.dat and the first byte is block #1. Who told you this?The order of blocks in blk-files is undefined. Title: Re: Is this a legit bug in Blockchain.info Block #1 ? (and other explorer ?) Post by: theochino on March 04, 2017, 03:33:34 PM Who told you this? The order of blocks in blk-files is undefined. The hash of the previous block referenced in the first block. Byte #12 to 44 .... Only zeros. Title: Re: Is this a legit bug in Blockchain.info Block #1 ? (and other explorer ?) Post by: DannyHamilton on March 04, 2017, 03:44:40 PM - snip- The first output from the first coinbase is to 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa so why blockchain is reporting the address from the next block (Two hundred something bytes later.) - snip- You are mistaken. Blockchain.info reports the address 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa as the first output from the first coinbase: https://blockchain.info/block/000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f https://i.imgur.com/StKNBOr.png Title: Re: Is this a legit bug in Blockchain.info Block #1 ? (and other explorer ?) Post by: theochino on March 04, 2017, 03:49:18 PM Mea culpa, I am the idiot !!!!
<--- Says Newbie over here. :P Had I asked that questions two years ago, I would have saved a lot of time. Never occurred to me to put #0 as the first block. Now I can move forward to the next block. ;D |
