Quote
maybe the coinbase maturity was what you meant?
No, because it was 120, before it was simplified into 100. If you have 6 blocks per hour, then 120 was used as "20 hours".After a block is created, the maturation time of 120 blocks is to make absolutely sure the block is part of the main chain before it can be spent. Your node isn't doing anything with the block during that time, just waiting for other blocks to be added after yours. You don't have to be online during that time.
i wanna quote this again cause i found this in 0.1.0 in lines 540 - 545
int CMerkleTx::GetBlocksToMaturity() const
{
if (!IsCoinBase())
return 0;
return max(0, (COINBASE_MATURITY+20) - GetDepthInMainChain());
}
if you were not pointing on older versions than 0.0.8 (but i doubt he would have discussed them with anyone and only before this forum even existed via e-mail with at max 1 other guy cause the net transitioning from 0 to 1 was already also be implemented via a Left shift (line 33 inside an enum in node.h), from how i understanding this, he used it as a transitioning state thing in principle. basically to activate this version from OFF into ON inside the code (it means the moment you read this line the network basically switches ON). node.h and node.pp were renamed into net.h and net.cpp in version 0.1.0 there you will find the same build for this enum and i doubt this should be understood in any other way).
but back to my before put code example:
then this should solve the confusion where 120 origins from.
so basically he added another 20
but how you come into 20 hours is still not clear to me?
was it really 6 hours per block back then in block generation (what would have meant he did only work to build the code further after 20 hours where over. well ok sleep time and such. quite impressive discipline if you do this in a robotic way if you ask me.
well maybe you have some more insight i do not have yet. this really makes a lot of fun now, to reconstruct how this was build up
