VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Learn how to Use Bitcoin, Cryptocurrencies and Blockchain Technology for Students | Digital Identity, Privacy and Zero-Knowledge Proofs

Three students in school uniforms work through open books at a classroom table, with textbooks and stationery nearby and study notes on the whiteboard behind them.

Digital identity is the way a system determines who a person or organisation is; authentication checks whether a person controlling an account can prove authorised access; privacy asks how much information should be disclosed. Blockchain, digital signatures and some zero-knowledge-proof methods can help with specific parts of these problems, but none replaces trustworthy institutions, safe devices or careful handling of personal data. Students can learn all these ideas using invented credentials without creating crypto wallets or sharing personal documents.

For Singapore parents, this subject connects directly to Singpass, OpenCerts, school certificates and cyber wellness. GovTech describes Singpass as Singapore’s national digital identity service, but Singpass is not Bitcoin and should not be described as a cryptocurrency wallet. The World Wide Web Consortium’s Verifiable Credentials Data Model 2.0, published as a Recommendation in May 2025, distinguishes issuers, holders and verifiers, and supports privacy-enhancing techniques such as selective disclosure. The educational aim is to share only what is needed, identify trustworthy sources, and recognise that a cryptographic proof still depends on its assumptions.

  • Distinguish identity proofing, login authentication, authorisation and verifiable claims.
  • Understand issuers, holders, verifiers and how an academic credential can be checked.
  • Learn what selective disclosure means and why some zero-knowledge proofs can confirm a statement without revealing all supporting details.
  • Separate Singapore’s Singpass, OpenCerts, digital signatures and public blockchains without assuming they use identical technologies.
  • Recognise privacy threats from repeated identifiers, public transaction records, fake verification websites and oversharing.
  • Complete classroom exercises with fictional student records, including a need-to-know checklist and a safe parent conversation.

Identity, authentication and authorisation are three different questions

Imagine a visitor at a school library. The librarian first asks what identity the visitor claims; the system may verify that identity through an official or institutional process. Next the visitor logs into an account, perhaps with a password or a secure authenticator. Finally the system checks whether that account is allowed to borrow a particular book. These are related steps, but they answer different questions: Who is this? Can the claimant prove control? and What may they do?

A child who mixes these concepts might believe that knowing a wallet address proves someone’s legal name or that possessing an NFT automatically grants entry to any club. Neither conclusion follows. A blockchain can verify certain cryptographic operations without identifying a real-world person. Conversely, a school can know exactly which student borrowed a book while using a conventional database with no blockchain involved.

What is identity proofing?

Identity proofing is a process of establishing that an applicant corresponds to the identity they claim, at a level appropriate to the context. It may use documents, official records, trusted institutions or other methods. NIST’s Digital Identity Guidelines address identity proofing and enrolment as separate tasks from login authentication. This distinction matters because a correctly functioning login screen does not independently establish that the person opening an account supplied truthful identity information.

In an invented classroom scenario, Student C claims to be the captain of a club. The teacher checks the official club list before issuing a certificate. The certificate may later help C prove the role, but it cannot repair a mistake in the original club list. An identity system needs reliable records at the beginning, not only strong cryptography afterward.

What is authentication?

Authentication checks whether a claimant can demonstrate control of an authorised account or credential. A password is one type of secret; a passkey or other cryptographic authenticator can provide different protections. NIST’s 2025 authentication guidelines discuss phishing resistance and authenticator assurance. The correct school lesson is that different authentication methods have different properties, not that every login must be connected to a blockchain.

Students sometimes call every verification step a password check. In reality, a service might use a cryptographic challenge, a device, a biometric unlock or a combination of factors. Biometrics used locally to unlock a cryptographic credential do not make a public blockchain proof of the user’s legal identity. Parents should teach children to recognise what the app is asking them to approve and which organisation is requesting it.

What is authorisation?

Authorisation determines what an authenticated account may do. A student may log in successfully but still lack permission to change another student’s grades. A teacher may read a class list but not alter school-wide examination results. A librarian may record a loan but not issue a diploma. Access control prevents an authenticated user from acting beyond the permissions assigned to their role.

Use a classroom role table with fictional users. The visitor can view a list of public books, a club member can request a book, a librarian can approve a loan and a principal can authorise specified administrative decisions. Ask what happens if the visitor obtains the librarian’s password. The risk is not merely a failed identity system but stolen account control and excessive privileges.

Why Singapore’s Singpass is a useful comparison

GovTech’s September 2026 Singpass information describes secure access to government and business services and features such as authentication, document signing and data sharing. The Singpass app also presents information from government sources and can ask a user to review requested data before consenting to share it in supported workflows. Its usefulness comes from institutional integration, controls and service design, not from the speculative value of a token.

A student should never be asked to share actual Singpass credentials, scan a live login QR code for the class, reveal a six-digit code or perform a real transaction to complete this lesson. Instead show an invented screen reading ‘School Library Identity Service’ and ask what information is requested, why it is needed and what independent evidence would establish that the service is genuine.

Singpass is not a Bitcoin wallet

A Bitcoin wallet manages information used to authorise cryptocurrency transactions under Bitcoin’s rules. Singpass serves digital identity and access to services in Singapore. The fact that both can involve cryptography, smartphone authentication and QR-code interactions does not make their purposes or legal structures equivalent. Parents should resist online claims that cryptocurrency is required to activate a Singpass account or unlock an official identity service.

A QR code is merely an encoded instruction or identifier and can direct a device to many kinds of applications. It does not prove that the destination is legitimate. In a safe lesson, the QR code is printed as a picture or replaced with an invented text label, and pupils practise asking ‘Who issued this request?’ before using an app.

The issuer, holder and verifier model

  • Issuer: the school or organisation authorised to make a particular claim, such as completing a course.
  • Holder: the individual or agent who holds the issued credential and can present it under permitted conditions.
  • Verifier: the employer, university or other recipient checking a particular claim and its evidence.
  • Subject: the person or thing described by the credential; it is not always the same person who physically holds the file.
  • Trust context: the reasons the verifier considers a specific issuer appropriate for the claim being made.

W3C’s Verifiable Credentials model uses these distinctions because a credential is not simply an image. It must carry information that can be secured and checked according to a specified mechanism. The verifier also has to decide whether the issuer is qualified to make the assertion. A signed statement from a fictional person does not become a recognised university qualification just because the signature is mathematically valid.

An example with a fictional school certificate

A student called Person A receives a certificate saying ‘Completed Introduction to Robotics’. The fictional school signs or securely issues that claim. Later, a contest organiser asks whether A completed the course. The organiser should check that the credential comes from an accepted issuer, has not been altered and remains valid under its rules. The organiser may have no need for A’s home address, full school history or family income.

This is a central privacy insight. A request to verify one claim does not justify collecting every other piece of personal data. A system may be technically capable of sharing a full transcript, but the responsible design asks what information is proportionate to the task. Students can learn this principle without handling genuine certificates.

Selective disclosure: prove the relevant part, not everything

Selective disclosure allows the holder of a credential, where the specific credential and proof technology support it, to reveal a subset of its claims rather than the entire record. Suppose a fictional student certificate records first name, school, age, club membership and award status. A science-fair organiser only needs evidence that the holder qualified for the junior division. A privacy-conscious presentation could disclose a suitable eligibility claim without exposing the whole certificate.

Not every credential format supports selective disclosure automatically. Some schemes reveal all claims, some can selectively disclose signed fields and some use proofs for specific properties. The choice depends on issuance, software, credential format and cryptography. Parents should not assume that any app branded ‘Web3’ or ‘decentralised identity’ offers private selective disclosure by default.

What is a zero-knowledge proof?

A zero-knowledge proof is a cryptographic technique by which one party can convince another of a specified statement without revealing the secret witness that makes the statement true, subject to the properties and assumptions of the proof system. It is not simply hiding a document behind a password. It is a method of verifying a statement while limiting what is learned from the proof. Different protocols have different efficiency, trust and privacy characteristics.

W3C’s May 2025 Verifiable Credentials Data Model 2.0 describes zero-knowledge proofs as one possible securing method for privacy-enhancing presentations. For example, the holder may prove an age threshold rather than disclose a complete birth date, where the issuer and cryptographic method support that operation. This does not imply that every credential wallet, identity system or blockchain automatically uses zero-knowledge proofs.

The age-threshold example

Imagine a fictional service for adults requiring a minimum age of 18. A conventional ID check might reveal a person’s full date of birth and other identity fields. A suitable privacy-preserving credential system could, under its specific design, let the holder prove that the age requirement is satisfied without revealing the exact birth date to that verifier. The validity of the proof still depends on trustworthy issuance and correct verification.

The class should not use actual children’s dates of birth, identity-card numbers or real identity documents. Create three invented ages and ask what each applicant must prove under different rules. The exercise demonstrates data minimisation. It is not an instruction for minors to evade age gates, and a proof showing one condition is satisfied is not authorisation to use an otherwise restricted financial service.

A lock-and-key story is only an analogy

An educator might describe a door whose key is hidden, yet a person can demonstrate an ability to open it repeatedly. The analogy helps beginners imagine proving knowledge without revealing a secret, but it is not a formal proof of zero knowledge. Real systems require precise completeness, soundness and zero-knowledge properties under mathematical definitions and a specified threat model.

Older learners can read a conceptual explanation of interactive proofs and distinguish the honest prover’s statement from what a dishonest prover might attempt. The educational objective is to know why proof design matters, not to implement a production-ready cryptographic protocol or handle identity secrets in a school assignment.

Why hashes are not zero-knowledge proofs

A cryptographic hash can provide a data fingerprint, but publishing a hash does not automatically create a zero-knowledge proof about an arbitrary private fact. Some supposedly anonymised data can be guessed or matched from small input spaces. For example, hashing a list of possible birth dates with a basic public algorithm may allow someone to test guesses and recover likely information. Students should not assume that a hashed personal identifier is inherently anonymous.

This is a useful Computing distinction. Hashes, digital signatures, encryption, selective disclosure and zero-knowledge proofs each have different purposes. They can be combined in a system, but one name cannot be substituted for another. Parents should be cautious about marketing that promises absolute privacy from a generic ‘encrypted blockchain’ without describing the actual data flows.

Digital signatures prove control, not every real-world fact

A valid signature can help show that someone controlling a particular signing key approved data under a given verification method. It does not necessarily identify the legal person holding the key or prove that an issuer’s underlying claims are true. If an unauthorised person obtains the key, technically valid signatures may be produced without rightful permission. Trustworthy key management and institutional processes remain necessary.

The classroom model can use a sealed envelope as a pretended signing key and a unique class stamp as a signature. The teacher should explicitly note that the stamp does not reproduce real cryptographic security. A student can understand the relation between authorisation and verification without generating a wallet seed phrase or attempting to sign a financial transaction.

What is a decentralised identifier?

Decentralised identifier designs, often abbreviated DIDs, aim to provide identifiers that can be resolved to associated verification methods or service metadata under particular standards and method rules. A DID does not automatically reveal someone’s legal identity, and creating one does not make all of that person’s claims trustworthy. Different methods depend on different registries, governance arrangements or networks.

W3C’s credential model allows issuer and subject identifiers, but verifiers still need a trust policy and must handle privacy carefully. Reusing the same stable identifier across many unrelated services can enable tracking and correlation. Some designs use pairwise identifiers or limited disclosures to reduce that risk. Children should not be asked to create live decentralised identifiers as a classroom requirement.

Why a public blockchain creates traceability

Many public blockchains deliberately make transaction activity inspectable. Addresses may be pseudonymous, but repeated use and outside information can link transactions to real identities. This means an identity system that simply writes every student’s name, grade and age on a public ledger would be deeply problematic. Public integrity and personal privacy are separate design problems that need to be solved together.

Ask students why storing a full academic transcript in permanent public records would be risky. Future employers, advertisers and strangers might gain access to information unrelated to the original purpose. Correcting inaccurate grades could also be difficult if the record is designed to be immutable. A better architecture may store personal information securely off-chain while using limited proofs where justified—or omit blockchain entirely.

Privacy includes metadata, not just the visible fields

Even if a proof hides a person’s name or date of birth, repeated presentation of a stable identifier, signature value, timestamp or network address can allow different services to correlate the person’s activity. The W3C Recommendation specifically discusses correlation risks and advises designs that reduce unnecessary disclosure and repeated identifiers. Zero-knowledge techniques alone do not guarantee complete unlinkability in every implementation.

This is an advanced but teachable principle: a digital system can reveal information through patterns as well as content. If a student uses the same supposedly anonymous pseudonym for every club, library and contest, observers may connect the records even without the real name. Different technical and organisational controls may be needed to protect privacy.

Why an issuer’s reputation remains important

An anonymous organisation can produce a valid cryptographic signature for the claim ‘This student is the world’s best scientist’. The signature might correctly prove that the anonymous organisation issued the text, but it does not make the statement credible. The verifier must decide what qualifications, evidence and authority the issuer has. Cryptography improves verification of provenance; it does not replace social and institutional trust.

In the context of education, a credential issued by a recognised university has different significance from a badge created by an unknown website. Even the university’s claim may need clarification about programme level, assessment and accreditation. Parents should therefore evaluate the underlying qualification as carefully as the verification mechanism.

Singpass, OpenCerts and public blockchains: what is shared?

These systems illustrate different uses of identity information, cryptography and verification. Singpass helps residents access services and authorise particular actions. OpenCerts supports verification of educational credentials. Public blockchains can record transactions and other state. Some verifiable-credential architectures may use blockchains as registries, while others do not need them. The presence of cryptography in each does not make their architectures identical.

A comparison chart should include purpose, operator or governance structure, information being protected, authentication method, privacy design and correction process. Students should avoid describing Singpass as ‘on Bitcoin’ or describing an OpenCerts certificate as a tradable cryptocurrency. Both statements confuse technological building blocks with actual products.

How Singapore’s PDPA informs privacy reasoning

Singapore’s Personal Data Protection Commission explains that the PDPA includes obligations concerning consent, notification, purpose limitation, protection, retention and access or correction, subject to the law’s scope and exceptions. These are organisational and legal responsibilities, not cryptocurrency protocol settings. A blockchain label does not automatically make a system compliant or relieve it of the duty to handle personal data responsibly.

A teacher can ask whether a tuition provider needs a student’s full identification record merely to issue a mock attendance badge. If a fictional student ID and a simple completion status suffice for the exercise, collecting additional personal information is unnecessary. This is data-minimisation reasoning grounded in ordinary privacy principles rather than a claim that every legal situation has the same solution.

A safe invented-identity classroom project

  • Create a fictional school named Northstar Academy and three invented student letters A, B and C.
  • Issue an imaginary Robotics Completion credential to A and B, leaving C without the award.
  • Create a mock employer that only needs to know whether the holder completed Robotics.
  • Give each fictional student a paper envelope representing a private credential store.
  • Require the verifier to check that the school actually issued the record and that the record was not altered.
  • Add one revoked credential and ask why original issuance is not the same as current validity.
  • Ask what extra data the employer does not need, such as home address, birthday or unrelated school grades.

Do not generate genuine Singpass credentials, solicit real identity documents or place student personal information on a public website. The activity deliberately uses plain paper. It teaches the correct questions before any computer-security implementation is considered.

A selective-disclosure card game

Write four imaginary facts about Student A on a folded card: school club, favourite sport, fictional birth year and completed course. An organiser asks only for proof of the completed course. Have the student decide which fields should be disclosed. This represents data minimisation, not actual cryptographic selective disclosure. Next explain how a properly engineered verifiable-credential mechanism might support revealing only a specific claim while checking the issuer’s proof.

Older students can extend the game with a policy requiring an age threshold. Ask what a system must verify, whether the issuer is trustworthy and what residual information could still leak. The answer should be that privacy depends on the full credential, proof format, identifiers and verification context. There is no guarantee that a paper exercise reproduces formal zero knowledge.

Why a verifier should not ask for more than necessary

An organisation can reduce privacy risks by requesting only information relevant to its purpose. If a sports event needs confirmation that a student belongs to an eligible age category, it may not need a copy of the family’s full identity documents. If a library needs proof of membership, it may not need the member’s exam scores. This principle protects both users and organisations by reducing unnecessary sensitive data handling.

W3C’s Verifiable Credentials Recommendation encourages verifiers to request only necessary information and encourages credential holders to understand and control what they present. These are design recommendations, not evidence that every deployed service follows them. Parents should still review real requests and ask why the information is being collected.

Phishing resistance and fake login screens

A scammer may create a realistic login page to steal passwords or one-time passcodes. NIST’s 2025 authentication guidance distinguishes phishing-resistant methods from methods that depend largely on a user recognising an impostor. A strong authentication method helps, but users must still verify transaction context, protect devices and avoid authorising unexpected requests. An apparently genuine QR login can be part of a fraudulent flow.

Students should practise refusing a message that says, ‘Scan this QR code and approve a Singpass request to receive free crypto.’ The supposed reward is unrelated to the requested authentication. Do not scan or approve anything. Navigate independently to official services and tell a trusted adult. In Singapore, scam reporting and guidance are available through ScamShield.

The difference between signing a document and signing a payment

A digital signature can bind a signer to specific data under an authentication and legal framework. But signing an official document and authorising a cryptocurrency transfer are distinct applications with different consequences and interfaces. A student who sees ‘sign’ on a wallet prompt should not assume it is harmless. Some wallet signatures or approvals can grant access or permissions that have substantial consequences.

For this lesson, use entirely fictional signature cards and do not interact with live cryptocurrency approval screens. The general safety lesson is that an authorisation should be understood in context: what is being approved, by whom, to which service, and with what scope. If a child cannot answer those questions, they should not proceed.

A fake credential issuer and an impressive logo

A website can display a university’s logo, a QR pattern and an image claiming that a credential is blockchain verified. None of those features by itself proves that the university issued the credential. A trustworthy verifier needs a suitable authenticating mechanism and a reason to trust the issuer. Some credentials can be cryptographically valid but self-asserted by an unknown party, which gives them limited evidentiary weight.

A parent can turn this into a fact-checking activity by giving the child two invented websites with similar logos but different domain names and issuer descriptions. Ask which independent official source should be consulted. The child should conclude that the real institution’s own website is a sensible starting point and that no one needs to enter passwords or payment details to satisfy the fictional exercise.

Why private identity credentials do not need a coin

A verifiable-credential system can use digital signatures, trusted registries and ordinary secure infrastructure without issuing a cryptocurrency or requiring its users to buy tokens. W3C allows various registry and securing mechanisms; a blockchain is one possible component rather than an obligatory requirement. Students should reject claims that a token purchase is necessary to obtain a normal school certificate unless the legitimate issuer’s actual policy proves otherwise.

This helps parents separate genuine digital innovation from token marketing. A system can use cryptography to make records verifiable while remaining an ordinary public-service or education product. The technical value is in trust, integrity and appropriate disclosure, not the market price of a speculative coin.

What if a credential must be corrected?

A student’s name might be misspelled or an award withdrawn after an assessment error. A robust credential system needs an authorised process to correct the claim, supersede an old credential or change its validity status. A public append-only audit trail may record the history, but the user still needs a clear current document and a legitimate appeal route. Immutability is not a substitute for institutional accountability.

In class, create certificate C-001 and intentionally record the wrong fictional course. The issuer later issues C-002 as the corrected credential and revokes C-001. Ask why both the new proof and the change of status matter. This illustrates an honest correction, not an attempt to hide history. Digital-record governance should support fairness as well as tamper evidence.

Why data minimisation is good engineering

Collecting unnecessary personal data adds storage, security, access-control and breach risks. If a school event only needs a participant count, there is little reason to build a permanent publicly accessible list of every participant’s full details. Engineers should define the purpose of each field before collecting it. This habit makes systems simpler to audit and easier to explain to parents.

A learner can review an invented signup form and cross out fields that are not relevant to the stated task. If the form asks for a parent’s bank password to join a robotics club, the answer should be an emphatic rejection. Data minimisation and fraud prevention reinforce one another: a legitimate service should be able to explain what information it needs and why.

Age-by-age learning sequence

  • Primary school: identity labels, privacy, passwords, asking permission and knowing when information should not be shared.
  • Lower secondary: identity versus authentication, issuer versus verifier, digital-signature purpose and fake login screens.
  • Upper secondary: selective disclosure, stable identifier correlation, credential revocation and basic cryptographic proofs as concepts.
  • JC and advanced Computing: completeness, soundness and zero-knowledge properties, credential formats, trust registries and formal privacy threat models.
  • Parents: protect Singpass and school records, verify official domains and use only fictional data in learning exercises.

Misconceptions that students should be able to correct

  • ‘Every blockchain address identifies a person’s legal name.’ Incorrect: an address is not a complete identity proof.
  • ‘A password reset gives control of every private key.’ Incorrect: self-custody key management differs from normal account recovery.
  • ‘A hash of a birth date is automatically private.’ Incorrect: it may be guessable or correlatable.
  • ‘A zero-knowledge proof means the verifier learns absolutely nothing about anything.’ Incorrect: it proves a defined statement and the wider protocol can reveal metadata.
  • ‘All verifiable credentials use a blockchain.’ Incorrect: there are multiple securing and registry mechanisms.
  • ‘An official-looking logo authenticates an issuer.’ Incorrect: cryptographic and institutional checks matter.
  • ‘A valid signature means the underlying statement is true.’ Incorrect: provenance and truth are different.
  • ‘A Singpass login is a Bitcoin payment.’ Incorrect: they serve different purposes.
  • ‘An unchangeable ledger can never contain an error.’ Incorrect: false original inputs remain possible.
  • ‘Privacy rights vanish when a document is cryptographically verifiable.’ Incorrect: lawful data handling remains essential.

Practice questions with model answers

  • What is identity proofing? Establishing an applicant’s claimed identity through an appropriate process.
  • What is authentication? Checking control of a recognised account or credential.
  • What is authorisation? Checking whether that account may perform a given action.
  • Who is the issuer of a fictional course certificate? The organisation responsible for issuing the claim.
  • Who is the verifier? The recipient checking the credential and deciding whether to trust the issuer.
  • What is selective disclosure? Revealing only some claims where the credential system supports it.
  • Can a zero-knowledge proof eliminate all metadata risks? No.
  • Does hashing a simple date of birth guarantee anonymity? No.
  • Must a verifiable credential be issued on Bitcoin? No.
  • What should a child do with an unexpected Singpass approval request? Do not approve; independently verify with a trusted adult.

FAQ for Singapore parents

Is Singpass a blockchain product?

Singpass is Singapore’s digital identity service, not a cryptocurrency wallet. Do not assume it uses Bitcoin just because it employs cryptographic security.

Does my child need a Singpass account for the lesson?

No. Use mock screens and invented identities rather than live authentication requests.

What does a digital certificate verify?

Depending on the scheme, it can support checks of issuer, integrity, subject claims and status. Its real-world meaning still depends on the issuer and context.

Is selective disclosure always available?

No. It depends on the credential format, cryptographic method and implementation.

Does zero knowledge mean no data at all is shared?

Not necessarily. The verifier learns the defined statement and the protocol may reveal identifiers or metadata.

Can a blockchain prove someone’s age?

A properly issued credential and suitable proof system may help establish an age condition, but an arbitrary wallet address does not prove age.

Why should children not share wallet addresses publicly?

Public transaction information can be linked with outside data and create privacy or targeting risks.

Are identity data and passwords the same thing?

No. Identity data describe a person, while authentication credentials help prove account control.

Can a digital signature be stolen?

Private signing credentials can be compromised, and a captured or misused authorisation can have serious consequences.

Is a verifiable record automatically truthful?

No. A recognised issuer and its underlying verification process still matter.

How does PDPA relate?

Singapore’s data-protection rules address lawful collection, use, disclosure, security and other duties within their scope.

Do parents need to put students’ certificates on public blockchains?

No. Use official credential workflows and protect personal educational information.

What is the easiest practical assignment?

A paper exercise in which one verifier requests only a course-completion claim and the student refuses to reveal unnecessary fields.

What is the most important scam warning?

Unexpected requests for Singpass approvals, OTPs, private keys or payments are reasons to stop and verify independently.

Can zero-knowledge proof systems have vulnerabilities?

Yes. Incorrect code, weak assumptions, malicious issuers or metadata leaks can undermine privacy and security.

What is the final learning objective?

A student can distinguish identity, access, proof and trust while sharing the minimum necessary information.

A five-lesson family learning programme

Lesson one: use fictional cards to separate identity, authentication and authorisation. Lesson two: create a pretend school certificate and check issuer, integrity and validity. Lesson three: play selective disclosure by sharing only one necessary field. Lesson four: examine fake login and credential-verification messages. Lesson five: compare Singpass, OpenCerts and a public blockchain to explain why their purposes and privacy requirements differ.

After the fifth session, ask the child to write a one-page parent guide: ‘What should a digital service be allowed to know about me?’ A strong answer will include a legitimate purpose, a trustworthy requester, appropriate permissions, secure data handling and the option to decline unnecessary requests. The assignment is useful even if the child never owns a cryptocurrency.


Verified primary references

Related eduKateSG lessons

Reviewed 20 November 2026. All class identities, ages and credentials are fictional. This guide explains concepts and documented standards, not a claim that any particular Singapore identity system uses zero-knowledge proofs or is built on Bitcoin. No login attempts or personal financial data are needed.