Chapter 1: The Historical Heritage of Cryptography—The Foundation of Trust

Introduction

In the digital world, everything is composed of code. How can we trust that the bank balance displayed on the screen is real? How can we ensure that the email we send has not been tampered with? The answer is cryptography. This ancient yet modern discipline is the security cornerstone of the entire digital world and also the first foundation stone of the magnificent blockchain edifice. To understand the revolutionary nature of blockchain, we must explore its genetic origins from the source - the long river of cryptographic history.

1.1 From Caesar Cipher to Modern Computers

The history of cryptography stretches back far. As early as over two thousand years ago in ancient Rome, Caesar the Great invented a simple shift encryption method - the "Caesar Cipher" - to transmit secret information during wars. This marked the beginning of classical cryptography. Throughout the long course of history, cryptography has always been an exclusive tool for military and diplomatic fields, with its core idea being that "encryption" and "decryption" use the same "key," which is called "symmetric encryption."

World War II pushed cryptography to new heights. Germany's "Enigma" machine once gave the Allies severe headaches, while the decryption work by scientists led by Alan Turing at Bletchley Park not only greatly shortened the war but also directly led to the birth of modern computers. After the war ended, cryptography gradually entered public view, but its core "symmetric encryption" concept faced a huge challenge: in an open network like the Internet, how to securely deliver the key to the other party in communication? This is called the "key distribution problem."

1.2 Public Key Cryptography: An Asymmetric Revolution

The turning point came in the 1970s. At Stanford University, three young scholars - Whitfield Diffie, Martin Hellman, and Ralph Merkle - launched an attack on this century-old problem.

They proposed a revolutionary idea: why must encryption and decryption use the same key? They envisioned whether it was possible to create an "asymmetric" key pair, where one key could be made public to anyone, called the "public key," while the other would be secretly kept by oneself, called the "private key." When others want to send you information, they can encrypt it with your public key, and this ciphertext can only be decrypted by you who possess the corresponding private key.

This idea completely solved the "key distribution problem." You no longer need to transmit keys through any secret channels; you simply need to boldly publish your public key to the world. In 1976, they published the paper "New Directions in Cryptography," officially announcing the birth of "public key cryptography." The status of this paper in the field of cryptography is comparable to the theory of relativity in physics. Interestingly, documents declassified many years later revealed that mathematicians James Ellis and Clifford Cocks at the British intelligence agency GCHQ had actually proposed similar ideas internally a few years earlier, but they were classified as top secret at the time.

Soon after, in 1977, three scholars at MIT - Ron Rivest, Adi Shamir, and Leonard Adleman - found the first mature algorithm for implementing public key cryptography. They named it the "RSA algorithm" using the initials of their surnames. The security of the RSA algorithm is based on a simple number theory fact: multiplying two large prime numbers is easy, but factoring this product is extremely difficult. The birth of this algorithm marked the transition of public key cryptography from theory to practice.

1.3 Digital Signatures: Undeniable Identity Proof

The magic of public key cryptography doesn't stop at encryption. By reversing the use of public and private keys, another revolutionary technology was born - digital signatures.

When you need to prove to others that a document was indeed sent by you and has not been tampered with, you can "sign" this document with your "private key" (actually performing an encryption calculation). After others receive the document, they can use your public "public key" for verification. If the verification passes, it proves two things simultaneously:

1. Identity Authentication: Since only you possess the private key, this signature must come from you and cannot be forged by others.
2. Data Integrity: Even the slightest change to the document content would fail to pass public key verification.

Digital signatures provide verifiable, undeniable proof of identity and data authenticity in the digital world. This technology became the core guarantee for the legitimacy of Bitcoin transactions later on.

1.4 Hash Functions: Creating Unique "Fingerprints" for Data

In the practice of digital signatures, we need another tool: hash functions. If we want to sign a huge file (like a movie), directly performing encryption calculations on it would be very slow. The role of hash functions is to convert data of any length into a fixed-length, unique string through an algorithm. This string is called a "hash value" or "digital fingerprint."

An excellent hash function (like SHA-256) has the following key characteristics:

• Determinism: The same data input will always produce the same hash value.
• Irreversibility: It's impossible to reverse-engineer the original data from the hash value.
• Avalanche Effect: Even the slightest change in the original data will result in a completely different hash value.
• Collision Resistance: It's nearly impossible to find two different pieces of data that produce the same hash value.

With hash functions, we can sign the "hash value" of a file instead of signing the entire file. This greatly improves efficiency. More importantly, hash functions play a crucial role in blockchain: they are not only used to generate unique identifiers for transactions but also serve as the link that "chains" blocks together. Each new block must contain the hash value of the previous block, forming an unalterable chain. Any modification to historical blocks would cause the hash values of all subsequent blocks to change, making it easily detectable by the network.

Summary

Public key cryptography, digital signatures, and hash functions - these three technologies born in the 1970s-80s - together constitute the "troika" of modern cryptography. They provide the foundation for identity authentication, data encryption, and integrity protection in the digital world. Although they were not originally created for cryptocurrency, they inadvertently prepared all the necessary "technical components" for Bitcoin's emergence thirty years later. A revolution concerning money and trust had its technical foundation ready, waiting only for a genius architect who could cleverly piece them together.