How Blockchain Works | How the Rules Can Change
Blockchain rules are implemented in software and governance arrangements, so people can propose changes. But writing new code is not the same as persuading independent participants to adopt it. Protocol upgrades, application changes and institutional policies involve different powers.
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 robotics club shares a booking ledger with two schools. A teacher proposes changing the cancellation rule from one approval to two. Kai Kai updates a draft of the program. Tricia asks whether the new rule already applies to existing bookings. The answer requires an agreed effective point and a proper adoption process.
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 rule must be identified first
Is the proposal about who may book a robot, the application code that checks a booking, the permissioned network’s membership policy, or the blockchain protocol itself? Each belongs to a different layer. Changing the booking rule does not necessarily require a protocol upgrade.
2. A developer can propose without commanding every node
On networks with independent operators, a developer can publish software but cannot assume everyone will adopt it. Users, node operators, validators, maintainers and other stakeholders may have different roles in coordination. The outcome depends on the network’s actual governance process.
3. Effective time matters
A rule change needs a clear boundary. A booking accepted yesterday should not be silently reinterpreted under a different rule without an appropriate policy. The system must explain what happens to pending requests, existing rights and disputes.
4. Different versions can create disagreement
If participants apply incompatible rules, they may reject each other’s proposed changes or follow different histories. That is not necessarily a software typo; it can reflect an unresolved coordination problem. Network-specific upgrade mechanisms matter.
5. Teach governance with paper rules
Give three students a shared booking notebook. Propose a new cancellation condition. Ask who may approve it, when it begins and how the old records will be interpreted. This makes governance understandable without running any blockchain software.
A family activity: find the missing assumption
Draw three boxes labelled People, Digital Record and Real-World Result. Read the opening story and ask: Who is allowed to propose a new rule, and who must accept it before it becomes effective? 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-081-governance-change-authority-workflow/”>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://ethereum.org/governance/”>https://ethereum.org/governance/</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: Blockchain rules are implemented in software and governance arrangements, so people can propose changes. But writing new code is not the same as persuading independent participants to adopt it. Protocol upgrades, application changes and institutional policies involve different powers.