Blockchain Basics

Chapter 11
Governance, Law and Ethical Practice

Diploma in Blockchain
Blockchain Basics   •   Diploma

Governance, Law and Ethical Practice

Introduction

Blockchain systems are often described as decentralised technologies that reduce reliance on central authorities. This description is useful but incomplete. Every blockchain embodies governance choices: who may validate transactions, how rules change, how disputes are handled, how participants exercise rights, and who bears responsibility when systems fail. Governance therefore connects technical design with law, economics, ethics and public policy.

For organisations, blockchain adoption is not simply a software decision. It may create obligations relating to financial regulation, anti-money-laundering controls, taxation, privacy, consumer protection, intellectual property, sustainability and corporate accountability. Legal outcomes differ by jurisdiction, business model and token type. Consequently, this chapter explains general principles rather than providing jurisdiction-specific legal advice.

Learning Objectives

By the end of this chapter, a learner should be able to:

  1. Distinguish on-chain from off-chain governance.
  2. Explain forks and their consequences for stakeholders.
  3. Analyse stakeholder rights and accountability in blockchain ecosystems.
  4. Identify major regulatory concerns, including AML/KYC, taxation, data protection and consumer protection.
  5. Evaluate environmental, social and ethical risks.
  6. Apply a governance and compliance framework to a practical blockchain project.

1. Governance as a Socio-Technical System

Blockchain governance is the process through which rules are created, interpreted, enforced and changed. It includes both formal mechanisms, such as voting and protocol upgrades, and informal mechanisms, such as developer influence, social norms, exchange policies and regulatory pressure.

A blockchain ecosystem normally contains several stakeholder groups:

StakeholderTypical interests and responsibilities
UsersAccess, security, privacy, predictable rules and fair treatment
DevelopersProtocol design, maintenance, security and documentation
Validators or minersTransaction ordering, network security and operational rewards
Token holdersVoting, economic value and participation rights, where applicable
Application operatorsCustomer service, compliance, cybersecurity and disclosures
Exchanges and custodiansMarket integrity, custody, identity checks and reporting
RegulatorsFinancial stability, consumer protection and lawful activity
CommunitiesSocial legitimacy, inclusion and accountability

A technically decentralised system can still be socially or economically centralised. For example, a small group may control software repositories, validator infrastructure, token supply or governance votes. Decentralisation must therefore be evaluated across several dimensions rather than inferred from the absence of a single central administrator.

2. On-Chain and Off-Chain Governance

2.1 On-chain governance

On-chain governance records decision procedures in the protocol or in smart contracts. Examples include token-weighted voting, delegated voting, quorum requirements, timelocks and automatic execution of approved proposals.

Its advantages include transparency, auditability and procedural predictability. Participants can inspect proposals and, in some systems, verify voting results directly on the ledger. Automated execution can reduce discretion and implementation delays.

Its limitations are equally important. Token-weighted voting can give disproportionate influence to wealthy holders, exchanges or insiders. Voters may be inactive, uninformed or influenced by short-term financial incentives. A proposal can be technically valid yet socially illegitimate. Smart-contract errors may also execute decisions that are difficult or impossible to reverse.

2.2 Off-chain governance

Off-chain governance occurs through developer discussions, improvement proposals, foundation boards, companies, validator coordination, community forums, legal agreements and social consensus. Most major blockchain decisions involve substantial off-chain activity even when final approval is recorded on-chain.

Off-chain systems can support deliberation, expertise and emergency response. They can also introduce ambiguity, unequal participation and informal power. A technically open process may be practically inaccessible to users who lack time, language access, technical knowledge or voting tokens.

2.3 A governance comparison

CriterionOn-chain governanceOff-chain governance
Record of decisionsUsually public and machine-readableMay be distributed across forums and meetings
ExecutionCan be automaticRequires human or organisational action
StrengthTransparency and procedural consistencyFlexibility, expertise and deliberation
RiskPlutocracy, voter apathy and code rigidityInformal concentration and weak accountability
Best useClearly specified routine changesComplex, controversial or emergency decisions

Effective governance usually combines both approaches. A sound model may require public discussion, impact assessment and legal review off-chain, followed by transparent voting and a delayed, reversible implementation on-chain.

3. Governance Design and Stakeholder Rights

Governance design should answer five questions:

  1. Who can propose a change?
  2. Who can vote or approve it?
  3. What threshold and quorum are required?
  4. How is the decision implemented?
  5. What remedies exist if the decision causes harm?

A vote is not automatically a right in the legal sense. Holding a governance token may provide contractual, economic or protocol-level influence, but it may not create ownership of a company, entitlement to profits or protection from loss. These rights depend on the token’s design and applicable law.

Important governance safeguards include:

  • clear voting and delegation rules;
  • disclosure of conflicts of interest;
  • publication of proposal rationale and risk assessments;
  • notice periods and comment periods;
  • quorum and supermajority requirements for significant changes;
  • independent security audits;
  • emergency procedures with narrow scope;
  • timelocks allowing participants to exit or prepare;
  • conflict-resolution and appeal procedures;
  • accessible records and inclusive participation.

The principle of accountability is especially important. If a protocol has no legal entity, responsibility may still arise for developers, service providers, custodians, promoters or operators. “Decentralised” does not automatically mean “law-free” or “responsibility-free.”

4. Forks and Constitutional Change

A fork is a change to the rules used by network participants. A soft fork introduces rules that remain compatible with older software under specified conditions. A hard fork changes rules in a way that may make older software incompatible, potentially producing two histories or networks.

Forks may arise from software upgrades, security incidents, disputes about monetary policy, disagreements about block size or responses to theft. A fork is therefore both a technical event and a governance event.

Stakeholder consequences of a fork

  • Users: may need to select a network and protect private keys against replay or fraud risks.
  • Validators and miners: may choose which chain to support and may face equipment or operational costs.
  • Exchanges: must determine whether and how to list resulting assets.
  • Businesses: may need to update accounting, contracts, software and compliance controls.
  • Token holders: may receive assets on more than one chain, but ownership and tax consequences vary.
  • Regulators: may assess whether new assets, services or promotional activities create legal obligations.

A responsible fork process should include technical testing, security analysis, stakeholder consultation, clear communication, replay protection where relevant, and a documented decision about chain identity and asset treatment.

5. Regulatory Compliance

Blockchain regulation commonly addresses the activity being performed rather than the technology itself. A payment service, securities offering, lending platform, gambling application and data-processing system may each be regulated differently even if all use a blockchain.

A compliance analysis should identify:

  1. the legal entity or persons operating the service;
  2. the jurisdiction of operation and affected customers;
  3. the nature of the token or digital asset;
  4. custody and control arrangements;
  5. customer and transaction flows;
  6. applicable licensing, reporting and recordkeeping duties;
  7. consumer, privacy and cybersecurity risks.

Token classification may depend on economic substance, including rights to repayment, profit, governance, access or use. Marketing language, promises of return and managerial dependence can be relevant. A technical label such as “utility token” is not determinative.

Organisations should use a documented legal-risk register, obtain qualified advice before launch and design compliance into product architecture rather than treating it as a final checklist.

6. AML and KYC

Anti-money-laundering (AML) controls seek to prevent and detect the use of financial systems for money laundering, terrorist financing, sanctions evasion and related crimes. Know-your-customer (KYC) procedures identify and verify customers and support risk-based monitoring.

A typical compliance programme contains:

  • customer identification and verification;
  • beneficial-owner identification for legal entities;
  • risk classification;
  • sanctions and politically exposed person screening;
  • transaction monitoring;
  • suspicious-activity escalation and reporting;
  • record retention;
  • staff training and independent testing.

Blockchain transparency does not eliminate AML obligations. Public addresses do not necessarily identify real people, and transactions may pass through mixers, bridges, privacy tools or multiple services. Conversely, blockchain analytics can generate false positives and may rely on uncertain address attribution. Analytics should support, not replace, documented human judgement and fair procedures.

KYC also creates privacy risks. Organisations should collect only necessary information, restrict access, secure records and define retention periods. Identity data should not be placed immutably on a public ledger unless there is a compelling lawful basis and a technically robust design.

7. Taxation and Accounting

Digital-asset taxation varies significantly. Potential tax events include disposal for fiat currency, exchange for another asset, payment for goods or services, staking rewards, mining income, airdrops, lending returns and receipt of tokens for employment or business activity.

A basic gain or loss calculation is often represented as:

Gain or loss = Disposal proceeds − Adjusted cost basis

Here, disposal proceeds and adjusted cost basis must be measured using the applicable tax rules and currency at the relevant time. Transaction fees may affect either proceeds or basis depending on jurisdiction. The formula is not a universal tax rule; holding periods, valuation methods, exemptions and treatment of income must be checked locally.

Accurate records should include date and time, asset, quantity, fair value, wallet or account, counterparty where known, transaction fees, purpose and supporting evidence. Organisations must also consider financial reporting, impairment, revenue recognition, custody liabilities and disclosure of material risks.

8. Data Protection and Privacy

Blockchains create tension with data-protection principles because ledgers are replicated, durable and often difficult to modify. Data-protection law commonly emphasises lawful processing, purpose limitation, data minimisation, accuracy, security and rights of individuals. Exact obligations depend on jurisdiction and organisational role.

A privacy-conscious architecture generally follows these principles:

  • keep personal data off-chain where possible;
  • store only a cryptographic reference or commitment on-chain;
  • encrypt sensitive data under controlled access;
  • separate identity from transaction identifiers;
  • define retention and deletion procedures;
  • conduct a privacy impact assessment;
  • assess whether hashes remain personal data when they can be linked to an individual.

Hashing does not automatically anonymise information. If a hash can be linked to a person or used to single out an individual, it may remain legally relevant personal data. Immutability also does not override a legal obligation to correct or delete information; it may instead indicate that the architecture was unsuitable for that data.

9. Consumer Protection and Dispute Resolution

Consumers may misunderstand volatility, custody arrangements, smart-contract risk, fees, governance rights and the possibility of permanent loss. Ethical and legal communication should be accurate, balanced and understandable. Marketing should not imply guaranteed returns, risk-free decentralisation or regulatory approval that does not exist.

Good practice includes:

  • plain-language risk disclosures;
  • transparent fees and exchange rates;
  • clear explanations of custody and private-key responsibility;
  • accessible complaints procedures;
  • fraud and phishing warnings;
  • controls for vulnerable customers;
  • fair treatment during outages and upgrades;
  • evidence-based performance claims.

Dispute resolution is difficult where transactions are irreversible and participants are pseudonymous. Applications should therefore specify governing law, jurisdiction, service responsibilities, support channels and procedures for mistaken payments or compromised accounts. Irreversibility is a technical property, not a substitute for justice or accountability.

10. Sustainability and Ethical Practice

Blockchain sustainability has environmental, social and governance dimensions. Proof-of-work networks may consume substantial electricity, although impact depends on hardware efficiency, utilisation and energy sources. Proof-of-stake generally uses less operational energy but introduces concerns about wealth concentration, validator centralisation and governance power.

Environmental evaluation should consider the whole system: hardware manufacture, data-centre operations, cooling, network equipment, electronic waste and the social effects of energy demand. A simple energy estimate can be expressed as:

Energy use = Power × Time

Power is measured in watts and time in hours, producing watt-hours. This estimate is useful only when the relevant equipment and operating period are correctly defined; it should not be presented as a complete lifecycle assessment.

Ethical practice also requires attention to financial exclusion, surveillance, labour conditions, accessibility, algorithmic discrimination, market manipulation and governance capture. Smart contracts can automate unfair outcomes as efficiently as fair ones. Developers should conduct threat modelling, bias assessment, accessibility review and impact assessment before deployment.

11. Applied Case: A Blockchain Remittance Platform

The following is an illustrative case, not a description of a specific company.

Background

A start-up proposes a blockchain-based remittance service allowing migrant workers to send digital tokens to family members. Local partners convert tokens into national currency. The founders argue that the system reduces cost and settlement time.

Problem

The proposed design stores customer names and identity-document hashes on a public blockchain. It permits transfers from non-custodial wallets without clear transaction monitoring. Marketing materials state that transfers are “anonymous, instant and risk-free.” Governance tokens are sold to fund development, and token holders vote on fee changes.

Analysis

The system presents several risks:

  • public identity records may conflict with data-protection principles;
  • wallet access without risk-based controls may create AML exposure;
  • “risk-free” claims may breach consumer-protection expectations;
  • the governance token may have regulatory implications depending on its rights and promotion;
  • unclear responsibility exists between the start-up and local conversion partners;
  • exchange-rate volatility may transfer risk to consumers;
  • an emergency upgrade process has not been defined.

Approach and solution

The start-up should conduct a jurisdiction-by-jurisdiction legal assessment and identify licensed partners where required. Identity information should remain in a protected off-chain system, with only a carefully assessed reference recorded on-chain. Customer onboarding, sanctions screening, transaction monitoring and suspicious-activity procedures should be implemented before launch.

Marketing should disclose fees, exchange-rate risk, settlement limitations, custody arrangements and loss scenarios. Governance should separate technical voting from legal responsibility, publish conflicts of interest, introduce proposal notice periods and use a timelock for fee changes. A documented incident-response and dispute-resolution process should be established.

Outcome

The redesigned service may be slower to launch and less anonymous than originally proposed, but it offers stronger legal defensibility, consumer protection and operational resilience. Its governance model becomes more credible because responsibility is assigned rather than obscured by claims of decentralisation.

Learning points

  1. Compliance requirements should shape architecture from the beginning.
  2. Privacy is improved by data minimisation, not by assuming hashes are anonymous.
  3. Consumer protection includes accurate marketing and accessible remedies.
  4. Governance tokens do not remove the responsibilities of operating entities.
  5. Sustainable trust requires technical, legal and ethical controls together.

12. A Practical Governance and Compliance Framework

A project team can use the following sequence:

  1. Map the ecosystem: identify entities, users, validators, custodians, jurisdictions and data flows.
  2. Classify activities and assets: examine economic substance, custody, payments, investment features and operational roles.
  3. Assess risks: document legal, cyber, privacy, financial, environmental and social risks.
  4. Design controls: implement access control, KYC, monitoring, disclosures, audits and incident response.
  5. Design governance: define proposal rights, voting, quorum, timelocks, emergency powers and accountability.
  6. Test before deployment: conduct code audits, privacy assessments, user testing and simulated failures.
  7. Monitor continuously: regulation, threats, token ownership, energy use and stakeholder impacts change over time.
  8. Document decisions: maintain records that demonstrate why controls and governance choices were made.

This framework reflects a central professional principle: blockchain governance is a continuing management responsibility, not a one-time technical configuration.

Challenges and Limitations

No governance model eliminates conflict. Transparency may expose users to surveillance; privacy may limit auditability. Automatic execution may improve consistency but reduce discretion in exceptional cases. Decentralisation may increase resilience while making accountability harder. Regulation may protect users but also create barriers to innovation and access.

Legal uncertainty is another limitation. Rules differ between jurisdictions and may change as authorities respond to new business models. Cross-border systems can face overlapping obligations. Technical compliance tools also have error rates and may reproduce biases. Professionals must therefore combine technical evidence, legal expertise, stakeholder consultation and ethical reasoning.

Contemporary Developments

Current developments include greater use of proof-of-stake, decentralised autonomous organisations, tokenised real-world assets, stablecoins, zero-knowledge compliance tools, digital identity systems and regulatory reporting infrastructures. These developments may improve efficiency and privacy, but they do not remove the need to establish responsibility, lawful purpose and effective remedies.

Artificial intelligence may assist transaction monitoring, fraud detection and governance analysis. However, automated decisions require validation, explainability, human oversight and procedures for correcting errors. AI should not be used as an unquestionable substitute for compliance professionals or fair treatment.

Chapter Summary

Blockchain governance combines protocol rules, social coordination, organisational authority and legal accountability. On-chain governance offers transparency and automation, whereas off-chain governance provides flexibility and expertise; robust systems usually combine both. Forks demonstrate that technical rule changes can affect property, markets, software compatibility and stakeholder rights.

Responsible blockchain practice requires analysis of the activity, asset and jurisdiction rather than reliance on technological labels. AML/KYC, taxation, data protection and consumer protection must be incorporated into system design. Privacy requires data minimisation and careful separation of on-chain and off-chain information. Sustainability includes energy, hardware, social and governance impacts. Ethical practice demands truthful communication, fair participation, accountability, accessibility and effective remedies.

Key Terms

Governance: The process of creating, changing and enforcing rules in a blockchain ecosystem.

On-chain governance: Governance decisions implemented or recorded through blockchain protocol mechanisms or smart contracts.

Off-chain governance: Governance conducted through social, organisational, legal and community processes outside the ledger.

Fork: A change to blockchain rules that may create divergent software or transaction histories.

Soft fork: A generally backward-compatible rule change.

Hard fork: A rule change that may be incompatible with older software.

Stakeholder: A person or organisation affected by, or able to influence, a blockchain system.

Quorum: The minimum participation required for a valid decision.

Timelock: A delay between approval and execution of a governance decision.

AML: Anti-money-laundering measures designed to prevent and detect illicit financial activity.

KYC: Know-your-customer processes for identifying and assessing customers.

Beneficial owner: The individual who ultimately owns or controls an entity or arrangement.

Data minimisation: Collecting and retaining only data necessary for a defined purpose.

Consumer protection: Measures that promote fair treatment, accurate information and remedies for users.

Token classification: Determining the legal and economic character of a digital asset.

Tax basis: The amount used to calculate taxable gain or loss under applicable rules.

Proof-of-work: A consensus approach requiring computational work to propose or validate blocks.

Proof-of-stake: A consensus approach in which participants commit value to support validation.

Replay protection: Technical measures preventing a transaction on one fork from being unintentionally valid on another.

Smart contract: Software that executes specified rules, often on a blockchain.

Review Questions

5 Short Answer Questions

  1. What is the main difference between on-chain and off-chain governance?
  2. Why can token-weighted voting produce governance inequality?
  3. What is the difference between a soft fork and a hard fork?
  4. Why does hashing not automatically make personal information anonymous?
  5. Name four components of an effective AML programme.

5 Long Answer Questions

  1. Compare the strengths and weaknesses of on-chain and off-chain governance, and explain why hybrid models are common.
  2. Discuss how a blockchain fork can affect users, validators, exchanges and token holders.
  3. Explain how data protection principles should influence blockchain architecture.
  4. Analyse the relationship between decentralisation and legal accountability.
  5. Evaluate the environmental and ethical issues associated with proof-of-work and proof-of-stake.

3 Analytical / Application Questions

  1. A decentralised lending application markets its governance token as an investment with guaranteed returns. Identify the governance, consumer-protection and regulatory risks, and propose controls.
  2. Design a compliance plan for a cross-border blockchain payment service. Include stakeholder mapping, AML/KYC, privacy, taxation and dispute resolution.
  3. A protocol community proposes an emergency hard fork after a major exploit. Develop a decision framework addressing technical testing, stakeholder rights, communication, replay protection and accountability.

Multiple Choice Questions with Answers

Question 1

Which statement best describes on-chain governance?

A. Decisions are made only by government regulators

B. Rules or voting procedures are recorded or executed through blockchain mechanisms

C. All decisions occur privately among developers

D. Users cannot inspect governance decisions

Correct Answer: B. Rules or voting procedures are recorded or executed through blockchain mechanisms

Question 2

What is a significant risk of token-weighted voting?

A. It prevents token holders from participating

B. It guarantees equal influence for every person

C. It can concentrate influence among wealthy holders

D. It makes software testing unnecessary

Correct Answer: C. It can concentrate influence among wealthy holders

Question 3

What is a hard fork?

A. A temporary internet outage

B. A rule change that may be incompatible with older software

C. A private transaction between two users

D. A method for encrypting identity documents

Correct Answer: B. A rule change that may be incompatible with older software

Question 4

Which information should generally be kept off a public blockchain where possible?

A. A block timestamp

B. A transaction hash

C. A validator signature

D. A customer’s identity document

Correct Answer: D. A customer’s identity document

Question 5

What is the primary purpose of KYC procedures?

A. To increase mining difficulty

B. To identify and assess customers

C. To guarantee token price stability

D. To eliminate all blockchain fees

Correct Answer: B. To identify and assess customers

Question 6

Which item is most important in calculating a taxable digital-asset gain under the basic model presented?

A. Disposal proceeds and adjusted cost basis

B. Number of network validators only

C. The colour of the user interface

D. The blockchain’s block height only

Correct Answer: A. Disposal proceeds and adjusted cost basis

Question 7

Why is blockchain immutability challenging for data protection?

A. It makes all data automatically public on the internet

B. It can make correction or deletion of recorded information difficult

C. It prevents encryption from being used off-chain

D. It removes the need for data security

Correct Answer: B. It can make correction or deletion of recorded information difficult

Question 8

Which measure best supports consumer protection?

A. Advertising guaranteed returns

B. Hiding custody risks in technical documentation

C. Providing clear fees, risks and complaint procedures

D. Removing all information about governance changes

Correct Answer: C. Providing clear fees, risks and complaint procedures

Question 9

Using Energy use = Power × Time, what is the energy use of a 100-watt device operating for 5 hours?

A. 20 Wh

B. 105 Wh

C. 500 Wh

D. 5,000 Wh

Correct Answer: C. 500 Wh

Question 10

Which statement about decentralisation is most accurate?

A. Decentralisation automatically removes legal responsibility

B. A technically decentralised system can still have concentrated social or economic power

C. Decentralised systems cannot be regulated

D. Decentralisation guarantees equal voting influence

Correct Answer: B. A technically decentralised system can still have concentrated social or economic power

Blockchain Basics
Chapter 11 of 14