Unit 1: Introduction to Blockchain and Decentralization - Subjective Questions

The growth of blockchain technology has been driven by several factors:

• Need for trustless systems: Blockchain allows participants who do not trust one another to exchange value without relying on a central intermediary.
• Success of Bitcoin: Bitcoin demonstrated that a decentralized digital currency could operate securely on a global scale.
• Transparency and auditability: Transactions recorded on a blockchain can be independently verified, improving accountability.
• Immutability: Cryptographic hashing and distributed consensus make confirmed records difficult to alter.
• Smart contracts: Programmable blockchains enable automated execution of agreements and business processes.
• Tokenization: Physical and digital assets can be represented as blockchain-based tokens.
• Institutional adoption: Financial institutions, governments, supply-chain companies, and technology firms have invested in blockchain research and applications.
• Web3 and decentralized finance: DeFi, NFTs, DAOs, and decentralized applications have expanded blockchain beyond digital currency.

Thus, blockchain has grown from a cryptocurrency infrastructure into a general-purpose platform for decentralized coordination, ownership, and computation.

The history of blockchain developed through several important stages:

1. Cryptographic foundations: Public-key cryptography, digital signatures, and cryptographic hash functions created the technical basis for secure digital transactions.
2. Hash-linked timestamping: Researchers Stuart Haber and W. Scott Stornetta proposed cryptographically linked records in 1991 to protect digital documents from tampering.
3. Merkle trees: Merkle trees made it possible to summarize and verify large collections of records efficiently.
4. Early digital cash: Systems such as David Chaum's DigiCash introduced privacy-preserving electronic payments, although they depended on centralized authorities.
5. Proof-of-work concepts: Hashcash and related proposals used computational work to discourage spam and abuse.
6. Decentralized currency proposals: Projects such as b-money and Bit Gold described ideas related to distributed digital money.
7. Bitcoin white paper: In 2008, Satoshi Nakamoto published Bitcoin: A Peer-to-Peer Electronic Cash System.
8. Bitcoin launch: The Bitcoin network began in January 2009 with the mining of the genesis block.

Bitcoin's major innovation was combining peer-to-peer networking, proof of work, digital signatures, economic incentives, and a distributed ledger to solve the double-spending problem without a central authority.

A distributed system is a collection of independent computers that communicate through a network and coordinate their actions so that users may perceive them as a single system.

Major characteristics:

• Concurrency: Multiple nodes perform operations simultaneously.
• No global clock: Nodes cannot rely on perfectly synchronized time.
• Independent failures: One node or communication link may fail while others continue operating.
• Resource sharing: Data, storage, and computational resources are distributed among nodes.
• Scalability: Capacity can be increased by adding more nodes.
• Message-based communication: Nodes coordinate by exchanging messages over a network.

Major challenges:

• Network delays and message loss
• Node crashes and malicious behavior
• Data consistency across replicas
• Coordination and synchronization
• Fault detection and recovery
• Security, authentication, and access control
• Reaching agreement among geographically separated nodes

Blockchain is a specialized distributed system in which nodes collectively maintain an ordered, replicated ledger by following a consensus protocol.

A blockchain is a distributed, append-only ledger in which transactions are grouped into blocks and blocks are linked using cryptographic hashes.

Basic structure of a block:

• Block header: Contains metadata such as the previous block hash, timestamp, and consensus-related information.
• Previous block hash: Links the block to its predecessor and creates a chronological chain.
• Transaction list: Contains validated transactions or state changes.
• Merkle root: Summarizes the transactions using a Merkle tree.
• Nonce or validator data: Used according to the selected consensus mechanism.

Working process:

1. A user creates and digitally signs a transaction.
2. The transaction is broadcast to peer nodes.
3. Nodes verify its signature and validity according to protocol rules.
4. Valid transactions are collected into a candidate block.
5. Miners or validators participate in consensus to propose and confirm the block.
6. The accepted block is linked to the previous block through its hash.
7. Nodes update their local copies of the ledger.

Changing an old block changes its hash and breaks the links to later blocks. Combined with distributed replication and consensus, this makes confirmed blockchain records tamper-evident and difficult to modify.

Blockchain security depends on several cryptographic mechanisms:

• Cryptographic hash functions: A hash function converts input data into a fixed-length digest. A secure hash function is deterministic, resistant to collisions, and highly sensitive to changes in input. Hashes link blocks and make unauthorized modifications detectable.
• Digital signatures: A user signs a transaction with a private key. Other participants verify the signature using the corresponding public key. This provides authentication, integrity, and authorization, although it does not by itself guarantee that a transaction will be accepted.
• Merkle trees: Transaction hashes are repeatedly combined until a single hash, called the Merkle root, remains. The Merkle root commits the block to all its transactions.
• Efficient verification: A Merkle proof allows a transaction to be checked using only a small set of hashes rather than downloading every transaction in the block.
• Tamper evidence: If transaction data changes, its transaction hash, Merkle root, and block hash also change.

Together, these tools protect transaction integrity, establish control of blockchain assets, and permit efficient verification of large ledgers.

Consensus is the process through which distributed nodes agree on a common ledger history or system state despite network delays, failures, or malicious participants.

Consensus is necessary because:

• There is no central administrator to decide which transactions are valid.
• Multiple nodes may receive transactions in different orders.
• Competing blocks may be proposed at nearly the same time.
• A malicious user may attempt to spend the same asset more than once.
• Some nodes may fail, disconnect, or send conflicting information.

A blockchain consensus mechanism generally provides:

• Validity: Accepted transactions satisfy protocol rules.
• Agreement: Honest nodes eventually recognize the same authoritative history.
• Ordering: Transactions are placed in a consistent sequence.
• Fault tolerance: The network can continue despite a bounded number of faulty participants.
• Finality: Accepted transactions eventually become irreversible or highly impractical to reverse.
• Sybil resistance: A participant cannot gain unlimited influence merely by creating many identities.

Consensus therefore replaces centralized decision-making with a protocol-based method of coordinating independent nodes.

Proof of Work and Proof of Stake are mechanisms for selecting block producers and protecting a blockchain from manipulation.

Proof of Work makes attacks expensive because an attacker must control substantial computational power. Its limitations include energy consumption and the possibility of mining-pool concentration.

Proof of Stake assigns influence according to stake and uses rewards and penalties to encourage honest validation. Its challenges include stake concentration, protocol complexity, and management of long-range or equivocation attacks.

Both mechanisms seek to provide consensus and Sybil resistance, but they use different scarce resources and economic incentives.

Decentralization is the distribution of authority, control, decision-making, data, and infrastructure among multiple independent participants instead of concentrating them in a single entity.

• Centralized system: One central authority controls the system, maintains data, and makes major decisions. It is usually efficient but creates a single point of control and failure.
• Decentralized system: Control is shared among several independent authorities or participants. Failure or censorship by one participant does not necessarily stop the entire system.
• Distributed system: Processing or data is spread across multiple networked computers. However, those computers may still be owned and controlled by one organization.

The terms distributed and decentralized are not identical. A cloud service may be geographically distributed but centrally governed. Conversely, a blockchain aims to combine distributed infrastructure with decentralized validation and governance.

Decentralization can exist at several levels, including infrastructure, data, consensus, governance, software development, ownership, and application access. A system should therefore be evaluated across multiple dimensions rather than labeled decentralized only because it uses many servers.

Blockchain enables decentralization by distributing responsibilities that are traditionally performed by a central intermediary.

• Replicated ledger: Multiple nodes store and verify the transaction history.
• Consensus protocol: Nodes agree on valid transactions and their ordering according to common rules.
• Public-key cryptography: Users control assets through private keys rather than through accounts managed solely by an institution.
• Cryptographic linking: Hash-linked blocks make historical changes detectable.
• Economic incentives: Rewards motivate miners or validators to secure the network.
• Penalties and costs: Proof of work, staking, and slashing make malicious behavior expensive.
• Smart contracts: Rules and agreements can be executed automatically by the network.
• Open participation: Permissionless blockchains may allow users, developers, and validators to participate without centralized approval.
• Independent verification: Participants can verify ledger data instead of trusting a third party's database.

Blockchain does not automatically guarantee complete decentralization. Control may still concentrate among validators, developers, token holders, infrastructure providers, or exchanges. Effective decentralization requires diversity across technical, economic, and governance layers.

Blockchain systems use several complementary methods of decentralization:

1. Disintermediation: A central intermediary is removed, allowing participants to interact directly through a peer-to-peer protocol.
2. Distributed ledger replication: Many nodes maintain copies of the ledger, reducing dependence on a single database.
3. Decentralized consensus: Independent miners or validators decide which state transitions are accepted.
4. Token-based incentives: Native tokens reward participants for validation, storage, liquidity, governance, or other services.
5. Smart contracts: Business rules are encoded and executed by a distributed virtual machine.
6. Decentralized governance: Protocol changes and shared resources may be managed through community processes, multisignature arrangements, or on-chain voting.
7. Decentralized identity and key ownership: Users manage credentials and assets using cryptographic keys.
8. Distributed storage: Data may be stored across peer-to-peer networks instead of on one organization's servers.
9. Open-source development: Public code allows independent review, modification, and implementation.

A robust decentralized application normally combines several of these methods. Using only a blockchain database while retaining centralized interfaces, governance, or data sources results in partial rather than complete decentralization.

A centralized application can follow several routes toward decentralization:

• Asset decentralization: Represent digital or physical assets as tokens controlled through user-held keys.
• Data decentralization: Move critical records from a private database to a shared ledger or decentralized storage system.
• Logic decentralization: Replace centrally executed business rules with smart contracts.
• Infrastructure decentralization: Distribute computation, node operation, storage, and network access among independent providers.
• Governance decentralization: Transfer decision-making from a company to a community, foundation, multisignature group, or DAO.
• Interface decentralization: Allow multiple independent applications to interact with the protocol instead of depending on one official website.
• Oracle decentralization: Obtain external data from multiple independent sources rather than a single data provider.
• Progressive decentralization: Begin with centralized control for rapid development and gradually transfer authority as the protocol matures.

A practical migration should identify trust assumptions, determine which components need decentralization, deploy transparent protocols, distribute control, and establish incentives for independent participation. The route chosen must balance security, performance, regulation, cost, and user experience.

Full ecosystem decentralization means that decentralization extends beyond the ledger to the complete environment required for a blockchain service to operate.

Important layers include:

• Consensus layer: No single validator, miner, or pool should control block production.
• Network layer: Peer-to-peer communication should not depend on one server or network provider.
• Data layer: Ledger and application data should be replicated or stored through resilient decentralized mechanisms.
• Computation layer: Smart-contract execution should occur across independent nodes.
• Application layer: Users should have access through multiple independently operated interfaces.
• Identity and custody layer: Users should be able to control keys and identities without mandatory centralized custody.
• Oracle layer: External information should come from diverse, independently verified sources.
• Governance layer: Protocol decisions should not be controlled by one company or small insider group.
• Development layer: Multiple teams should be able to audit and implement the protocol.
• Economic layer: Token ownership and resources should not be excessively concentrated.

Complete decentralization is difficult to achieve. Most real systems are decentralized to different degrees across these layers. The objective is to eliminate critical single points of failure, censorship, and unilateral control.

The terms are explained as follows:

• Node: A computer running blockchain software and participating in the network. Depending on its role, it may relay transactions, store the ledger, validate blocks, or produce blocks.
• Transaction: A digitally authorized instruction that transfers value or changes blockchain state.
• Block: A structured collection of validated transactions and metadata linked to an earlier block.
• Genesis block: The first block of a blockchain. It has no conventional predecessor and forms the foundation of the ledger history.
• Block height: The sequential position of a block relative to the genesis block. The genesis block is commonly assigned height zero, although conventions may vary.
• Confirmation: Evidence that a transaction has been included in an accepted block. Additional blocks built after that block increase confidence that the transaction will not be reversed.

These terms describe the basic operation of a blockchain: nodes validate transactions, transactions are grouped into blocks, blocks extend the chain from the genesis block, and confirmations indicate increasing transaction finality.

Blockchain networks can be classified according to ownership and participation rules:

• Public blockchain: The ledger is broadly accessible, and the network is not owned by one organization. Bitcoin and Ethereum are common examples.
• Private blockchain: One organization controls participation, governance, and often validation. It is used when confidentiality and administrative control are required.
• Consortium blockchain: A group of organizations jointly controls the network. No single member has complete authority.
• Permissionless blockchain: Any participant can generally submit transactions, read data, and potentially participate in consensus according to protocol requirements.
• Permissioned blockchain: Participants must receive authorization to perform specified roles such as reading, writing, validating, or administering the network.

A public blockchain is often permissionless, but the concepts are not identical. Public versus private mainly describes ownership and accessibility, whereas permissionless versus permissioned describes whether authorization is required for participation.

Public permissionless networks favor openness and censorship resistance. Private and consortium networks usually provide higher control, privacy, predictable performance, and regulatory compliance, but offer a lower degree of decentralization.

The blockchain trilemma refers to the difficulty of simultaneously achieving a high degree of decentralization, security, and scalability.

• Decentralization: Many independent participants can operate and verify the network.
• Security: The system resists attacks, fraud, censorship, and unauthorized state changes.
• Scalability: The network processes a high volume of transactions with acceptable speed and cost.

Increasing block size or hardware requirements may improve throughput but make node operation expensive, reducing decentralization. Reducing the number of validators may improve speed but create concentrated control. Increasing replication and verification can strengthen security but limit performance.

Approaches used to improve the balance include:

• Layer-2 networks: State channels and rollups process activity outside the base layer while using it for security or settlement.
• Sharding: Work and state are divided among multiple groups of nodes.
• Efficient consensus: Proof-of-stake and Byzantine fault-tolerant protocols may reduce resource consumption and confirmation time.
• Data-availability techniques: Specialized mechanisms ensure transaction data can be verified efficiently.
• Modular architecture: Execution, consensus, settlement, and data availability are assigned to specialized layers.

The trilemma is not an absolute law, but it highlights the engineering trade-offs involved in blockchain design.

Bitcoin prioritizes monetary security, simplicity, and censorship-resistant value transfer. Ethereum provides a programmable environment for decentralized applications. Hyperledger Fabric focuses on controlled enterprise collaboration, privacy, and configurable consensus.

Therefore, the appropriate platform depends on whether the application requires open participation, programmable public settlement, or permissioned organizational control.

A smart contract is a program stored and executed on a blockchain. It automatically applies predefined rules when users or other contracts invoke it. A decentralized application, or DApp, is an application whose critical logic or state is managed by smart contracts or another decentralized protocol.

Role in decentralization:

• Smart contracts replace some functions of centralized administrators with transparent code.
• They execute consistently across blockchain nodes.
• They can manage tokens, voting, lending, exchanges, escrow, insurance, and digital ownership.
• DApps allow users to interact directly with protocols through cryptographic wallets.
• Composable smart contracts can be combined to create larger decentralized services.

Limitations and risks:

• Programming errors may lead to irreversible losses.
• Smart contracts cannot directly access external information and therefore require oracles.
• Front-end websites and hosting may remain centralized.
• Upgradable contracts can introduce administrator control.
• Transaction fees and network congestion may affect usability.

A DApp is genuinely decentralized only when its contracts, data, governance, interfaces, and supporting infrastructure avoid critical centralized dependencies.

Benefits of blockchain-based decentralization:

• Fault tolerance: The system can remain available even if some nodes fail.
• Censorship resistance: No single party can easily block valid participation or transactions.
• Transparency: Shared records can improve auditability and accountability.
• User control: Participants can directly control assets through cryptographic keys.
• Reduced intermediary dependence: Peer-to-peer transactions may reduce administrative layers.
• Integrity: Consensus and cryptographic linking make unauthorized record changes difficult.
• Open innovation: Developers can build applications on shared public protocols.

Limitations:

• Lower performance: Distributed verification may be slower than centralized processing.
• Transaction costs: Fees can rise during periods of high demand.
• Governance difficulty: Community agreement on upgrades and disputes can be slow.
• Key-management risk: Lost or stolen private keys may cause permanent loss.
• Privacy concerns: Transparent ledgers can expose transaction patterns.
• Regulatory uncertainty: Legal treatment differs across jurisdictions.
• Concentration risks: Mining pools, validators, developers, exchanges, or token holders may accumulate influence.
• Oracle dependence: External data can reintroduce trusted intermediaries.

Blockchain decentralization is most valuable when multiple parties need shared state but cannot rely on a single trusted administrator.

A Byzantine fault occurs when a component of a distributed system behaves arbitrarily. A faulty or malicious node may send conflicting messages, provide false information, or deliberately attempt to disrupt agreement.

The Byzantine Generals Problem is a conceptual model in which separated participants must agree on one coordinated action even though some participants or communication channels may be unreliable. The challenge is to ensure that honest participants reach the same decision despite dishonest actors.

Byzantine fault tolerance, or BFT, is the ability of a distributed protocol to continue operating correctly while a bounded number of nodes exhibit Byzantine behavior.

In many classical BFT systems, consensus can tolerate fewer than one-third faulty participants. If the total number of validators is and the number of faulty validators is , a common requirement is:

Blockchain consensus addresses this problem through mechanisms such as proof of work, proof of stake, validator voting, cryptographic signatures, incentives, and penalties. These mechanisms allow honest nodes to identify an accepted ledger state without trusting every participant individually.

The double-spending problem is the risk that the same digital unit may be spent in two conflicting transactions. Unlike physical cash, digital information can be copied, so a decentralized currency requires a method to determine which transaction is authoritative.

Bitcoin addresses the problem as follows:

1. Transactions are digitally signed by the owners of the relevant private keys.
2. Nodes verify that transaction inputs refer to unspent outputs.
3. Valid transactions are broadcast throughout the peer-to-peer network.
4. Miners collect transactions into blocks and perform proof of work.
5. Nodes follow the valid chain with the greatest accumulated proof of work.
6. Conflicting transactions cannot both spend the same output in the accepted ledger history.
7. Additional blocks increase the cost of reorganizing the chain and reversing a confirmed transaction.

An attacker attempting double spending must create an alternative chain and overtake the honest network's accumulated work. The probability of success generally decreases as more confirmations are added, assuming honest miners control the majority of effective computational power.

Bitcoin therefore solves double spending through global transaction ordering, proof-of-work consensus, economic cost, and distributed verification rather than through a central payment authority.