Bitcoin’s rules are not set by a schoolteacher, a central bank or the person who originally invented it. The system runs through software and network participants, including validating nodes that check transactions and blocks, miners that propose new blocks, and developers who write and review code. A single group cannot simply publish a new rule and force every participant to accept it. For a ten-year-old, the most useful idea is that a shared system needs people to agree on which rules they actually follow.
Singapore parents can explain that process through classroom games, paper-ledger exercises and respectful discussions about evidence. A person may publish a proposed Bitcoin improvement, but publication does not mean universal acceptance or a government endorsement. Children do not need to run a node, buy mining equipment or hold cryptocurrency to understand consensus. The objective is to distinguish proposing a rule, checking a rule, choosing software and making a real financial decision, while remembering that the existence of agreed technical rules does not guarantee Bitcoin’s price or protect someone from scams.
- Main idea: Bitcoin operates through independently followed and checked software rules
- Key roles: developers propose code, miners propose blocks and full nodes validate rules
- Important word: consensus describes agreement about the rules and accepted record
- Source-checking rule: a public BIP proposal is not automatically adopted
- Parent experiment: write a pretend class rule, try a conflicting version and compare results
- Singapore protection: Bitcoin is not Singapore legal tender and is not a guaranteed investment
- Child outcome: explain who can propose change and why a proposed rule need not be accepted
Why do any games need rules?
A classroom game becomes confusing if each student invents a different scoring system. One person might say a star is worth two points while another says it is worth five. Even if everyone acts politely, the group’s totals will disagree unless the participants share compatible instructions. Rules give people a way to decide which results count.
Bitcoin faces a far more complex version of the coordination problem. Participants may be spread around the world and do not all know or trust one another. Software rules help them check whether transactions and blocks are valid. A child can understand this without knowing programming languages or using financial software.
A computer can follow instructions consistently
Computer software is built from instructions that specify what to do with information. In a financial network, it matters whether different machines follow compatible validation rules. If one machine accepts a transaction that another rejects, the participants may disagree about what the authoritative record shows.
Try a paper instruction card: ‘A person may not spend more imaginary tokens than they have.’ Give the child four pretend transaction examples and ask which obey the rule. If the instructions are clear and the arithmetic is accurate, different family members can reach the same conclusion.
What does decentralised mean?
In a decentralised network, record checking and participation are not exclusively controlled by one central operator. Bitcoin is designed so that many participants can independently verify its shared transaction history according to the rules they run. This is different from a conventional bank ledger maintained under a particular institution’s authority.
Decentralisation does not mean ‘nobody has influence’ or ‘all participants do identical jobs’. Developers, miners, wallet providers, businesses and node operators can influence the network in different ways. The child should avoid simplistic claims that a single person controls everything or that no one has responsibilities.
What does a full node do?
A Bitcoin full node runs software that checks blocks and transactions under the rules it follows. When it receives a block that violates those rules, it can reject that block rather than merely trusting the sender’s confidence. This independent validation is an important part of the network’s design.
In a class game, appoint two checkers. Each uses the same written rulebook but independently checks a submitted score sheet. If both identify a transfer of more points than a student owns, they can reject it. The analogy omits cryptographic signatures and proof of work, but illustrates why independent checking can matter.
Why aren’t all nodes identical?
Different network participants may use different software implementations, settings, connection policies or versions. Nodes still need to follow compatible consensus rules if they are to agree on the valid chain. A student should understand that the word node describes a role rather than a promise that every computer has the exact same appearance or configuration.
A family exercise can use two types of calculator for the same sums. Their screens may look different, but if they apply ordinary arithmetic correctly, they agree on the result. This analogy is simple and imperfect, but it shows that interface differences do not necessarily mean disagreement on the underlying rules.
What does a miner do?
Bitcoin miners use computing resources in a proof-of-work competition to propose candidate blocks. A block may include transactions that miners selected from those available to them, and the successful valid block may carry a permitted reward. Miners are not the sole judges of which blocks comply with Bitcoin’s rules.
Explain that a student who writes a class ledger page is not automatically allowed to invent extra imaginary money. The checker can refuse a page that violates the rules. In the real Bitcoin system, proof of work and distributed network validation add significant technical complexity.
Can a miner change the supply limit?
A miner can attempt to publish a block claiming an excessive reward, but validating nodes using rules that limit the subsidy can reject it. Mining power alone does not make an otherwise invalid payment or issuance automatically acceptable to every participant. This is why it is misleading to say that miners can print unlimited Bitcoin.
Use a pretend example: the class rule allows a recorder to add only two bonus points. The recorder claims 200 instead. Ask whether the page follows the announced rule. No. The class should reject it under the exercise’s rules even if the recorder spent a long time preparing it.
What do developers do?
Developers can write, review, test and suggest changes to Bitcoin-related software. They may also document bugs, improve performance or contribute translations and educational material. The Bitcoin Core project describes a broad open-source community that includes many kinds of contributors rather than a single company issuing commands.
A software developer’s patch is not automatically a network-wide rule change. People choose which software to run, and proposed changes to consensus rules require participants to adopt compatible behaviour. This distinction is valuable in computing education: making code available is different from getting the community to use it.
Does a popular developer control Bitcoin?
A respected contributor can influence public discussion, but influence is not the same as absolute authority. Bitcoin Core maintainers can manage a software project’s development workflow; they cannot force every node operator in the world to install a new version or accept incompatible consensus rules.
Think of a school club in which an experienced pupil recommends changing a game. Other students may listen carefully because the pupil is knowledgeable. Yet the recommendation is still not the same thing as everyone agreeing to play the changed rules. The model helps separate expertise from compulsory obedience.
What does open source mean?
Open-source software has published code that can be inspected and, subject to its licence, changed and shared. Bitcoin’s open-source tradition allows contributors to review implementation details and discuss possible improvements. Openness creates opportunities for scrutiny but does not mean every person reading the code can instantly understand every technical or security implication.
For a child, compare a recipe kept secret with one published in a cookbook. The public recipe can be discussed, tested and adapted. But a badly written recipe can still make a poor cake, so publication alone is not proof of quality. The child learns to distinguish transparency from guarantees.
Why review matters before software is released
A software change can have unintended consequences. Developers and reviewers may inspect code, test scenarios, consider compatibility and discuss whether a change would create security or operational problems. Open-source review is a process rather than a magic stamp certifying that no bug can exist.
A family can simulate review with two versions of a pretend rulebook. One sentence says ‘each student may send any number of points’ and another says ‘each student may only send available points’. Ask what problems the first version creates. A child who checks consequences before agreeing to a new rule is practising the mindset behind careful review.
What is a Bitcoin Improvement Proposal?
A Bitcoin Improvement Proposal, or BIP, is a document used to propose or describe a technical feature, standard or related process within Bitcoin’s ecosystem. BIPs help organise public discussion and provide a written history of ideas. The BIPs repository explicitly warns that publishing a BIP does not itself demonstrate community consensus or imply that a proposal will be adopted.
Ask the child to write a fictional School Improvement Proposal proposing that students use coloured scorecards. The proposal includes a reason and examples. It may be well written but still require discussion and adoption. Calling the paper an improvement proposal does not make the change automatic.
Can anyone propose an idea?
People can suggest ideas and contribute to technical discussions, but useful network-wide proposals need careful evidence, clear design and review. The public BIP process describes how proposals are prepared, discussed, submitted and archived. A ten-year-old does not need to follow detailed mailing lists or software repositories.
A child can practise the spirit of a proposal by writing a sentence about what problem they wish to solve, how the proposed rule would help and what might go wrong. That is appropriate classroom design thinking without exposure to technical tools or financial activity.
What is consensus?
Consensus in this setting is the practical agreement participants need over valid rules and the accepted transaction history. Bitcoin’s design relies on compatible validation behaviour and a mechanism for deciding which valid chain has accumulated the relevant work. It is not the same as taking a simple classroom majority vote on every single transaction.
For age ten, say that the participants must be able to agree on the rules by which records are checked. A child can explore this by having different family members review the same pretend ledger. When someone uses a different rule, the results may diverge. The exercise shows why agreement on rules comes before agreement on outcomes.
Does Bitcoin use one vote per person?
No. Bitcoin’s consensus and mining processes are not a normal election in which each human participant has one ballot that decides the next protocol rule. Proof of work helps secure the chain, while validating nodes enforce the rules they follow. Real governance involves technical proposals, economic participants and adoption decisions.
An age-ten analogy can distinguish a vote from a check. If twenty children vote that 3 + 4 = 9, the vote does not change arithmetic. Similarly, a node’s validation is about whether a block satisfies rules, not whether its creator is popular. Avoid telling the child that technical coordination is literally identical to school democracy.
What if two people disagree on a rule?
Disagreement may remain a discussion without changing network behaviour. Participants can also choose to adopt different software. If the differences are incompatible at the consensus level, networks may diverge rather than continuing to share one accepted record. The details depend on the particular change and how people respond.
Use a fictional board game. Some children play with a maximum of ten points and others change the maximum to fifteen. If they cannot agree, they may need separate scoreboards. A child can see why two versions of a rulebook might no longer support one coherent game.
What is a fork?
A fork is a term used for forms of divergence in blockchain-related software or network histories. In discussions of consensus changes, a hard fork generally broadens which blocks can be considered valid relative to previous rules, while a soft fork adds restrictions compatible with certain older-rule validations. The technical details are more complicated than a simple drawing.
For ten-year-olds, a fork can be introduced as a path splitting when groups stop using compatible instructions. Do not imply that every software update causes a permanent new cryptocurrency. Many updates are ordinary software improvements, and temporary chain reorganisations have their own technical meaning.
What is a soft fork?
In simplified terms, a soft fork changes consensus rules so that some blocks previously allowed are no longer allowed, while new valid blocks remain valid under the older rule set in the relevant respect. It is a stricter-rule change. The practical adoption and network behaviour can still be complex.
Use an imaginary dress rule. The original school club permits red or blue shirts. The new club rule permits only blue shirts. A blue shirt satisfies both rules, while a red shirt fails the stricter rule. This is only an analogy to narrower validity conditions and does not explain every Bitcoin soft-fork deployment.
What is a hard fork?
A hard fork, in simplified consensus terminology, permits some blocks that would have been invalid under the previous rules. Participants enforcing the old rules would reject those blocks. If some adopt the new rules and others do not, network compatibility and the accepted history can diverge.
Consider a fictional club that once limited transactions to ten points but now allows twelve. A transaction worth eleven violates the old limit and satisfies the new one. Students can see why an older checker and a newer checker might disagree. This example is not actual Bitcoin code.
Are forks always good or always bad?
No. A change may be proposed to fix a problem, add a feature or support a new design, but each proposal raises questions about security, complexity, coordination and unintended consequences. Disagreement can arise even among knowledgeable people acting in good faith. A ten-year-old can learn to listen to reasons without needing to decide a complicated technical dispute.
Ask a child what evidence they would want before changing a rule used by many people. They might mention whether the new rule solves a real problem, how it affects others and what happens if participants refuse it. These are sound questions for school teamwork and computing.
Why is backwards compatibility useful?
Backwards compatibility means new software or formats are designed to keep working appropriately with older participants or systems in a defined way. In a widely used network, reducing unnecessary disruption can be valuable. The exact meaning depends on the type of change and what older software understands.
Use a pretend worksheet template. If a teacher changes the form so that yesterday’s answer sheets become unreadable, students may lose time and need new instructions. A change that preserves expected behaviour can be easier to adopt. Compatibility can be important, but preserving it is not automatically the only objective in every technical decision.
What happens when users refuse an update?
Users or operators may choose not to install a new software version. What happens next depends on whether the update changes consensus rules and whether the network remains compatible. In some circumstances, people continue participating under shared rules; in others, a split or other disruption may occur.
The Bitcoin Core project’s own explanation emphasises that participants retain a choice about which software they run. This supports an important distinction: software maintainers can release a version, but they cannot simply compel every network participant to install it. Children can grasp that choice without needing to study the complexities of software deployment.
Who makes decisions about Bitcoin’s website?
A website describing Bitcoin is not the network itself. Bitcoin.org explains that it is an independent open-source information project and cannot speak with exclusive authority for the entire Bitcoin network. Its editors and maintainers can manage website content, but that does not give them the power to set network consensus rules.
Show a fictional school’s website and a school’s rulebook. A person who edits the website’s home page does not automatically have authority to change the rules of every club. Ask the child to distinguish controlling information about a system from controlling every participant’s behaviour.
Is a wallet provider the same as Bitcoin?
A wallet service or software application can help users interact with Bitcoin. It may set its own interface, customer support terms and operational procedures, but those business or software choices are not identical to the underlying Bitcoin consensus rules. An attractive app is not proof of a safe asset or honest provider.
A child can understand this through a calculator. Different calculator brands may display arithmetic in different styles, but ordinary mathematical rules are not owned by a particular device maker. The analogy has limits, but it illustrates how an interface can be separate from a rule set.
Does a large mining company control every other node?
A mining company may have significant computing power and economic influence, but that does not mean it can force every independently validating node to accept blocks violating the nodes’ consensus rules. A network can nevertheless face serious security or coordination risks if mining power becomes overly concentrated; decentralisation should not be oversold as absolute immunity to influence.
Parents should present both ideas together. Independent validation is an important safeguard, while concentration and incentives remain relevant technical topics. The child can learn to avoid sweeping sentences like ‘one miner controls everything’ and ‘no powerful participant can ever influence the system’.
What if a company claims to be ‘the official Bitcoin authority’?
Bitcoin does not have a single company that owns the protocol in the ordinary sense. Businesses, websites and public personalities may use Bitcoin-related branding or claim expertise. Those claims need to be checked against what the organisation actually does and which responsibilities it has.
A ten-year-old should never follow a supposed authority into a financial chat or pay an urgent fee to receive a prize. ScamShield warns about impersonation, investment offers and secret-sharing requests. The correct response is to stop and ask a trusted adult, rather than investigate by sending money.
What if a rule-change headline predicts a price rise?
A headline about a software change can describe a genuine technical proposal and still include an unsupported prediction about investment returns. Technical improvements or disagreements do not guarantee Bitcoin’s future market value. A child should separate what has been proposed, what has actually been adopted and what promoters hope will happen in the market.
For example, ‘A change was published for discussion’ can be checked through a project repository. ‘This will double every family’s money’ is a financial forecast. The first statement cannot establish the second. MoneySense warns that cryptocurrency trading is highly speculative and losses can be severe.
A class council game about changing rules
Start with a fictional game: everyone gets five counters, transfers are written in a ledger and no one may spend more than their balance. Ask one family member to propose allowing negative balances. Another writes a review explaining why the change might allow confusion or unexpected debts. A third checks proposed entries under the existing rules.
The family can discuss the proposal without adopting it. If they decide to test a new version, use a separate paper ledger so the results do not get mixed together. This illustrates proposal, review, adoption and incompatible records. It is not an exact simulation of Bitcoin governance or a reason to create real wallets.
A second game about independent checking
Give two pretend checkers identical copies of a ledger and the same rulebook. A third person proposes a transfer from a student with only two counters to someone else for five counters. Both checkers should reject it. Now secretly give one checker a different rulebook that allows borrowing.
The checkers may disagree. Ask whether the disagreement means one of them is dishonest. Not necessarily; they may be following different rules. The lesson is to identify which rule set each person is using. This is a useful general computing and collaborative problem-solving habit.
A third game: identify a proposal versus a final rule
Write three fictional notices: ‘We suggest awarding two points for attendance’, ‘This proposal is open for comments’ and ‘The club adopted the new rule on Monday’. Ask the child which statements describe ideas and which describe decisions. Then explain that a BIP’s existence does not itself prove Bitcoin’s network has adopted the proposal.
Have the child underline words such as proposed, draft, reviewed, accepted and implemented. Not every word has an identical technical meaning in every software process, but recognising the distinction is a valuable comprehension skill when reading technology news.
Bitcoin rules and Singapore law are different questions
Bitcoin network rules determine which transactions and blocks participants accept. Singapore law and MAS regulations govern relevant financial activities and businesses in Singapore. Following a cryptocurrency protocol does not automatically satisfy every legal requirement, and a business claiming to use Bitcoin does not become a government-authorised institution merely by doing so.
MoneySense explains that cryptocurrencies are not legal tender and that consumer protections have limits. Parents should distinguish ‘the network accepted a transaction’ from ‘the financial arrangement is safe, lawful and suitable for this family’. For an age-ten lesson, no actual transaction or investment is necessary.
What children can learn from open-source collaboration
Open-source software offers examples of people proposing improvements, reviewing one another’s work and documenting decisions. Those habits can be useful for group science projects or school coding lessons. They involve careful communication, patience and a willingness to discover mistakes.
A child who is interested can design a pretend rules document for a recycling game or a small library. Other family members can test edge cases and suggest corrections. The exercise fosters critical thinking and fairness without financial stakes, online identity exposure or software installations.
Why an agreed technical rule is not moral approval
A system may correctly check whether a transfer follows its technical rules without knowing whether the sender was threatened, deceived or mistaken. A blockchain’s accepted transaction therefore does not prove that an outside business is honest or that a purchase is appropriate. Technical validity and informed human consent are separate questions.
Ask the child to imagine a valid class-point transfer made after somebody falsely promised a prize. The ledger can accurately record the change while the promise is still dishonest. That is why families need scam awareness and independent source checking alongside curiosity about technology.
A parent’s approach to difficult questions
When the child asks who is in charge, avoid saying ‘nobody, so it is always safe’ or ‘miners, so they can do anything’. A clearer answer is that roles differ and participants need compatible rules. When the child asks who can fix mistakes, explain that technical validity does not create a universal customer-service desk for every Bitcoin transfer.
Encourage ‘I don’t know yet’ where appropriate. A complex engineering system can be studied one piece at a time. Parents do not need to pretend to know every detail to teach sound habits of checking sources and asking responsible questions.
Three practice questions and answers
Question 1. A developer writes new Bitcoin code. Does that force every node to accept the change? Answer: no. Participants choose software and must share compatible rules. Question 2. A miner proposes a block with an invalid reward. Must a validating node accept it because the miner worked hard? Answer: no.
Question 3. A BIP is published in a public repository. Does that prove the proposal has been adopted across the network? Answer: no. Publication is not the same as consensus or adoption. A good pupil explains why, using the words proposal, verification and choice.
Common misconceptions to correct
‘Satoshi still personally commands every node’ is false. ‘Developers can force every user to install their code’ is false. ‘Mining power makes any invalid block valid for everybody’ is false. ‘A BIP number is proof of approval’ is false. ‘A website editor is the owner of Bitcoin’ is false.
‘Every software update is a fork into a new cryptocurrency’ is false. ‘A decentralised network has no possible security problems’ is also false. The strongest explanation acknowledges a distributed design, different roles and practical limits instead of using sweeping claims.
A 30-minute no-purchase lesson
First ten minutes: write a class ledger and validation rules. Next ten minutes: appoint a proposer, a checker and a reviewer, then test an invalid entry and a proposed rule change. Final ten minutes: discuss what would happen if two groups used incompatible rules and how a child should evaluate an exaggerated headline about profit.
Finish with one sentence from the child: ‘People can propose new Bitcoin rules, but other participants do not automatically have to accept them.’ The exercise teaches participation and evidence without a node, wallet, exchange account or cryptocurrency purchase.
Age-ten revision checklist
- I can explain why a network needs compatible rules.
- I know a full node checks transactions and blocks.
- I know miners propose blocks rather than force invalid rules on every checker.
- I know developers write and review software.
- I can define open source in everyday language.
- I know a BIP is a proposal or documented process, not automatic adoption.
- I can describe consensus as shared agreement needed for records.
- I know different rulebooks may create incompatible systems.
- I can explain a fork using a classroom analogy.
- I understand protocol rules are not the same as Singapore law.
- I reject technical claims that promise guaranteed investment profits.
- I can learn without using real money.
Parents should ask for a one-minute explanation and a paper demonstration rather than memorised software terminology. If the child can identify two different roles and say what each cannot guarantee, the lesson has achieved its purpose.
Technical and Singapore source guide
Bitcoin’s FAQ describes network consensus, software choice and the different roles of participants. Bitcoin Core’s project overview describes open-source contributors, maintainers and validating-node software. The Bitcoin Improvement Proposals repository explicitly warns that publication does not equal consensus or adoption. BIP 3 describes the current proposal process.
For family financial protection, MoneySense’s risk guidance, updated 4 November 2026, warns about cryptocurrency speculation, provider failure and limits of regulation. ScamShield’s crypto scam guidance explains why unfamiliar financial requests and secret-sharing are dangerous. This content teaches computing concepts; it is not trading, financial or legal advice.
Continue the age-ten series
Read the Bitcoin origin and Satoshi timeline to see how the original design emerged. Continue with blockchain records and double spending and mining and the supply limit. Reinforce safe behaviour with wallet and scam safety.
The final educational outcome is a child who can distinguish who writes, checks and adopts rules, and who understands that technically valid transactions do not remove financial risk. Everything can be learned with paper and discussion.
