Why Distributed ledger concept in Blockchain / Solidity? - Purpose & Use Cases

The Big Idea

What if everyone could instantly trust shared records without needing to trust a single person?

The Scenario

Imagine a group of friends trying to keep track of who lent money to whom using a single notebook that only one person holds. Every time someone borrows or pays back money, they have to wait for that person to update the notebook.

The Problem

This manual method is slow because only one person can update the notebook at a time. It's also risky because if the notebook is lost or altered, everyone's records become unreliable. Mistakes or cheating can easily happen without a way to check.

The Solution

A distributed ledger shares the record-keeping across many people at once. Everyone has a copy that updates together, so no single person controls the data. This makes it fast, secure, and trustworthy because everyone can verify the information.

Before vs After

✗ Before

notebook = {}
notebook['Alice'] = 10  # Alice lent $10
# Only one person updates the notebook

✓ After

ledger = DistributedLedger()
ledger.record('Alice lends $10')
# Everyone has the same updated copy

What It Enables

It enables secure, transparent, and tamper-proof record-keeping shared across many participants without needing a central authority.

Real Life Example

Think of a group of neighbors sharing expenses for a community garden. Using a distributed ledger, everyone can see and agree on who paid what, preventing disputes and confusion.

Key Takeaways

Manual record-keeping is slow and risky when only one person controls the data.

Distributed ledgers share data across many copies, making it secure and trustworthy.

This concept allows groups to keep transparent and reliable records without a middleman.

Practice

1. What is the main purpose of a distributed ledger in blockchain technology?

easy

A. To store data only on one central computer

B. To share data across many computers to keep it safe and clear

C. To allow only one person to control the data

D. To make data unreadable for everyone

Solution

1. Step 1: Understand the concept of distributed ledger

   A distributed ledger shares data across many computers instead of one central place.

2. Step 2: Identify the main goal

   This sharing keeps data safe and clear for everyone involved.

3. Final Answer:

   To share data across many computers to keep it safe and clear -> Option B

4. Quick Check:

   Distributed ledger = shared safe data [OK]

Hint: Distributed means data is shared, not stored in one place [OK]

Common Mistakes:

• Thinking data is stored on a single computer
• Believing one person controls the ledger
• Confusing encryption with data sharing

2. Which of the following is the correct way to describe a block in a distributed ledger?

easy

A. A software program that controls the network

B. A single piece of data stored only on one computer

C. A secret key used to encrypt data

D. A group of transactions linked together and shared across the network

Solution

1. Step 1: Define what a block is in blockchain

   A block is a group of transactions bundled together.

2. Step 2: Understand its role in the network

   Blocks are linked and shared across the network to keep data consistent.

3. Final Answer:

   A group of transactions linked together and shared across the network -> Option D

4. Quick Check:

   Block = grouped shared transactions [OK]

Hint: Blocks group transactions and share them across the network [OK]

Common Mistakes:

• Thinking a block is just one piece of data
• Confusing blocks with encryption keys
• Believing blocks are software programs

3. Consider a simple blockchain network where each block contains a hash of the previous block. If the first block's hash is 'abc123', and the second block's hash is calculated as hash('abc123' + 'data2'), what happens if someone tries to change 'data2' in the second block?

medium

A. The first block's hash changes automatically

B. Nothing changes because hashes are not linked

C. The hash of the second block changes, breaking the chain

D. The network ignores the change and continues

Solution

1. Step 1: Understand hash linking in blocks

   Each block's hash depends on the previous block's hash and its own data.

2. Step 2: Effect of changing data in second block

   Changing 'data2' changes the second block's hash, which breaks the chain's integrity.

3. Final Answer:

   The hash of the second block changes, breaking the chain -> Option C

4. Quick Check:

   Changing data breaks hash chain [OK]

Hint: Changing block data changes its hash, breaking the chain [OK]

Common Mistakes:

• Thinking hashes are independent
• Believing first block changes automatically
• Assuming network ignores hash mismatches

4. A developer wrote this pseudocode for adding a new block to a distributed ledger:

function addBlock(data) {
  previousHash = getLastBlockHash()
  newHash = hash(data)
  block = { data: data, previousHash: previousHash, hash: newHash }
  ledger.append(block)
}

What is the main error in this code?

medium

A. The new hash should include the previous hash, not just data

B. The previous hash should be ignored when adding a block

C. The block should not store the previous hash

D. The ledger should be cleared before appending

Solution

1. Step 1: Review how block hashes are calculated

   A block's hash must include the previous block's hash and its own data to link blocks securely.

2. Step 2: Identify the mistake in hash calculation

   The code only hashes the data, missing the previous hash, breaking the chain security.

3. Final Answer:

   The new hash should include the previous hash, not just data -> Option A

4. Quick Check:

   Hash must include previous hash + data [OK]

Hint: Hash must combine previous hash and data to link blocks [OK]

Common Mistakes:

• Hashing only data without previous hash
• Ignoring previous hash in block structure
• Clearing ledger unnecessarily

5. You want to design a distributed ledger system where multiple participants can add transactions, but only valid transactions are accepted after consensus. Which approach best ensures data integrity and trust in this system?

hard

A. Use a consensus algorithm that requires agreement from most participants before adding a block

B. Allow any participant to add blocks without checks to speed up the process

C. Store the ledger on a single trusted server controlled by one participant

D. Encrypt all transactions so no one can see the data

Solution

1. Step 1: Understand consensus in distributed ledgers

   Consensus algorithms require most participants to agree on the data before adding it, ensuring trust.

2. Step 2: Evaluate options for data integrity and trust

   Allowing unchecked additions or central control reduces trust; encryption alone doesn't ensure consensus.

3. Final Answer:

   Use a consensus algorithm that requires agreement from most participants before adding a block -> Option A

4. Quick Check:

   Consensus ensures trust and data integrity [OK]

Hint: Consensus means most agree before adding data [OK]

Common Mistakes:

• Skipping consensus to speed up adding blocks
• Centralizing ledger storage
• Relying only on encryption without consensus