Scribd
Upload
2 views

Mod-III ( Distributed consensus )

Uploaded by

thebengalnewssquare
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
2 views

Mod-III ( Distributed consensus )

Uploaded by

thebengalnewssquare
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Distributed Consensus in Blockchain Technology

Distributed consensus is the process by which nodes in a decentralized network agree on the validity of
transac ons and the current state of the blockchain ledger. Achieving consensus is cri cal for maintaining
the integrity, security, and trust in a blockchain system, especially since there is no central authority.

Consensus Mechanisms
Consensus mechanisms ensure that all nodes in the network agree on a single version of the blockchain,
despite failures or malicious actors. Various consensus mechanisms are designed for specific use cases.

Nakamoto Consensus
 Named a er Bitcoin's pseudonymous creator, Satoshi Nakamoto.
 Used in Bitcoin, it combines Proof of Work (PoW) with a longest-chain rule:

o Nodes (miners) compete to solve a computa onal puzzle.


o The first miner to solve it adds a new block to the blockchain.
o Nodes accept the chain with the most cumula ve computa onal work as the valid chain.

Consensus Mechanisms
1. Proof of Work (PoW):
 Concept: Miners solve cryptographic puzzles to validate transac ons and create new blocks.
 Key Features:
o Computa onally intensive.
o Ensures security through economic cost (electricity, hardware).
 Challenges:
o High energy consump on.
o Vulnerable to 51% a acks (if a single en ty controls over 50% of the network’s compu ng
power).
2. Proof of Stake (PoS):
 Concept: Validators are chosen to create blocks based on the amount of cryptocurrency they
"stake."
 Key Features:
o Energy-efficient compared to PoW.
o Security is based on the economic stake in the network.
 Challenges:

o Risk of centraliza on if wealthier par cipants dominate staking.


o "Nothing at Stake" problem (validators could validate mul ple conflic ng chains).
3. Proof of Burn (PoB):

 Concept: Par cipants burn cryptocurrency (send it to an unspendable address) to gain the right to
validate transac ons.
 Key Features:
o Combines elements of PoW and PoS.
o Demonstrates commitment to the network.
 Challenges:
o Burned assets are permanently removed, which might discourage par cipa on.
4. Difficulty Level:
 Adjusted dynamically in PoW systems to maintain consistent block crea on mes.
 Increases as network hash rate grows, ensuring fair compe on among miners.

Sybil A ack
A Sybil a ack occurs when a malicious actor creates mul ple fake iden es (nodes) to gain
dispropor onate influence over the network.
Mi ga on in Blockchain:
1. Proof-based Mechanisms:
o PoW: High computa onal cost makes Sybil a acks economically unfeasible.
o PoS: Requires staking assets, which is costly to fake.
2. Permissioned Models: Limit network access to verified par cipants.

Energy U liza on and Alterna ves

1. High Energy Use in PoW:


o Bitcoin and Ethereum (before Ethereum 2.0) require vast computa onal resources.
o Mining involves solving energy-intensive puzzles.
2. Energy-Efficient Alterna ves:
o Proof of Stake (PoS): Dras cally reduces energy consump on by elimina ng mining.
o Delegated Proof of Stake (DPoS): A subset of nodes are elected to validate transac ons.
o Proof of Authority (PoA): Trusted validators ensure block produc on in private or
consor um blockchains.
Consensus Models
I. Permissionless Models

 Open to anyone; no centralized authority.


 Examples: Bitcoin, Ethereum.
 Mechanisms:
o PoW: Security via computa onal effort.
o PoS: Security via staked cryptocurrency.
 Advantages:
o Fully decentralized.
o Trustless system.
 Challenges:
o Energy consump on.
o Scalability.
II. Permissioned Models
 Restricted to approved par cipants (e.g., enterprises, consor ums).
 Examples: Hyperledger, Corda.
 Mechanisms:
o Proof of Authority (PoA): Validators are pre-approved, ensuring efficiency.
o Prac cal Byzan ne Fault Tolerance (PBFT): Consensus through direct communica on among
nodes.
 Advantages:
o High efficiency.
o Scalable for enterprise use.

 Challenges:
o Par ally centralized.
o Requires trust in validators.

You might also like