Hex data from the prenet genesis transaction

I was checking out a thread and got curious about what the prenet genesis transaction actually looked like. After some research, I found a few things. I get that the transaction version wasn’t included (just like the block hash was missing the version), and I know how to calculate sha256 for any data. Still, that transaction should hash to 769a5e93fac273fd825da42d39ead975b5d712b2d50953f35a4fdebdec8083e3. I played around with different values for OP_CODESEPARATOR and OP_CHECKSIG, trying 0xab and 0xac, but nothing matched. I even experimented with endianness in both 32-bit and 256-bit formats, but no luck. So far, the only thing I’ve managed to successfully hash is the prenet genesis block. Is that transaction just a memory now, or is there a way to piece together what it looked like back in the prenet days?

This is an interesting question and I took far too long to figure it out. The transaction hex is There are 3 key differences in the prerelease version: 1. The transaction and block versions are not included in the serialization for hashing 2. The nSequence is found in the CTxOut rather than CTxIn 3. OP_CODESEPARATOR is 0xa9 and OP_CHECKSIG is 0xaa The last point was harder to find as the source for script.h is not available. However it can be easily bruteforced.

Does anyone know, how to reproduce Satoshi's seed, which was used to initialize his random number generator, when he tried to mine "bnNonce" in the prenet coinbase transaction in 2008? Source code: https://bitcointalk.org/index.php?topic=382374.msg4108762#msg4108762 Here, we can see "695dbf0e" as "bnNonce". It is supposed to be random, but it is only some 32-bit number, so there are not so many values to check. And also, it comes from "BigNumber" library, which is also used for other purposes. So, is the same randomness used to generate the private key for "04 d451b0d7e567c615719a630b9f44632a0f34f5e7101f9942fe0b39996151cef1 0a809c443df2fab7cd7e58a3538cd8afd08ccfaa49b637de4b1b383f088ad131", or is it somehow separated? Because if it is connected, then potentially, this private key can be recovered. Also, if the source of randomness is just some timestamp from 2008, then it could reveal, when exactly this public key was created. Edit: It seems "OpenSSL 0.9.8h 28 May 2008" was in use, or maybe even some older version. And it contains these pseudo-random values, which can give a hint, if called functions were pseudorandom for prenet, just to test things, or if the real randomness was used: Still trying to figure it out, if things are random or pseudorandom. Starting from pseudorandom should be easier, because it should give the exact same numbers.

03d451b0d7e567c615719a630b9f44632a0f34f5e7101f9942fe0b39996151cef1 this is a 2025 adress has 1$ info https://decashed.eth.loan/2025/01/the-pre-release-genesis-blocks-first-address/