Blockchain Network Foundations

Introduction and Context

Modern economic and social activity depends on systems that record facts: ownership, payments, identity, contracts, credentials, and the movement of goods. Traditionally, these records have been maintained by central institutions such as banks, government agencies, corporations, and platform operators. A central institution usually controls the database, determines who may update it, and resolves disputes when records conflict.

Blockchain networks emerged as an alternative approach to maintaining records among parties that may not fully trust one another. Instead of relying on one central database administrator, a blockchain distributes copies of a ledger across multiple network participants. Participants use agreed rules, cryptographic techniques, and a consensus process to determine which transactions become part of the shared record.

A blockchain is therefore not merely a database and not merely a cryptocurrency technology. It is a type of distributed ledger system with particular features: replicated data, ordered records, cryptographic linkage, network protocols, and governance rules. These features can support digital assets and automated agreements, but they also introduce limitations involving performance, privacy, energy use, legal responsibility, and governance.

This chapter establishes the conceptual vocabulary required for later study of blockchain architecture, consensus mechanisms, smart contracts, security, and applications.

Learning Objectives

After completing this chapter, you should be able to:

1. Explain the meaning and purpose of a distributed ledger.
2. Distinguish centralized, decentralized, and distributed systems.
3. Describe how blockchain networks create trust without depending entirely on one central authority.
4. Identify major network participants and explain their roles.
5. Use fundamental blockchain terminology accurately.
6. Trace the historical movement from centralized information systems to blockchain networks.
7. Evaluate practical, governance, ethical, and regulatory implications of blockchain adoption.

1. From Centralized Records to Shared Ledgers

Centralized systems

In a centralized system, one organization or administrative authority controls the principal record. A bank, for example, maintains the authoritative balance of a customer account. When a transfer occurs, the bank verifies the request, updates its database, and communicates the result to the relevant parties.

Centralization offers important advantages. It can provide high transaction speed, consistent administration, clear accountability, efficient privacy controls, and relatively simple dispute resolution. A central operator can also correct errors and coordinate upgrades.

However, centralized systems create dependence on the operator. The system may fail if the operator experiences a technical outage, becomes compromised, acts dishonestly, or refuses service. The operator is also a valuable target for cyberattack. In addition, users must trust the institution’s internal controls, staff, software, and legal compliance.

Distributed systems

A distributed system places computing resources or records across multiple machines or locations. Distribution improves resilience and can increase processing capacity, but it does not automatically eliminate central control. A company may operate a distributed database across many data centres while retaining complete authority over it.

Thus, distribution describes where resources or copies are located, whereas decentralization describes how authority and decision-making are arranged.

Decentralized systems

A decentralized system distributes control among multiple independent participants. No single participant necessarily has unilateral authority over the whole system. Decentralization can be technical, political, economic, or organizational.

These dimensions should be distinguished. A network may have technically distributed servers but economically concentrated ownership. A public blockchain may allow anyone to validate transactions, yet a small number of mining or staking operators may control a large share of its activity. Decentralization is therefore a matter of degree rather than a simple yes-or-no property.

Distributed ledgers

A distributed ledger is a record system in which multiple participants maintain synchronized copies of transaction data. The ledger records events in an agreed structure and is updated according to shared rules. Participants do not necessarily hold identical software, authority, or data access, but they follow a protocol that determines how valid updates are accepted.

A distributed ledger may be permissionless, allowing broad participation, or permissioned, restricting participation to approved organizations. Blockchain is one important design of distributed ledger, but the terms are not exact synonyms. Some distributed ledgers do not use blocks, public verification, or blockchain-style consensus.

2. What Makes a Blockchain a Blockchain?

A blockchain is a ledger in which transactions are grouped into blocks, and blocks are linked in chronological sequence using cryptographic references. Each block normally contains transaction data, a reference to the preceding block, a timestamp or similar ordering information, and data associated with the network’s consensus procedure.

A cryptographic hash function transforms input data into a fixed-length output called a hash. A small change in the input normally produces a substantially different output. A hash does not encrypt data for later decryption; it is primarily used for integrity checking and identification.

When a block includes the hash of its predecessor, changing an earlier block causes the references in subsequent blocks to become inconsistent. This makes unauthorized alteration detectable. It does not, by itself, make alteration mathematically impossible. Security also depends on controlling who can propose changes, how consensus is reached, how keys are protected, and how the network responds to attacks.

Transactions and blocks

A transaction is a digitally represented instruction or event, such as transferring a token, recording a supply-chain event, or invoking a smart contract. A transaction may include the sender’s public address, destination, amount or data, and a digital signature.

A digital signature uses a private key to prove that the holder authorized a message. Other participants can verify the signature using the corresponding public key. A signature supports authenticity and integrity, but it does not prove that the person controlling a key is legally entitled to an asset. That connection requires identity systems, legal rules, or organizational controls.

Valid transactions are collected into a block by a block producer. Depending on the protocol, this participant may be called a miner, validator, sequencer, or another term. Once the network accepts a block according to its consensus rules, nodes update their local ledger state.

State and history

The transaction history is the ordered sequence of accepted transactions. The state is the current condition derived from that history. For example, a token ledger’s state may show the current balances of all addresses, while its history records every accepted transfer.

A blockchain system must ensure that valid participants agree sufficiently on both the order of transactions and the resulting state. This is especially important when two transactions appear to spend the same digital asset. The protocol must determine which transaction is accepted and which is rejected or delayed.

3. Trust Models in Blockchain Networks

Blockchain does not eliminate trust. It changes the object and distribution of trust. Users may trust cryptographic verification, open-source software, economic incentives, institutional governance, legal enforcement, or a combination of these.

Trust in centralized systems

In a conventional system, trust is concentrated in an institution. Users trust the institution to maintain accurate records, prevent unauthorized access, follow regulations, and remain operational. The institution may provide customer support and reverse transactions under defined conditions.

Trust in blockchain systems

In a blockchain network, trust is distributed across several mechanisms:

• Cryptographic trust: signatures and hashes allow participants to verify certain properties without relying on personal knowledge of one another.
• Protocol trust: software rules specify how transactions are validated and blocks are accepted.
• Economic trust: rewards and penalties can encourage participants to follow the rules.
• Transparency-based trust: publicly inspectable records can enable independent verification.
• Governance trust: participants must trust the processes used to change the protocol and resolve disagreements.
• Institutional and legal trust: organizations remain responsible for interfaces, custody, compliance, and off-chain obligations.

The expression “trustless” is therefore misleading if it suggests that no trust is required. A more accurate description is “reduced reliance on a single trusted intermediary for particular verification tasks.”

Permissionless and permissioned trust models

A permissionless network generally allows participants to join, submit transactions, and attempt to validate blocks without obtaining prior approval. Its security must address unknown or potentially hostile participants. Consensus mechanisms commonly use computational expenditure, economic deposits, or other participation costs.

A permissioned network restricts participation through identity and authorization controls. It may be operated by a consortium of banks, logistics companies, public agencies, or other known organizations. Permissioned networks can offer higher throughput and stronger privacy, but participants must trust the administrators and membership rules.

4. Consensus and Agreement

Consensus is the process by which network participants agree on the validity and ordering of transactions. It is not simply a vote on every social or legal question. It is a technical mechanism operating within a defined protocol.

A blockchain network must address several questions:

1. Who may propose a block?
2. How do other participants verify it?
3. What happens when competing blocks are proposed?
4. When is a transaction considered final?
5. How are dishonest or unavailable participants handled?

Proof of Work

Proof of Work selects or prioritizes block producers partly through computational work. Participants compete to find a value satisfying a protocol-defined condition. The process consumes energy because participants perform repeated calculations, although the exact energy use depends on hardware, electricity sources, network demand, and protocol design.

Its security model makes rewriting history expensive, particularly when an attacker lacks a large share of the network’s computational capacity. It may offer strong openness and objective participation rules, but it can have high energy consumption, variable confirmation times, and limited throughput.

Proof of Stake

Proof of Stake uses an economic stake as part of validator selection and accountability. Validators typically lock assets or otherwise commit value. Protocol rules may impose penalties for certain forms of dishonest behavior or failure.

Proof of Stake can reduce direct energy requirements compared with competitive computational mining. Nevertheless, it introduces questions about wealth concentration, validator selection, delegation, slashing, custody, and governance. The precise security properties depend on the particular protocol rather than on the label alone.

Finality

Finality describes the degree of confidence that a transaction will not be reversed. Some systems provide probabilistic finality: confidence increases as additional blocks are added. Other systems provide protocol-defined or economic finality after a specified agreement process. Users must distinguish transaction inclusion, confirmation, and finality because these are not always identical.

5. Major Blockchain Network Participants

Blockchain networks involve different participants with distinct responsibilities. One entity may perform several roles, but the roles should be conceptually separated.

Users and clients

Users initiate transactions through wallets, applications, exchanges, or enterprise systems. A wallet generally manages cryptographic keys and constructs or signs transactions; it does not necessarily store coins in the way a physical wallet stores cash. In many systems, assets are represented by ledger entries controlled by keys.

Nodes

A node is a computer running software that communicates with the network. A full node independently verifies transactions and blocks according to the protocol. It may store the complete ledger history or a complete representation of current state, depending on the implementation.

Light clients perform less verification and rely on full nodes or specialized proofs. This can reduce hardware and bandwidth requirements but increases dependence on external information.

Validators, miners, and block producers

These participants perform the protocol-specific work of proposing or confirming blocks. “Miner” is associated primarily with Proof-of-Work systems, while “validator” is common in Proof-of-Stake systems. A block producer may receive transaction fees, protocol rewards, or other compensation.

Developers and maintainers

Developers create and maintain node software, wallets, smart contracts, testing tools, and infrastructure. Code changes may be adopted through formal governance, informal coordination, or a combination. Developers may have significant practical influence even when they cannot unilaterally change the ledger.

Exchanges and custodians

Exchanges facilitate conversion between assets and may hold keys on behalf of customers. Custodians provide key-management services for individuals or institutions. These intermediaries improve usability but reintroduce centralized points of control and failure.

Oracles and bridges

A blockchain cannot automatically observe most external events. Oracles transmit off-chain information, such as interest rates, weather conditions, or delivery status, to smart contracts. Bridges connect separate networks by transferring representations or messages between them. Both functions create important security risks because the external data or cross-network communication may be manipulated.

Governance participants

Governance participants may include token holders, validators, developers, users, businesses, regulators, and community organizations. They influence protocol upgrades, fee policies, dispute processes, and standards. Governance power may be formal, such as an on-chain vote, or informal, such as the ability to persuade operators to adopt software.

6. Essential Blockchain Terminology

Address, public key, and private key

An address is an identifier used to receive assets or interact with a blockchain. It is often derived from a public key or related data. A private key is secret information used to authorize transactions. Loss or theft of a private key can result in loss of control, although some systems support recovery arrangements through other mechanisms.

Wallet

A wallet is hardware or software that manages keys and supports transaction signing. A custodial wallet gives key control to a service provider, while a non-custodial wallet places key responsibility with the user.

Block height and genesis block

Block height indicates a block’s position in the chain, subject to the numbering convention of the particular network. The genesis block is the initial block from which the blockchain begins.

Peer-to-peer network

A peer-to-peer network allows participants to communicate directly rather than routing every message through one central server. Nodes relay transactions and blocks according to network protocols.

Fork

A fork occurs when protocol rules or the accepted transaction history diverge. A temporary fork may arise when competing blocks appear close together. A planned protocol change may produce a soft fork or hard fork, depending on compatibility and the effect on validation rules.

Smart contract

A smart contract is software deployed on a blockchain that executes according to specified rules. It is not necessarily a legal contract, and its execution may not capture the full meaning of legal agreement. Smart contracts can automate transfers, permissions, auctions, or financial logic, but programming errors can produce irreversible consequences.

Gas and transaction fee

Gas is a unit or accounting concept used by some platforms to measure computational or storage work. A transaction fee compensates network participants or helps manage scarce capacity. Fee structures vary by protocol.

Token

A token is a digital representation recorded by a blockchain system. Tokens may represent native network assets, claims, voting rights, physical goods, access permissions, or other rights. Tokenization does not automatically establish legal ownership of the underlying object.

Immutability

Blockchain records are often described as immutable. In practice, immutability means that accepted records are difficult to alter without detection or broad network agreement. It does not mean that data can never be changed. Protocol upgrades, governance decisions, attacks, legal interventions, or application-level corrections may affect how records are interpreted.

7. Historical Evolution

The development of blockchain networks reflects several earlier technological and institutional developments.

Central databases and client-server computing

Early business information systems concentrated data and processing in mainframes. Client-server architecture later distributed application functions between user devices and servers, but organizations still generally controlled authoritative databases.

Internet and peer-to-peer communication

The Internet enabled geographically separated computers to communicate through common protocols. Peer-to-peer systems demonstrated that participants could share resources without a single central server. File-sharing networks, distributed storage, and decentralized communication systems influenced later blockchain designs, although they did not necessarily solve the problem of agreeing on a single transaction history.

Public-key cryptography and digital cash

Public-key cryptography made it possible to sign digital messages and verify signatures. Earlier digital-cash proposals explored electronic payments, privacy, and scarcity. A central challenge remained: digital information can be copied, so a payment system needs a reliable method for preventing the same unit from being spent twice.

The emergence of Bitcoin

Bitcoin combined peer-to-peer networking, digital signatures, hash-linked blocks, incentive mechanisms, and Proof of Work to create an open network for maintaining a transaction history without a central payment administrator. Its design demonstrated that a public blockchain could coordinate economic activity among pseudonymous participants, though with trade-offs in throughput, latency, energy use, and governance.

Programmable blockchains and enterprise platforms

Later systems expanded beyond relatively simple payment transfers by supporting programmable smart contracts and decentralized applications. Other projects developed permissioned platforms for business consortia, where participants are known and access controls are important. These developments broadened blockchain’s possible applications but also made system design more complex.

8. Practical Applications and Professional Implications

Blockchain is most promising where several independent parties need a shared record, reconciliation is costly, and participants benefit from verifiable history. Potential applications include:

• cross-organizational supply-chain records;
• settlement of digital assets;
• trade documentation and provenance;
• credential verification;
• identity and access management;
• shared registries;
• automated financial agreements; and
• machine-to-machine payment or authorization systems.

A blockchain is not automatically appropriate. A conventional database may be better when one trusted organization controls the process, records require frequent correction, high performance is essential, or confidentiality is paramount.

A professional evaluation should ask:

1. Which parties require a shared record?
2. Why is a conventional database insufficient?
3. Who is allowed to read, submit, and validate data?
4. What is the legal status of recorded assets or events?
5. How will incorrect external data be corrected?
6. Who pays for operation and upgrades?
7. What happens if keys are lost or participants leave?
8. What privacy, cybersecurity, and regulatory obligations apply?

9. Illustrative Case: A Multi-Company Food Provenance Network

Background

Assume that a group of farms, processors, logistics companies, retailers, and auditors wants to improve the traceability of packaged food. Each organization currently maintains a separate database. When a contamination investigation occurs, employees exchange spreadsheets and emails to reconstruct the product’s path.

This is an illustrative case, not a report of a specific real-world deployment.

Problem

The participants face duplicated data entry, inconsistent identifiers, delayed investigation, and disputes about when and where a product changed custody. No single company wants to give another company complete control of the shared record. At the same time, the information cannot be entirely public because it includes commercially sensitive quantities and supplier relationships.

Analysis

The problem is not simply a lack of database technology. It is a coordination problem among organizations with partially aligned interests. A permissioned distributed ledger could provide a shared event history while allowing role-based access. However, the ledger cannot determine independently whether a temperature sensor was accurate or whether an employee entered a truthful location.

Approach and solution

The consortium designs a permissioned network. Approved organizations operate validating nodes. Each shipment receives a digital identifier. Participants record events such as harvest, processing, dispatch, receipt, and inspection. Digital signatures identify the organization submitting an event. Sensitive commercial details are stored off-chain, while the ledger records references, permissions, and relevant proofs of integrity.

Governance rules define onboarding, software upgrades, audit access, correction procedures, and responsibility for compromised credentials. External sensors are authenticated, and unusual readings are reviewed rather than accepted automatically.

Outcome

When a product lot is flagged, authorized participants can reconstruct its recorded movement more rapidly and identify affected batches. The system improves coordination and auditability, but it does not guarantee truthful data. It also creates new responsibilities for key management, privacy protection, node operation, and consortium governance.

Learning points

The case demonstrates that blockchain value often arises from shared governance rather than from cryptography alone. A permissioned network can reduce reconciliation work, but it cannot replace organizational controls, quality assurance, legal accountability, or trustworthy data collection.

10. Limitations, Risks, and Governance

Scalability and performance

Open participation, extensive validation, and strong security can limit transaction throughput or increase confirmation time. Scaling solutions may use larger blocks, secondary networks, sharding, batching, or other techniques, but each introduces trade-offs involving complexity, interoperability, security, or decentralization.

Privacy

A transparent ledger may expose transaction patterns even when addresses are pseudonymous. Personal data placed directly on an immutable ledger may conflict with privacy obligations and deletion requirements. Privacy-preserving techniques and off-chain storage can reduce exposure, but they require careful design and may increase complexity.

Key management

Private-key compromise is a major operational risk. Organizations should use secure key storage, role separation, transaction limits, multi-signature controls, recovery procedures, monitoring, and tested incident response. Convenience should not be confused with security.

Smart-contract and oracle risk

A smart contract may execute exactly as programmed while producing an economically or legally undesirable result. Code review, testing, formal analysis where appropriate, controlled upgrades, and emergency procedures are important. Oracle and bridge components require special scrutiny because they connect blockchain logic to external systems.

Governance and concentration

Even a technically decentralized system may be influenced by a small number of developers, validators, infrastructure providers, exchanges, or token holders. Governance should make decision rights, upgrade procedures, conflicts of interest, and emergency powers explicit.

Legal and regulatory issues

Blockchain applications may involve financial regulation, consumer protection, data protection, taxation, anti-money-laundering requirements, securities law, property law, and sector-specific rules. Regulatory treatment differs across jurisdictions and changes over time. Organizations should obtain qualified legal advice rather than assuming that technical decentralization removes legal responsibility.

Environmental and social considerations

The environmental impact of a blockchain depends largely on its consensus mechanism, hardware, electricity sources, and utilization. Proof-of-Work networks may consume significant electricity, while Proof-of-Stake systems shift attention toward hardware, governance, custody, and concentration risks. A responsible assessment should compare the complete system with realistic alternatives rather than relying on slogans.

11. Best Practices for Foundational Blockchain Projects

1. Define the business or public problem before selecting blockchain.
2. Map participants, authority, incentives, and accountability.
3. Choose permissioned or permissionless architecture deliberately.
4. Minimize sensitive personal and commercial data stored on-chain.
5. Separate on-chain records from off-chain documents and sensors.
6. Design key-management and recovery procedures before deployment.
7. Test consensus, smart contracts, integrations, and failure scenarios.
8. Document governance, upgrades, disputes, and emergency actions.
9. Measure performance, cost, energy use, privacy, and user experience.
10. Treat blockchain as part of a socio-technical system, not as a substitute for institutions.

Chapter Summary

A blockchain is a form of distributed ledger that organizes transactions into cryptographically linked blocks and uses network rules to establish an agreed history. Distributed computing does not automatically mean decentralized control; authority, ownership, and validation may remain concentrated. Blockchain trust is distributed among cryptography, protocol rules, incentives, transparency, governance, and legal institutions rather than eliminated.

Permissionless networks admit broad participation and must address unknown or adversarial actors. Permissioned networks restrict membership and can provide predictable performance and privacy, but they depend more heavily on organizational governance. Nodes, users, validators, developers, custodians, oracles, bridges, and governance participants perform different roles in the ecosystem.

Blockchain developed from centralized databases, peer-to-peer networking, public-key cryptography, and digital-cash research. Its applications are strongest where independent parties need a shared, auditable record and no single party is accepted as the sole administrator. Nevertheless, blockchain does not guarantee truthful input, legal ownership, privacy, scalability, or security. Sound professional practice requires comparison with conventional alternatives, explicit governance, careful key management, and attention to ethical and regulatory responsibilities.

Key Terms

Distributed ledger: A shared record maintained and synchronized by multiple participants.

Blockchain: A distributed ledger that groups records into cryptographically linked blocks.

Centralization: Concentration of control or authority in one organization or small group.

Decentralization: Distribution of decision-making authority among multiple independent participants.

Node: A computer running software that communicates with and may verify a blockchain network.

Transaction: A digitally represented instruction or event submitted to the ledger.

Block: A collection of transactions and associated metadata accepted as a unit.

Hash: A fixed-length output produced from input data by a cryptographic hash function.

Digital signature: Cryptographic evidence that a private key authorized a message.

Private key: Secret cryptographic information used to authorize transactions.

Wallet: Software or hardware that manages keys and supports blockchain interactions.

Consensus: A protocol process for agreeing on valid transactions and their ordering.

Validator: A participant that performs protocol-specific transaction or block validation.

Proof of Work: A consensus approach using computational work as a participation and security mechanism.

Proof of Stake: A consensus approach using committed economic value in validator selection or accountability.

Finality: The degree of assurance that an accepted transaction will not be reversed.

Smart contract: Blockchain-resident software that executes specified rules.

Oracle: A service or mechanism that supplies external information to a blockchain application.

Fork: A divergence in protocol rules or accepted transaction history.

Token: A digital representation of an asset, right, permission, or value recorded on a blockchain.

Review Questions

Short Answer Questions

1. What is a distributed ledger, and how does it differ from a conventional centralized database?
2. Why are distribution and decentralization not synonymous?
3. What role does a cryptographic hash play in a blockchain?
4. Distinguish a private key from a wallet.
5. What is the purpose of consensus in a blockchain network?

Long Answer Questions

1. Explain how blockchain changes, rather than eliminates, the need for trust.
2. Compare permissionless and permissioned blockchain networks, including their strengths and weaknesses.
3. Describe the roles of users, nodes, validators, developers, custodians, oracles, and governance participants.
4. Trace the major stages in the evolution from centralized databases to blockchain networks.
5. Discuss the principal limitations and governance risks that organizations should evaluate before adopting blockchain.

Analytical / Application Questions

1. A consortium of hospitals wants to share verified patient credentials while protecting privacy. Evaluate whether a permissioned blockchain is appropriate and identify the main design and governance issues.
2. A company proposes recording all customer identity information directly on a public blockchain. Analyze the security, privacy, legal, and operational risks and recommend an alternative architecture.
3. A supply-chain blockchain shows that a shipment arrived on time, but later evidence reveals that the source sensor was faulty. Explain why blockchain did not prevent the error and design controls for improving data reliability.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a distributed system from a decentralized system?

A. A distributed system always has no central authority.

B. Distribution concerns the location of resources, while decentralization concerns the distribution of control.

C. Decentralization means all data must be stored in one database.

D. The two terms always have exactly the same meaning.

Correct Answer: B. Distribution concerns the location of resources, while decentralization concerns the distribution of control.

Question 2

What is the primary purpose of linking each blockchain block to the previous block with a cryptographic hash?

A. To encrypt every transaction so nobody can read it.

B. To guarantee that all real-world data entered is truthful.

C. To make unauthorized changes detectable and difficult to conceal.

D. To eliminate the need for network participants.

Correct Answer: C. To make unauthorized changes detectable and difficult to conceal.

Question 3

Which participant normally manages cryptographic keys and may sign transactions on behalf of a user?

A. Wallet

B. Oracle

C. Block explorer

D. Consensus algorithm

Correct Answer: A. Wallet

Question 4

What is the main function of a consensus mechanism?

A. To create legal ownership automatically.

B. To determine which transactions and blocks the network accepts.

C. To replace all software developers.

D. To guarantee unlimited transaction throughput.

Correct Answer: B. To determine which transactions and blocks the network accepts.

Question 5

Which feature is most characteristic of a permissioned blockchain?

A. Anyone may validate without authorization.

B. Participants are approved or identified by an administrative process.

C. No organization has any governance responsibility.

D. The ledger must be completely public.

Correct Answer: B. Participants are approved or identified by an administrative process.

Question 6

Why is the term “trustless” potentially misleading when describing blockchain?

A. Blockchain networks cannot use cryptography.

B. Users still rely on protocol design, governance, incentives, and sometimes legal institutions.

C. All blockchain transactions require a bank employee’s approval.

D. Blockchain records are always editable by any user.

Correct Answer: B. Users still rely on protocol design, governance, incentives, and sometimes legal institutions.

Question 7

Which statement about a digital signature is correct?

A. It proves that the signer is legally entitled to an asset in every situation.

B. It provides evidence that the holder of a private key authorized the message.

C. It permanently hides transaction data from all participants.

D. It replaces the need for a public key.

Correct Answer: B. It provides evidence that the holder of a private key authorized the message.

Question 8

What is an oracle used for in many blockchain applications?

A. It supplies external information to blockchain-based logic.

B. It creates the genesis block manually after every transaction.

C. It stores every private key in a public database.

D. It prevents all protocol upgrades.

Correct Answer: A. It supplies external information to blockchain-based logic.

Question 9

Which situation is generally the strongest candidate for a shared blockchain ledger?

A. A single company needs a fast private database for its internal payroll.

B. Several independent organizations need an auditable shared record and do not want one party to control it entirely.

C. A user wants to store a large collection of private videos at minimum cost.

D. A business requires unrestricted correction of every historical record.

Correct Answer: B. Several independent organizations need an auditable shared record and do not want one party to control it entirely.

Question 10

What is a major limitation of blockchain immutability?

A. It guarantees that the original data entry was accurate.

B. It prevents all software bugs.

C. It can preserve an incorrect or fraudulent input once accepted, unless governance or corrective processes intervene.

D. It means no participant needs access controls.

Correct Answer: C. It can preserve an incorrect or fraudulent input once accepted, unless governance or corrective processes intervene.