Duration: 90 minutes
Core Idea: Bitcoin's security depends on simple but powerful technical ideas such as keys, signatures, hashing, and UTXOs, which allow ownership and verification without a central authority.
Learning Objectives
By the end of this lesson, students should be able to:
- Explain how public and private keys help secure Bitcoin ownership and transactions.
- Describe what a digital signature is and how it proves that a transaction was authorized by the rightful owner.
- Explain, in simple terms, what cryptography, encryption, and decryption mean in the context of Bitcoin.
- Define hashing and describe why hash functions are important for Bitcoin's security and data integrity.
- Identify basic properties of a hash function, such as fixed-length output, one-way behavior, and sensitivity to small input changes.
- Explain the UTXO model and how bitcoin is spent, received, and returned as change through transaction outputs.
- Describe how nodes help prevent double-spending by checking whether an output has already been spent.
Tools & Resources
Visual Aids
- Chapter 8 - How Bitcoin Works
Support Library
- Vocabulary Reference Card — Chapter 8 — Terms: cryptography, hash, UTXO, digital signature, private/public key, merkle tree, blockchain
- Misconceptions Libraries — Chapter 8 — Address: "lost seed phrase can be recovered," "private key = password," "blockchain is anonymous"
- Technical Explainers & Deep-Dives — Hash functions, public/private keys, UTXO model, Proof of Work security
Activities
- Transactions in Action
- Exploring the Mempool
Online Teaching
- Use a digital whiteboard and draw each concept live rather than relying only on verbal explanation.
- Teach one technical idea at a time and pause often for checking questions.
- Use visuals for keys, signatures, hashes, and UTXOs so students can follow the structure.
- Keep the goal conceptual and avoid going too deep into mathematics or jargon.
Preparation
- Prepare and laminate diagrams: public/private key pairs, digital signatures, UTXO model, hashing (one-way function).
- Bookmark blockchain explorer and SHA-256 hash calculator; select 2-3 real Bitcoin transactions to walk through step-by-step.
- Prepare whiteboard notes for explaining inputs, outputs, and how transactions confirm on the blockchain.
Procedure
This lesson gives students a first look at the technical side of Bitcoin without assuming prior technical knowledge. The guide now follows the same compressed structure as the Diploma, with cryptography grouped under one heading and UTXOs grouped under the other.
8.0 Introduction, 8 minutes
Start by setting expectations:
- What makes Bitcoin secure if there is no central bank controlling it?
- How can the network know whether a person really owns the bitcoin they are trying to send?
- What actually happens behind the scenes when someone makes a Bitcoin transaction?
Clarify that this chapter focuses on the basic technical foundations of Bitcoin, especially keys, signatures, hashing, and UTXOs. Also reassure students that they do not need to become engineers to understand the essential logic. The chapter itself makes this point clearly by comparing Bitcoin to the internet, many people use it every day without fully understanding every layer underneath it.
8.1 Security through Cryptography, 57 minutes
Bitcoin as a Ledger Stored Across Many Computers
Begin with the chapter's simple framing of the Bitcoin network:
- Bitcoin is a record of transactions
- that record is stored on many computers called nodes
- the ledger is public and pseudonymous
- it shows addresses and transaction history, not personal identity details
This section helps students connect back to what they already know from earlier chapters. Bitcoin is not based on hidden accounts inside a bank. It is based on a shared ledger that many participants can verify. is especially helpful here because it shows users, wallets, and the broader Bitcoin network connected to the public ledger.
Public and Private Keys
Now move into cryptography.
Explain that each Bitcoin user has:
- a private key, which must remain secret
- a public key, which can be shared
Clarify their purpose in simple terms:
- the private key proves control and authorizes spending
- the public key helps others verify that the transaction was authorized correctly
A strong teaching point from the chapter is that Bitcoin uses public/private key cryptography, not the older model where two people must first share the same secret key. That matters because it allows secure verification without forcing users to reveal the secret that protects their funds.
You can explain it like this:
- the private key is like the secret proof that the bitcoin belongs to you
- the public key is part of what allows the network to verify your authorization
- whoever controls the private key controls the ability to spend the bitcoin
Be careful here not to overcomplicate the encryption language. The most important point for students is ownership and authorization.
Digital Signatures and Transaction Authorization
Now explain what happens when someone sends bitcoin.
Use the chapter's sequence:
- a user creates a transaction
- the sender generates a digital signature using their private key
- the transaction is broadcast to the network
- nodes verify that the signature is valid
- once verified and confirmed, ownership is transferred on the ledger
Make clear that a digital signature is not the same thing as typing a name. It is cryptographic proof that the real owner authorized the transaction. This is one of the core mechanisms that allows Bitcoin to work without a central authority approving transactions manually. The diagram is useful because it shows signing and verification visually, as well as the transaction path from sender to network validation.
A good sentence for class is:
Bitcoin transactions are not approved because a bank says so. They are accepted because the network can verify valid cryptographic proof.
Hashing and One-Way Functions
Next, explain hashing.
Start simple:
- a function takes an input and produces an output
- a one-way function is easy to run in one direction, but realistically impossible to reverse
- a hash function takes data of any size and turns it into a fixed-length output called a hash
Use one of the chapter's analogies, whichever feels clearest for your audience:
- the smoothie analogy for one-way functions
- the fingerprint analogy for hashes
- the musical score analogy for checking whether something changed
The fingerprint analogy is probably the clearest for most classes:
- a hash is like a digital fingerprint for data
- if the input changes even a little, the hash changes completely
- this helps computers check integrity and detect tampering
Then explain why hashing matters in Bitcoin:
- transactions are hashed
- the network uses hashes to help verify integrity
- if a transaction is changed, the hash changes
- this helps protect the ledger from unnoticed manipulation
The visuals on pages 7 to 10 are very useful here. The chapter shows both the fixed-length output idea and the "small change, completely different result" principle, which is one of the most important concepts for students to understand.
Basic Properties of Hash Functions
Briefly walk through the properties highlighted in the chapter, without making them feel overly academic:
- Deterministic: the same input gives the same output every time
- One-way / pre-image resistance: you cannot realistically reverse the process
- Sensitive to change: even a small input change creates a very different output
- Collision resistance: it is extremely difficult to find two different inputs with the same output
- Fast to verify: the function is efficient to run and check
You do not need students to memorize every term, but they should understand the general point: hashing gives Bitcoin a reliable way to identify data and detect change.
8.2 The UTXO Model, 25 minutes
The UTXO Model
Now move into the second major part of the chapter: UTXOs, or Unspent Transaction Outputs.
Explain it in simple terms using the chapter's cash analogy:
- bitcoin is not tracked like a bank account balance only
- instead, it is made up of spendable pieces called UTXOs
- when you spend bitcoin, you use one or more existing UTXOs as inputs
- new UTXOs are then created as outputs
Use the example from the chapter:
- if you have a 10 BTC UTXO
- and you send 6 BTC
- a new 6 BTC UTXO goes to the recipient
- a new change UTXO comes back to you
- a small part is paid as a miner fee
That helps students see that Bitcoin works more like spending cash and receiving change than subtracting numbers from a simple account line. The diagrams are especially strong here because they visually show one UTXO being broken into recipient output, change output, and fee.
Make two key points explicit:
- your wallet balance is the sum of your UTXOs
- when you spend, old UTXOs are consumed and new ones are created
Preventing Double-Spending
Close the content by explaining one of the most important implications of the UTXO model.
If someone tries to spend the same output twice, nodes reject the second attempt because they maintain the ledger and can verify whether that UTXO has already been spent. This is how Bitcoin prevents double-spending without needing a central payment company to manage the records. The example is very useful here because it walks through Alice combining UTXOs, sending funds to Bob, receiving change, and having the confirmed transaction update the ledger across nodes.
A clear way to say it in class is:
Bitcoin prevents double-spending because the network keeps track of which outputs remain unspent and which have already been used.
Wrap-Up and Check for Understanding
Close with a few quick questions:
- What is the difference between a public key and a private key?
- What does a digital signature prove?
- Why is hashing useful in Bitcoin?
- What happens if a transaction is changed after it is hashed?
- What is a UTXO in simple terms?
- How does the network stop someone from spending the same bitcoin twice?
Educator Notes
This chapter contains more technical language than earlier ones, so prioritize clarity, analogy, and repetition.
The goal is not to turn students into developers. The goal is to help them understand why Bitcoin security works.
The strongest points to prioritize, if time is short, are:
- private key vs public key
- digital signatures
- what hashing does
- UTXOs as spendable pieces of bitcoin
- how double-spending is prevented
The most useful visuals in this chapter are:
- the user-wallet-network diagram
- the digital signature visual
- the hashing examples and fixed-length output diagrams on pages 7 to 10
- the UTXO diagrams on pages 10 to 12
What Good Looks Like
- It is important to treat cryptography as a foundation not a mystery, use heavy visuals, avoid deep mathematics, connect back to earlier chapters, and test understanding with applications like "If someone changes one transaction, what breaks?"
- Educators should be patient with students who struggle, think visually and draw everything, be honest about what students don't need to understand, be willing to say "I don't know but here's how we'd find out," and remain encouraging throughout.
- Students understand why Bitcoin cannot be hacked because it is protected by mathematics, respect the elegant design of the system, feel comfortable with complexity knowing they don't need every detail, gain confidence asking questions without judgment, and recognize they have leveled up in understanding something most people don't.
- Learning Outcomes should be met if students can explain cryptography basics like one-way functions and digital signatures without deep mathematics, understand the UTXO model showing that you own coins not accounts, recognize hashing as the foundation of Bitcoin's security, understand transaction anatomy including signatures and confirmations, explain why Bitcoin is immutable, and ask critical questions about potential attacks or vulnerabilities.
Time Management
If time is short, prioritize:
- Private key vs public key
- Digital signatures
- What hashing does
- UTXOs as spendable pieces of bitcoin
- How double-spending is prevented
If ahead, take time on:
- User-wallet-network diagram and visual security model
- Digital signature visual: detailed cryptographic process
- Merkle trees and chain security
- Advanced attack vectors and why they fail
If Students Struggle
- Cryptography as threatening → "You use it daily; Bitcoin uses it same way."
- Hashing as concept → Fingerprint analogy; unique, can't change without hash change.
- Digital signatures → "Proves authorization without revealing password."
