Quote
why is there no copy to find for version 0.0.9?
Because "0.0.8" is artificial name, that you cannot find in the source code. There was pre-release version, with no versioning, then Satoshi introduced versions here and there, and then he released "BitCoin v0.01 ALPHA" as the first official one. Initially, there were only two digits: major version (equal to zero), and minor version (equal to one). The third digit was introduced later, and that's why that version is recognized as "0.1.0". But it was initially just "0.01". And there was no "0.0" version, because there was simply no versioning at all in earlier code (also, Satoshi started counting from one, the first zero was only used to indicate "ALPHA" state, and was later dropped in 22.0 version by Core developers). If you want to confirm that, you can look for example at block header: note it had no version in "November 2008 code". And if you explore that code from 2008, you will notice that there is no "eight version" anywhere in that code. It was simply taken from the year, and made out of thin air by some people.And if you don't believe me, then open your "0.1.0" version, and read just the first line of "readme.txt".
Edit: Satoshi started writing code in 2007. But at this point in time, there was no versioning anywhere in his own code. However, you can find this date, where he grabbed some libraries, for example this one:
Quote
Code:
// This file is public domain
// SHA routines extracted as a standalone file from:
// Crypto++: a C++ Class Library of Cryptographic Schemes
// Version 5.5.2 (9/24/2007)
// http://www.cryptopp.com
#ifndef CRYPTOPP_SHA_H
#define CRYPTOPP_SHA_H
#include <stdlib.h>
namespace CryptoPP
{
// SHA routines extracted as a standalone file from:
// Crypto++: a C++ Class Library of Cryptographic Schemes
// Version 5.5.2 (9/24/2007)
// http://www.cryptopp.com
#ifndef CRYPTOPP_SHA_H
#define CRYPTOPP_SHA_H
#include <stdlib.h>
namespace CryptoPP
{
How long have you been working on this design Satoshi? It seems very well thought out, not the kind of thing you just sit down and code up without doing a lot of brainstorming and discussion on it first. Everyone has the obvious questions looking for holes in it but it is holding up well 
Since 2007. At some point I became convinced there was a way to do this without any trust required at all and couldn't resist to keep thinking about it. Much more of the work was designing than coding.Fortunately, so far all the issues raised have been things I previously considered and planned for.
There are more pieces of code you can check, like those ones:
Quote
Code:
static const int VERSION = 101;
Quote
Code:
CAboutDialog::CAboutDialog(wxWindow* parent) : CAboutDialogBase(parent)
{
m_staticTextVersion->SetLabel(strprintf("version 0.%d.%d Alpha", VERSION/100, VERSION%100));
{
m_staticTextVersion->SetLabel(strprintf("version 0.%d.%d Alpha", VERSION/100, VERSION%100));
right this now also makes sense.
i found out this version principle was original coming as a development by IBM
they are called Internetional Business Machines inside own brand name.
and 101 is always a typical indicator for business worlds.
what shows how this company did also create how the world is understood as a root thing.
they were the first that were working with naming a first version in this case. 0.1 alpha as version. 0.2 a beta version. 0.3 as gamma
especially those 3 came alive as kind of a Standard in their own beginning days for creating code by coders and developers for their own hardware.
later the principle: major.minor.patch was created to get into as this version shows 0.0.8
yes they dropped the first major part for bitcoin.
but i think we should understand this as going life for the individual user. meaning it can either be a 0 or a 1 in value.
in this case we reached 1 as the first number already and from there on it switched ON for mass consumers use case and resulted in no longer using Major.
or better said Major replaced Minor.
so only 2 parts are now existing for versioning definition what makes it into x.x to show
and today we are in version 25.0
but one problem still stays:
you cannot switch ON that network without declaring yourself a miner!
cause mining is what makes the network connect to the principle of work being done, money power and hence its own evolution for development.
i wonder what will happen when the official coins are mined in full.
people will start to analyse more its roots.
finding out what i wrote about amounts being encrypted inside code as well.
and from there? increasing into 33,... million coins?
would not wonder me
but then i guess in this moment it will starting to decay.
maybe it already did the moment it got changed into 21 millions.
as long as this is still locked into the infinity loop for file main.h and what code line 33 does with itself in 0.0.8. the network runs better.
like immortality in principle as an effect.
on the other hand humans are not mortal what points on the first version that did change the code from that original line into 21 million, started to decay the codes life span.
like any software being created is going eventually to die out.
sure you can revive it in some way but only inside an understanding as a kind of simulated environment from the past inside modern times.
the principle why virtual machines got created.
the lies and the visions from the past created the future once. people got born into not understanding the lies as lies anymore. believing more into the lies than its orignal truth.
it becomes their world of understanding and from inside this they try to connnect into implementing the past.
explains why the truth is not always pleasant and it can completely blow your mind.
but let*s just focus on making the best out of it we can of our own time i guess.
so much for versioning increasing and its effect on software and people.