4 Aspects from the Bitcoin Whitepaper
Time is up and you submitted the aspects below.
1. Two aspects of the whitepaper that you understood well and found interesting; explain them in detail in your own words. 1.1 Proof-of-Work One aspect of the Bitcoin whitepaper that I think I understand well is the Proof-of-Work concept. In this system, the computational power of the network nodes is used to verify transactions and add new blocks to the blockchain. Nodes in the network perform calculations in order to find a number that produces a valid hash for a block. When a node successfully finds this value, it proves that it has invested computational effort into solving the problem, which allows the block to be added to the blockchain. Once the block is added, the transactions contained in it become part of the public ledger, which stores the full history of previous transactions. This makes it possible for the network to verify which transactions are valid. The node that successfully mines the block is rewarded for its work. This reward comes in two forms: the block reward for mining the block and the transaction fees from the transactions included in that block. I find this concept interesting because the system uses computational work as proof that the block is valid. Instead of relying on a central authority, the network itself verifies the correctness of transactions through the work performed by the nodes. 1.2 Security Through Computational Difficulty Another aspect I understood well is how the system protects itself from attackers who might try to manipulate transactions or rewrite parts of the blockchain. In order to change a transaction in a previous block, an attacker would have to redo the Proof-of-Work for that block and for every block that was added after it. At the same time, the rest of the network continues to add new blocks to the chain. This means that an attacker would need enormous computational power to catch up with and eventually surpass the rest of the network. In practice, this becomes extremely difficult and expensive. Because of this, it is usually more rational for participants to follow the rules of the system and use their computational power to mine blocks honestly instead of trying to attack the network. I found this aspect particularly interesting because it shows how Bitcoin aligns incentives in a way that protects the system from corruption. The cost of attacking the network becomes so high that honest participation is the more profitable option for most participants. 2. Two aspects of the whitepaper that you found hard to grasp; explain why you struggled. 2.1 Long-Term Privacy of Public Transactions One aspect of the Bitcoin whitepaper that I found harder to fully grasp is the idea that privacy can be maintained simply by keeping public keys anonymous. The whitepaper explains that transactions are publicly visible on the blockchain but are linked only to cryptographic addresses rather than real identities. It also suggests generating new key pairs for each transaction to reduce the ability to link activities to a single owner. While I understand how this mechanism works technically, I find it difficult to fully grasp how effective this privacy protection is in practice over long periods of time. Because all transactions are permanently recorded on the blockchain, a large history of transactions is continuously accumulating. Over time, patterns may emerge that allow analysts to connect different addresses through transaction behavior, especially when multiple inputs are used or when funds move between related wallets. Additionally, in real-world situations, people and companies often interact with exchanges, payment services, or merchants that require identity verification. If one address is ever linked to a real identity, it may become possible to trace related transactions and connect other addresses to the same user. This makes me question how strong the privacy guarantees really are once enough transaction data and external information become available. For this reason, while I understand the concept of pseudonymous privacy described in the whitepaper, I find it challenging to fully understand how this model can maintain strong privacy in the long term as more transaction history and data analysis techniques develop. 2.2 Reclaiming Disk Space and Merkle Trees Another part of the Bitcoin whitepaper that I found difficult to fully understand was the section about reclaiming disk space using Merkle trees. The whitepaper explains that once a transaction is buried under enough blocks, older transaction data can be discarded in order to reduce the amount of storage required by the blockchain. Instead of storing all the detailed transaction data, only certain cryptographic hashes from a Merkle tree need to be preserved. While I understand the general goal of reducing storage requirements, I struggled with the exact mechanism that allows data to be removed without breaking the block’s hash. The whitepaper states that transactions are organized in a Merkle tree and that only the root hash of this tree is included in the block header. Because the root represents all transactions in the block, parts of the tree can theoretically be removed while the root hash still proves the integrity of the data. What I found difficult to grasp is how deleting parts of the transaction data does not affect the ability to verify the blockchain later. Since the blockchain is supposed to be an immutable and fully verifiable record, it was initially confusing to understand how nodes can remove information but still maintain trust in the system. The idea that only certain hashes need to remain while the rest of the data can be “stubbed off” was conceptually challenging, especially without a deeper understanding of how Merkle trees structure and verify information.