How Blockchain Works | Why Privacy Is Hard
A public blockchain can make transactions independently checkable, but that visibility can also reveal patterns about people. A pseudonymous address is not the same as an anonymous person, and putting a hash on a ledger does not automatically make sensitive data safe.
This article is written for children, parents and adults who want to understand how the system actually works. The practical example is fictional and does not describe a deployed eduKateSG blockchain. No cryptocurrency purchases or real accounts are required.
A real question behind the technology
Alicia’s class shares certificates for a science fair. The organisers want parents to verify awards, but the proposed ledger includes student names, scores and timestamps. Tricia asks a crucial question: why must everyone see these details merely to check that a certificate came from the school?
Before choosing a blockchain, ask whether a conventional database, signed record or accountable operator can meet the same need. The value of a shared ledger has to be established rather than assumed.
1. The difference between public verification and public disclosure
The organiser’s useful goal is to let a recipient check that a certificate was issued by an authorised school. That does not require broadcasting every student’s assessment record. An issuer-controlled signed credential may satisfy the need without any blockchain. If a ledger is justified for a separate shared-status purpose, the design should minimise what is published.
2. Why pseudonymous addresses can reveal identities
A public address may not contain a person’s name, yet repeated transactions, timing, counterparties and outside information can link activity together. Once an address is connected to a person, a history of otherwise separate actions may become easier to interpret. Pseudonymity is therefore a limited protection, not a promise of anonymity.
3. Why a hash is not automatically private
Hashing data can help establish a commitment or detect changes. But a hash of a predictable value, such as a short student identifier, may be vulnerable to guessing and comparison. Publishing the hash can also reveal that a particular record exists. The right design must examine what can be inferred from all the available information.
4. The problem of lasting copies
Replicated ledger records can be difficult to remove from every participating system. A later correction or revocation entry does not guarantee that earlier personal details disappear. The organisers need a privacy and retention plan before publishing anything.
5. A better school design
Use fictional identifiers for classroom demonstrations. For actual student records, examine signed credentials, restricted status services, selective disclosure and an appropriate data-protection review. Separate what the recipient needs to verify from what the school needs to store.
A family activity: find the missing assumption
Draw three boxes labelled People, Digital Record and Real-World Result. Read the opening story and ask: Can a parent verify that a certificate is authentic without seeing every student’s results? Invite the learner to name what can be checked, which person has authority and which fact still needs evidence.
Now change one condition. One organisation goes offline, an authorised officer makes a mistake or a website shows outdated information. Ask whether the record, the real-world outcome and the responsibility for correction are the same thing. They are not. Let the learner propose a simpler solution if it works.
What parents and adults should ask
Identify the exact requirement, participants, permissions, independent verification mechanism, source of outside facts and incident owner. Ask how the system handles delay, errors, recovery, privacy and the loss of an operating organisation.
A good decision includes a baseline comparison with conventional alternatives and a measurable outcome. Producing more blocks, attracting attention or using a fashionable label is not evidence that the original problem was solved.
Frequently asked questions
Does blockchain eliminate trust?
No. It can change who must be trusted for particular digital actions and what can be checked independently. Source data, software, keys, governance and human responsibility remain.
Do children need a real wallet to learn this?
No. Paper examples, invented records and clear role cards are enough to teach the important distinctions.
Is a more complicated system automatically more secure?
No. Security depends on the specific design, implementation, threat model, operational practice and assumptions. Complexity creates additional responsibilities as well as potential capabilities.
Continue through the learning library
For the specialist treatment, visit <a href=”https://edukatesg.com/portfolio/master-blockchain-069-pseudonym-metadata-inference/”>the related technical lesson</a>. Continue through the <a href=”https://edukatesg.com/master-blockchain-learning-guide/”>English Blockchain Learning Guide</a>, <a href=”https://edukatesg.com/master-blockchain-learning-guide-chinese/”>Simplified Chinese Learning Guide</a> and <a href=”https://edukatesg.com/master-blockchain/”>main Blockchain hub</a>.
Read <a href=”https://edukatesg.com/2026/10/13/how-blockchain-works-the-complete-system/”>The Complete System</a>, <a href=”https://edukatesg.com/2026/10/13/how-blockchain-works-closed-loop-system/”>Closed Loop System</a> and <a href=”https://edukatesg.com/2026/10/15/how-blockchain-works-what-blockchain-can-and-cannot-prove/”>What Blockchain Can and Cannot Prove</a> for the wider architecture and evidence boundaries.
Sources and scope
The relevant source is <a href=”https://www.pdpc.gov.sg/help-and-resources/2022/07/guide-on-personal-data-protection-considerations-for-blockchain-design”>https://www.pdpc.gov.sg/help-and-resources/2022/07/guide-on-personal-data-protection-considerations-for-blockchain-design</a>, with broader technical context in <a href=”https://csrc.nist.gov/pubs/ir/8202/final”>NIST IR 8202</a>. The story and activities are fictional teaching examples; the exact properties of a real blockchain depend on its implementation.
Takeaway: A public blockchain can make transactions independently checkable, but that visibility can also reveal patterns about people. A pseudonymous address is not the same as an anonymous person, and putting a hash on a ledger does not automatically make sensitive data safe.