Blockchain Architecture Design Unit 2 Easy Notes
Blockchain Architecture Design Unit 2 Easy Notes
Unit-2 Consensus
Edushine Classes
Follow Us
Download Notes : https://rzp.io/rzp/3GAooFts
https://telegram.me/rrsimtclasses/
Blockchain Design (BCS063)
2. Termination (Finality)
The consensus process must eventually end and produce a result (you can’t keep waiting
forever).
💡 A block must get confirmed within some time.
3. Validity (Correctness)
Only valid transactions and valid blocks should be accepted. Invalid data should be rejected.
💡 No double spending, no fake transactions allowed.
4. Fault Tolerance
It must work properly even if some nodes fail or act maliciously (this is known as Byzantine
Fault Tolerance).
💡 If 1 or 2 nodes are hacked or offline, the system still works.
5. Security
It should be resistant to attacks like:
• 51% attack (controlling the majority of the network)
• Sybil attack (creating fake identities).
6. Efficiency
The mechanism should not be too slow or waste too much energy (like PoW does).
7. Scalability
It should be able to handle many users and transactions as the network grows.
-
Blockchain Design (BCS063)
2. 🕒 Latency
• How much time does it take to confirm a transaction?
• PoW has high latency, PoS has low latency.
3. 💻 Computational Power
• PoW needs high energy (to solve puzzles), which makes it slow.
• PoS and others use less power → more scalable.
4. 🌐 Network Size
• More nodes = more time to reach agreement.
• Bigger network = more secure, but also slower.
5. ⚖️ Security vs Speed Trade-off
• If we want more speed, sometimes we need to reduce security or decentralization.
• Good consensus protocols balance speed, security, and decentralization.
🔸 Simple Example:
Socho ki blockchain ek highway hai. Agar traffic zyada ho gaya, to hum ek flyover
(Layer 2) bana dete hain jahan se fast vehicles jaa sakein. Fir sirf final result highway
pe aata hai.
🔸 Fayda:
• Fast transaction
• Kam fees
• Main blockchain pe load kam
2. Sharding
• The blockchain is divided into smaller parts called shards.
• Each shard handles its own data and transactions.
🔸 Example:
Socho ek school me ek hi teacher 100 students ko padha raha ho (slow hoga). Ab 10
teachers laga diye, har teacher 10-10 students ko padhaye. Speed badh gayi. Yehi
sharding ka idea hai.
🔸 Fayda:
• Saare shards parallel me kaam karte hain → fast processing
• Zyada log use kar sakte hain
3. Changing Consensus Mechanism
Switching from slow protocols like Proof of Work (PoW) to faster ones like:
Proof of Stake (PoS)
Delegated Proof of Stake (DPoS)
Byzantine Fault Tolerance (BFT)
🔸 Simple Language:
Socho ek kaam karne ka tareeka slow hai (manual typing), to hum uska automatic
system laga dete hain (voice typing) – kaam wahi, speed zyada!
4. Sidechains
A sidechain is a separate blockchain connected to the main blockchain.
✅ How it helps:
Heavy work is shifted to the sidechain
Main chain becomes less busy
Better performance
🔸 Example:
Socho ek school me ek extra classroom bana diya jisme students shift ho gaye. Ab
main class me bheed kam ho gayi. Yehi sidechain ka kaam hai.
🔸 Simple socho:
Ek train ke dabbe (block) me zyada log baith sakein ya train fast chale – to sab
destination pe jaldi pahuchenge.
- Download
DownloadNotes
Notes: :https://rzp.io/rzp/3GAooFts
https://rzp.io/rzp/3GAooFts
Blockchain Design (BCS063)
2. 👨💼 Identity Management
Goal:
All users are identified and verified before joining the network.
Why:
No anonymous users = easy to track actions = more trust.
Example:
In supply chain, each company has a verified identity on the blockchain.
3. ⚡ High Performance and Scalability
Goal:
Achieve fast transactions and good scalability with few trusted nodes.
Why:
In private networks, you don’t need to wait for thousands of users to
approve.
Example:
Faster settlement of payments between banks using blockchain.
4. 🛡️ Data Privacy
Goal:
Ensure confidentiality of data among selected participants.
Why:
Businesses don't want to expose sensitive data to outsiders.
Example:
Patient data in a healthcare blockchain is visible only to doctors and hospitals.
Example:
Use of Practical Byzantine Fault Tolerance (PBFT) or Raft.
7. ️ Customizability and Flexibility
Goal:
Allow changes in rules, roles, and smart contracts as per business need.
Why:
Organizations need control to update policies when required.
Example:
Role-based access: Manager can approve, employee can only view.
Cons:
Communication becomes slow if number of nodes becomes large
Example:
Digital currency systems in banks using blockchain.
🔸 Simple Example:
Socho ek classroom mein 10 students hain. Teacher nahi aayi hai,
lekin students milke decide karte hain ki kaunsa topic padhein. Agar
2-3 students jhooth bol bhi dein, baaki 7-8 log agar agree kar lein, to
woh topic final ho jata hai.
Yahi hai PBFT — jisme group milke vote karta hai aur majority ka
decision final hota hai.
Thank You…