cgra's

The Main Point

There was a particular, strange detail in TRB's block and transaction synchronization, to which I found a plausible clue from the pre-TRB commit history. But if I wanted to document this interesting detail, where would I refer to? I don't see much point in referring to some Github or whatever random corporate platforms, so I needed something else.

I will come back to this particular synchronization case later, but now I will share my copy of the pre-TRB commit history, and will begin use that as my point of pre-TRB reference in the future.

This copy of the https://github.com/bitcoin/bitcoin.git repository was cloned in 2020-06-03, so it is not particularly close to the revision TRB's genesis is born from, which would've been ideal.

If you, the reader, happen to have an older copy lying around, please verify, if the pre-TRB history is the same in your copy as in mine. I tried to make it easy by including a script just for that purpose.

The included script will do four things:

• Extract all the 1716 commits as separate patch files, possibly for gitless consumption.
• Calculate SHA512 hashes for each patch file.
• Calculate SHA512 hashes from each revision the commits represent. It will take all the files and file names for each revision, sort them, and hash into a single revision hash.
• Record chronological order, commit hashes, parent commits, and corresponding patch and revision hashes into a single, large list.

The results of my own script run is included in the file, and should help verifying the sameness of our separate repository copies.

The file: pre-trb.tar.gz (166'276'856 bytes), and my signature.

Other Notes

The included git repository will also contain commits from the "TRB genesis commit" to the moment I cloned it onto my computer. They're there only because I didn't have an easy or clean way to get rid of them.

Some of these commits may have more than one parent (they are merges).

Some patches may appear in two separate series of commits, which eventually merge into one series. It's probably so, because for some time there existed a SourceForge SVN repository simultaneously with the Git repository. Same changes were committed twice, once for each separate repository, but eventually joined into a single Git repository.