Skip to main content
Cryptography Basics
CHAPTER 14

Blockchain and Cryptography Basics

Updated: May 15, 2026
20 min read

# CHAPTER 14

Blockchain and Cryptography Basics

1. Introduction

Throughout this course, we have used cryptography to secure data controlled by a central authority—a bank server, an AWS data center, or a Certificate Authority. But what if people don't trust central authorities? Can we use cryptography to create a system where millions of strangers agree on a single, unalterable truth without needing a bank to verify it? The answer is the Blockchain. In this chapter, we will strip away the financial hype surrounding cryptocurrency and focus purely on the cryptographic mechanisms—Hash Chains and Digital Signatures—that make distributed ledgers possible.

2. Learning Objectives

By the end of this chapter, you will be able to:
  • Define a Blockchain from a purely cryptographic perspective.
  • Understand how Hash Chains create an immutable ledger.
  • Explain the role of Digital Signatures in cryptocurrency transactions.
  • Differentiate between a Centralized Database and a Distributed Ledger.
  • Recognize the security vulnerabilities in blockchain ecosystems (e.g., wallet theft).

3. Beginner-Friendly Explanation

Imagine a group of 10 friends playing a high-stakes poker game without poker chips.
  • Centralized (The Bank): They nominate Alice to write down everyone's balance in a notebook. Everyone trusts Alice. But if Alice is secretly bribed, she can change the numbers.
  • Decentralized (Blockchain): *Everyone* gets a notebook. Every time a bet is made, the person shouts it out: "Bob pays Charlie $50!" All 10 friends write it down simultaneously.
  • The Cryptography: To ensure nobody can erase a previous page, every time a page is filled, they take a mathematical "Fingerprint" (Hash) of that page. They write that fingerprint at the very top of the *next* page. If anyone tries to rip out a past page and change a bet, the fingerprints on all subsequent pages will instantly break, and the other 9 friends will reject the altered notebook.

4. Hash Chains (The "Block" in Blockchain)

A Blockchain is literally just a chain of blocks of data, linked together by cryptography.
  1. 1. Block 1 (The Genesis Block): Contains transactions (e.g., "Alice pays Bob 1 BTC"). It is run through a SHA-256 hash function. *Hash:* 0000abc123...
  1. 2. Block 2: Contains new transactions. Crucially, it also includes the Hash of Block 1. It is then hashed. *Hash:* 0000def456...
  1. 3. Block 3: Includes new transactions AND the Hash of Block 2.

The Avalanche Effect in Action: If a hacker goes back in time and tries to change a transaction in Block 1, the Hash of Block 1 completely changes. Because Block 2 included the *old* Hash of Block 1, Block 2 is now mathematically invalid. The hacker would have to re-hash Block 1, Block 2, Block 3, and every block ever created, faster than the rest of the world combined. This is computationally impossible, making the ledger Immutable.

5. Digital Signatures in Transactions

If there is no bank, how does the system know Alice actually authorized the payment to Bob? Asymmetric Cryptography:
  • A "Cryptocurrency Wallet" is not a container that holds coins; it is simply a piece of software that manages a Public/Private Key pair.
  • Your Public Key is your Wallet Address. Anyone can see it and send money to it.
  • Your Private Key is your password. You use it to digitally sign outgoing transactions.

When Alice sends money to Bob, she writes the transaction and signs it with her Private Key. The network of computers verifies the signature using her Public Key. If the signature is valid, the transaction is permanently added to the next block.

6. Distributed Ledgers and Consensus

In a blockchain network (like Bitcoin), there is no central server. Millions of computers (Nodes) around the world hold a complete copy of the ledger. When a new block of transactions is created, it is broadcast to all Nodes. They all independently verify the hashes and the digital signatures. If the math checks out, they all agree (Consensus) to add the block to their local copy of the ledger.

7. Mini Project: Build a Simple Blockchain Simulation (Concept)

How does a developer actually link blocks together?

The Conceptual Code Logic:

python
1234567891011 
# Block 1
Block1_Data = "Alice pays Bob 10"
Block1_PreviousHash = "00000000" # First block has no previous hash
Block1_Hash = SHA256(Block1_Data + Block1_PreviousHash)
# Result: 8f2a...

# Block 2
Block2_Data = "Bob pays Charlie 5"
Block2_PreviousHash = "8f2a..." # It includes Block 1's Hash!
Block2_Hash = SHA256(Block2_Data + Block2_PreviousHash)
# Result: 3c9b...

If you alter Block1Data, Block1Hash changes, causing Block2_Hash to fail verification. The chain is broken.

8. Real-World Scenarios

In 2014, the Mt. Gox cryptocurrency exchange handled 70% of all Bitcoin transactions worldwide. Hackers systematically stole 850,000 Bitcoins (worth billions today). Crucially, the hackers did *not* break the SHA-256 algorithm, nor did they break the blockchain itself. The blockchain remained mathematically perfect. The hackers compromised the centralized web servers of the Mt. Gox company and stole the users' Private Keys (which were stored insecurely). In blockchain, "Not your keys, not your coins." If someone steals your Private Key, they own your identity on the network.

9. Best Practices

  • Cold Storage (Hardware Wallets): Because Private Keys are the sole proof of ownership in a decentralized system, keeping them on a computer connected to the internet (a "Hot Wallet") is extremely dangerous due to malware. Best practice dictates storing large amounts of cryptocurrency on "Cold Storage" hardware wallets (like Ledger or Trezor)—physical USB devices that sign transactions internally, ensuring the Private Key never touches an internet-connected computer.

10. Legal and Ethical Notes

While the cryptography behind blockchain is neutral and secure, the decentralized nature of the technology makes it a preferred tool for ransomware gangs, money laundering, and dark web marketplaces. Security professionals tracking threat actors often analyze the public blockchain ledger (Chain Analysis) to trace the flow of illicit funds between anonymous wallet addresses.

11. Exercises

  1. 1. Explain how the inclusion of the "Previous Block's Hash" secures a blockchain against retrospective tampering.
  1. 2. What cryptographic primitive ensures that a user cannot spend cryptocurrency belonging to someone else?

12. FAQs

Q: Is blockchain only used for cryptocurrency? A: No. While cryptocurrency is the most famous application, the underlying technology (an immutable, distributed ledger) is being adopted for supply chain tracking, secure medical records sharing, and digital voting systems—any scenario where multiple untrusting parties need a mathematically verifiable single source of truth.

13. Interview Questions

  • Q: Describe the role of SHA-256 in maintaining the immutability of a blockchain. How does the "Avalanche Effect" prevent historical ledger alteration?
  • Q: In a decentralized blockchain environment, explain the functional difference between a Public Key (Wallet Address) and a Private Key. Why is key management considered the weakest link in cryptocurrency security?

14. Summary

In Chapter 14, we examined cryptography applied at a global, decentralized scale. We demystified the Blockchain, revealing it to be nothing more than a chronological database secured by continuous SHA-256 Hash Chains. We learned that without central banks, trust is enforced entirely by Asymmetric Cryptography, using Digital Signatures to prove ownership and authorize transactions. Ultimately, we established that while the blockchain's mathematics are incredibly secure, the human responsibility of guarding the Private Key is absolute.

15. Next Chapter Recommendation

We have explored all the major algorithms and architectures. Now, we must define the operational rules for managing them safely. Proceed to Chapter 15: Cryptographic Best Practices.

Finish this Chapter

Save your progress on your learning path and prepare for coding interview challenges.

Previous Chapter Cryptography in Cloud Computing
Next Chapter Cryptographic Best Practices

Discussion

Join the discussion

Log in or create a free account to participate.

Sort: ·

Explore More

📖 Related Tutorials 4

❓ Related Quizzes 5