Proof of Work vs Proof of Stake in Blockchain / Solidity - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the consensus mechanism used in Proof of Work.

Blockchain / Solidity

consensus = "[1]"

Drag options to blanks, or click blank then click option'

AProof of Stake

BProof of Work

CDelegated Proof

DByzantine Fault

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing Proof of Work with Proof of Stake.

Using unrelated consensus mechanisms.

The consensus mechanism for Proof of Work is called "Proof of Work" itself, where miners solve puzzles to validate transactions.

2fill in blank

medium

Complete the code to define the consensus mechanism used in Proof of Stake.

Blockchain / Solidity

consensus = "[1]"

Drag options to blanks, or click blank then click option'

AProof of Stake

BProof of Work

CProof of Authority

DProof of Capacity

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing Proof of Stake with Proof of Work.

Choosing unrelated consensus types.

Proof of Stake uses the "Proof of Stake" consensus mechanism where validators are chosen based on their stake.

3fill in blank

hard

Fix the error in the code that calculates the mining reward for Proof of Work.

Blockchain / Solidity

reward = base_reward [1] difficulty

Drag options to blanks, or click blank then click option'

A*

B+

C-

D/

Attempts:

3 left

💡 Hint

Common Mistakes

Using addition instead of multiplication.

Using division or subtraction which do not make sense here.

The mining reward is typically calculated by multiplying the base reward by the difficulty factor.

4fill in blank

hard

Fill both blanks to complete the code that selects a validator in Proof of Stake based on stake and random chance.

Blockchain / Solidity

selected_validator = validators[[1]] if stake [2] threshold else None

Drag options to blanks, or click blank then click option'

Aindex

B>

C<

Drandom()

Attempts:

3 left

💡 Hint

Common Mistakes

Using random() as index which is incorrect.

Using wrong comparison operators.

The validator is selected by index if their stake is greater than the threshold.

5fill in blank

hard

Fill all three blanks to complete the code that calculates the chance to validate a block in Proof of Stake.

Blockchain / Solidity

chance = ([1] / total_stake) [2] random.random() and chance [3] threshold

Drag options to blanks, or click blank then click option'

Auser_stake

B>

C<

D*

Attempts:

3 left

💡 Hint

Common Mistakes

Using division instead of multiplication.

Using wrong comparison operators in conditions.

The chance is calculated by multiplying user stake over total stake by a random number, then checking if chance is less than threshold.

Practice

1. Which of the following best describes how Proof of Work (PoW) secures a blockchain?

easy

A. Users vote to approve each new block.

B. Validators are randomly chosen based on coin ownership.

C. Blocks are added by the oldest node in the network.

D. Miners solve complex puzzles using computing power to add blocks.

Solution

1. Step 1: Understand Proof of Work mechanism

   Proof of Work requires miners to solve difficult puzzles using computing power to find a valid block.

2. Step 2: Compare options with PoW concept

   Only Miners solve complex puzzles using computing power to add blocks. correctly describes miners solving puzzles with computing power.

3. Final Answer:

   Miners solve complex puzzles using computing power to add blocks. -> Option D

4. Quick Check:

   Proof of Work = computing puzzles solved by miners [OK]

Hint: PoW means solving puzzles with power, not random choice. [OK]

Common Mistakes:

• Confusing PoW with random validator selection.
• Thinking PoW uses voting instead of computing power.
• Assuming oldest node adds blocks in PoW.

2. Which syntax correctly represents a simple check for a Proof of Stake validator selection in pseudocode?

easy

A. if (random() < stake_percentage) { validateBlock(); }

B. while (computePower > threshold) { mineBlock(); }

C. for (node in network) { if (node.age > 10) { addBlock(); } }

D. if (votes > 50%) { approveBlock(); }

Solution

1. Step 1: Identify Proof of Stake selection logic

   Proof of Stake selects validators based on stake percentage, often modeled as a probability check.

2. Step 2: Match pseudocode to PoS logic

   if (random() < stake_percentage) { validateBlock(); } uses a random check against stake percentage, matching PoS validator selection.

3. Final Answer:

   if (random() < stake_percentage) { validateBlock(); } -> Option A

4. Quick Check:

   PoS validator selection uses stake-based probability [OK]

Hint: PoS uses stake chance, so random() < stake_percentage fits. [OK]

Common Mistakes:

• Choosing mining loop which is PoW, not PoS.
• Confusing age-based or vote-based logic with PoS.
• Ignoring stake percentage in validator selection.

3. Given this pseudocode for a simplified blockchain consensus:

stake = {"Alice": 30, "Bob": 70}
random_value = 65
if random_value < stake["Alice"]:
    validator = "Alice"
else:
    validator = "Bob"
print(validator)

What will be the output?

medium

A. Alice

B. Bob

C. Error

D. None

Solution

1. Step 1: Compare random_value with Alice's stake

   random_value is 65, Alice's stake is 30, so 65 < 30 is false.

2. Step 2: Determine validator based on condition

   Since condition is false, validator is set to "Bob" and printed.

3. Final Answer:

   Bob -> Option B

4. Quick Check:

   65 < 30 is false, so validator = Bob [OK]

Hint: Check if random_value is less than stake to pick validator. [OK]

Common Mistakes:

• Assuming 65 < 30 is true.
• Confusing stake values or variable names.
• Expecting syntax error from pseudocode.

4. This pseudocode tries to simulate Proof of Work mining but has an error:

nonce = 0
while nonce < 5:
    if hash(nonce) == target:
        print("Block mined")
    nonce += 1

What is the main problem here?

medium

A. The print statement is inside the if but no break after mining.

B. The loop never stops because nonce is never updated.

C. The hash function is not defined.

D. The nonce increment is outside the loop.

Solution

1. Step 1: Analyze loop and mining condition

   The loop increments nonce correctly and stops at 5, so no infinite loop.

2. Step 2: Check mining success handling

   When hash(nonce) == target, it prints "Block mined" but continues looping without stopping.

3. Step 3: Identify missing break after mining

   Without break, it may print multiple times or waste resources after mining success.

4. Final Answer:

   The print statement is inside the if but no break after mining. -> Option A

5. Quick Check:

   Missing break after mining causes extra loops [OK]

Hint: Stop loop after mining success with break to avoid extra work. [OK]

Common Mistakes:

• Thinking nonce is not incremented.
• Assuming infinite loop due to missing increment.
• Ignoring need to stop after mining success.

5. You want to design a hybrid blockchain consensus that uses Proof of Stake to select a validator and then Proof of Work to confirm the block. Which approach correctly combines both?

hard

A. All nodes solve PoW puzzles, then highest stake node adds block.

B. Random node adds block, then stake holders vote to confirm.

C. Select validator based on stake, then validator solves PoW puzzle to add block.

D. Validators solve PoW puzzles, but stake is ignored.

Solution

1. Step 1: Understand hybrid consensus design

   Hybrid means combining PoS for validator selection and PoW for block confirmation.

2. Step 2: Match options to hybrid logic

   Select validator based on stake, then validator solves PoW puzzle to add block. selects validator by stake, then that validator does PoW mining, fitting hybrid design.

3. Step 3: Eliminate incorrect options

   Options A, C, D either ignore stake or PoW or mix steps incorrectly.

4. Final Answer:

   Select validator based on stake, then validator solves PoW puzzle to add block. -> Option C

5. Quick Check:

   Hybrid = PoS select + PoW mining [OK]

Hint: Hybrid = stake picks validator, then PoW confirms block. [OK]

Common Mistakes:

• Ignoring PoW after validator selection.
• Assuming all nodes mine in hybrid.
• Confusing voting with PoW confirmation.