The discussion about the terminology used by Satoshi Nakamoto when creating Bitcoin has generated considerable debate in the crypto community. One of the most contentious points is the distinction between the terms "Timechain" and "Blockchain." Initially, Satoshi used "Timechain" to describe the interconnected block structure in Bitcoin, but later removed all references to this term. Why did this happen? What is the significance behind this change? Let's explore these points in detail.
*The Origin of the Term Timechain*
In the first version of Bitcoin's code released by Satoshi Nakamoto, the term "Timechain" was used to describe the sequence of blocks that make up Bitcoin. This terminology may have been chosen due to the sequential nature of the blocks, which are added approximately every ten minutes. However, as the project developed and the code evolved, all references to "Timechain" were removed, replaced by more generic terms like "chain" and "chain of blocks."
*Why Did Satoshi Nakamoto Remove Timechain?*
There are several theories about why Satoshi decided to remove the term "Timechain." The most plausible is that he realized the terminology did not adequately capture the nature of the Bitcoin network. Let's analyze some points that may have influenced this decision:
- Block Unpredictability: The idea of "Timechain" suggests a precise and predictable time sequence, something Bitcoin cannot guarantee due to the variation in the network's hash rate. While the goal is for new blocks to be added every ten minutes, in practice, this can vary. The exact time of creation of each block depends on many factors, including network difficulty and available computational power.
- Transaction Sequencing: In a "Timechain," transactions are expected to be sequential and time-ordered. However, in Bitcoin, the order of transactions within a block is determined by the miner who solves the block. This means that while transactions are immutably recorded, their order is not necessarily sequential in terms of time.
- Time Reliability: The timestamp of each block in Bitcoin is based on the time provided by the miner and validated by network nodes. This timestamp, however, is not an exact measure of time and can be slightly adjusted by the miner as long as it is within an acceptable range. This reduces the precision and reliability of the "Timechain" concept.
*The Philosophy of Time*
Another interesting point is the philosophy of time itself. Time is a concept widely discussed in both philosophy and science. There are debates about its nature, existence, and how it should be measured. However, there is consensus that time is a continuous sequence and divisible into measurable units such as seconds, minutes, and hours. This divisibility allows time to be predictable and used to measure events consistently.
In the context of Bitcoin, while we can predict that a block will be added every ten minutes on average, we cannot predict the exact moment a block will be created. This imprecision makes the concept of "Timechain" inadequate, as Bitcoin's block chain does not follow an exact time sequence.
*The Evolution of Bitcoin's Code*
In the original Bitcoin code, there were references to "hashTimechainBest," which indicated the best block within the longest chain. Over time, this terminology was replaced by terms like "hashBestChain" and "chainWork," which refer to the difficulty and accumulated work in the block chain. This change reflects a deeper understanding of Bitcoin's nature and operation.
In the code revised by Gavin Andresen, one of Bitcoin's early developers, we no longer find references to "Timechain." Instead, we see an emphasis on "chain" and "block," focusing on network integrity and security. The removal of "Timechain" and the adoption of "chain of blocks" (in the whit...
One would expect a timechain to not only target a fixed block time, but also to tie its emission to time. That is most simply achieved by 1 minute blocks with a fixed 60 coin reward. Then the coin supply simply equals the chain age in seconds.
The issue lies in the fact that we cannot establish a deterministic time interval between blocks, as miners must compete with their hashing power to discover each block. Implementing a fixed interval would compromise security. Moreover, setting a very short time frame between blocks could lead to a bunch of orphan blocks and other issues because of relay time, bandwidth, and others.
The idea is interesting, but the implementation poses challenges.
While highly variable, the blocktime average over hundreds of blocks can be held very close to its target (and with a trivial one line difficulty adjustment to boot). The orphan rate doesn't get pronounced until blocktimes are made significantly shorter than 1 minute.
5 comments
[ 3.3 ms ] story [ 17.9 ms ] thread*The Origin of the Term Timechain*
In the first version of Bitcoin's code released by Satoshi Nakamoto, the term "Timechain" was used to describe the sequence of blocks that make up Bitcoin. This terminology may have been chosen due to the sequential nature of the blocks, which are added approximately every ten minutes. However, as the project developed and the code evolved, all references to "Timechain" were removed, replaced by more generic terms like "chain" and "chain of blocks."
*Why Did Satoshi Nakamoto Remove Timechain?*
There are several theories about why Satoshi decided to remove the term "Timechain." The most plausible is that he realized the terminology did not adequately capture the nature of the Bitcoin network. Let's analyze some points that may have influenced this decision:
- Block Unpredictability: The idea of "Timechain" suggests a precise and predictable time sequence, something Bitcoin cannot guarantee due to the variation in the network's hash rate. While the goal is for new blocks to be added every ten minutes, in practice, this can vary. The exact time of creation of each block depends on many factors, including network difficulty and available computational power.
- Transaction Sequencing: In a "Timechain," transactions are expected to be sequential and time-ordered. However, in Bitcoin, the order of transactions within a block is determined by the miner who solves the block. This means that while transactions are immutably recorded, their order is not necessarily sequential in terms of time.
- Time Reliability: The timestamp of each block in Bitcoin is based on the time provided by the miner and validated by network nodes. This timestamp, however, is not an exact measure of time and can be slightly adjusted by the miner as long as it is within an acceptable range. This reduces the precision and reliability of the "Timechain" concept.
*The Philosophy of Time*
Another interesting point is the philosophy of time itself. Time is a concept widely discussed in both philosophy and science. There are debates about its nature, existence, and how it should be measured. However, there is consensus that time is a continuous sequence and divisible into measurable units such as seconds, minutes, and hours. This divisibility allows time to be predictable and used to measure events consistently.
In the context of Bitcoin, while we can predict that a block will be added every ten minutes on average, we cannot predict the exact moment a block will be created. This imprecision makes the concept of "Timechain" inadequate, as Bitcoin's block chain does not follow an exact time sequence.
*The Evolution of Bitcoin's Code*
In the original Bitcoin code, there were references to "hashTimechainBest," which indicated the best block within the longest chain. Over time, this terminology was replaced by terms like "hashBestChain" and "chainWork," which refer to the difficulty and accumulated work in the block chain. This change reflects a deeper understanding of Bitcoin's nature and operation.
In the code revised by Gavin Andresen, one of Bitcoin's early developers, we no longer find references to "Timechain." Instead, we see an emphasis on "chain" and "block," focusing on network integrity and security. The removal of "Timechain" and the adoption of "chain of blocks" (in the whit...
One coin per second forever...
The idea is interesting, but the implementation poses challenges.