Sidechains in Blockchain / Solidity - Mini Project: Build & Apply

Sidechains

📖 Scenario: You are working on a blockchain project that uses sidechains to improve scalability and add new features without overloading the main blockchain.Sidechains are separate blockchains linked to the main chain, allowing assets to move between them securely.

🎯 Goal: Build a simple program that simulates transferring tokens from the main blockchain to a sidechain and back.This will help you understand how sidechains work in practice.

📋 What You'll Learn

Create a dictionary to represent the main blockchain balances

Create a dictionary to represent the sidechain balances

Create a variable for the transfer amount

Write code to move tokens from the main chain to the sidechain

Write code to move tokens back from the sidechain to the main chain

Print the final balances on both chains

💡 Why This Matters

🌍 Real World

Sidechains help blockchains handle more transactions and add new features without slowing down the main chain.

💼 Career

Understanding sidechains is useful for blockchain developers working on scalable and flexible blockchain solutions.

1

Create main blockchain balances

Create a dictionary called main_chain_balances with these exact entries: 'Alice': 100, 'Bob': 50, 'Charlie': 75.

Blockchain / Solidity

# Create the main_chain_balances dictionary with exact entries
# Your code here

Hint

Use curly braces {} to create a dictionary with keys and values.

2

Create sidechain balances and transfer amount

Create a dictionary called sidechain_balances with the same keys as main_chain_balances but all values set to 0. Then create a variable called transfer_amount and set it to 20.

Blockchain / Solidity

main_chain_balances = {'Alice': 100, 'Bob': 50, 'Charlie': 75}
# Create sidechain_balances dictionary with keys 'Alice', 'Bob', 'Charlie' all set to 0
# Create transfer_amount variable set to 20
# Your code here

Hint

Use the same keys as main_chain_balances but set all values to 0 for sidechain_balances.

Set transfer_amount to 20.

3

Transfer tokens from main chain to sidechain

Write a for loop using user to iterate over main_chain_balances. Inside the loop, subtract transfer_amount from main_chain_balances[user] and add transfer_amount to sidechain_balances[user].

Blockchain / Solidity

main_chain_balances = {'Alice': 100, 'Bob': 50, 'Charlie': 75}
sidechain_balances = {'Alice': 0, 'Bob': 0, 'Charlie': 0}
transfer_amount = 20
# Transfer tokens from main_chain_balances to sidechain_balances
# Your code here

Hint

Use a for loop to update balances for each user.

4

Transfer tokens back and print final balances

Write a for loop using user to iterate over sidechain_balances. Inside the loop, add transfer_amount back to main_chain_balances[user] and subtract transfer_amount from sidechain_balances[user]. Then print main_chain_balances and sidechain_balances.

Blockchain / Solidity

main_chain_balances = {'Alice': 100, 'Bob': 50, 'Charlie': 75}
sidechain_balances = {'Alice': 0, 'Bob': 0, 'Charlie': 0}
transfer_amount = 20
for user in main_chain_balances:
    main_chain_balances[user] -= transfer_amount
    sidechain_balances[user] += transfer_amount
# Transfer tokens back from sidechain_balances to main_chain_balances
# Print both dictionaries
# Your code here

Hint

Use a for loop to move tokens back. Then print both dictionaries to see final balances.

Practice

1.

What is the main purpose of a sidechain in blockchain technology?

easy

A. To store user passwords securely

B. To replace the main blockchain entirely

C. To mine new cryptocurrencies faster

D. To allow assets to move between blockchains without changing the main chain

Solution

1. Step 1: Understand sidechain function

   Sidechains connect to a main blockchain to move assets safely without altering the main chain.

2. Step 2: Compare options

   Only To allow assets to move between blockchains without changing the main chain describes this purpose correctly; others describe unrelated functions.

3. Final Answer:

   To allow assets to move between blockchains without changing the main chain -> Option D

4. Quick Check:

   Sidechains move assets safely = C [OK]

Hint: Sidechains move assets without changing main chain [OK]

Common Mistakes:

• Thinking sidechains replace main blockchain
• Confusing sidechains with password storage
• Assuming sidechains speed up mining

2.

Which of the following is the correct way to describe the process of moving assets from the main chain to a sidechain?

lockOnMainChain() and issueOnSidechain() are functions.

easy

A. issueOnSidechain(); lockOnMainChain();

B. lockOnMainChain(); issueOnSidechain();

C. burnOnMainChain(); issueOnSidechain();

D. issueOnSidechain(); burnOnMainChain();

Solution

1. Step 1: Understand asset transfer steps

   Assets are locked on the main chain first, then issued on the sidechain.

2. Step 2: Match function order

   lockOnMainChain(); issueOnSidechain(); correctly calls lockOnMainChain() before issueOnSidechain().

3. Final Answer:

   lockOnMainChain(); issueOnSidechain(); -> Option B

4. Quick Check:

   Lock then issue = A [OK]

Hint: Lock assets first, then issue on sidechain [OK]

Common Mistakes:

• Issuing before locking assets
• Using burn instead of lock for main chain
• Mixing function order

3.

Consider this pseudocode for moving assets from a sidechain back to the main chain:

burnOnSidechain()
unlockOnMainChain()

What will be the output if burnOnSidechain() fails?

medium

A. Assets remain locked on the main chain

B. Assets are unlocked on the main chain anyway

C. Assets are burned on the main chain

D. Assets are duplicated on both chains

Solution

1. Step 1: Analyze burn failure effect

   If burnOnSidechain() fails, assets are not removed from the sidechain.

2. Step 2: Understand unlock condition

   unlockOnMainChain() should only run after successful burn; if burn fails, unlock does not happen.

3. Final Answer:

   Assets remain locked on the main chain -> Option A

4. Quick Check:

   Burn must succeed before unlock = D [OK]

Hint: Burn sidechain assets before unlocking main chain [OK]

Common Mistakes:

• Assuming unlock happens even if burn fails
• Thinking assets get duplicated
• Confusing burn with lock

4.

Find the error in this pseudocode for transferring assets to a sidechain:

lockOnMainChain()
issueOnSidechain()
unlockOnMainChain()

medium

A. Unlocking main chain assets immediately after issuing is incorrect

B. Locking assets should happen after issuing

C. Issuing on sidechain should be replaced with burning

D. Unlocking main chain assets is required here

Solution

1. Step 1: Review transfer steps

   Assets must stay locked on the main chain until they are returned from the sidechain.

2. Step 2: Identify incorrect unlock

   Unlocking immediately after issuing breaks asset security; unlock should happen only when assets return.

3. Final Answer:

   Unlocking main chain assets immediately after issuing is incorrect -> Option A

4. Quick Check:

   Unlock only after return = A [OK]

Hint: Don't unlock main chain assets too early [OK]

Common Mistakes:

• Unlocking main chain assets too soon
• Confusing issue with burn
• Reversing lock and issue order

5.

You want to design a sidechain system that allows fast transactions but ensures no asset duplication. Which approach best achieves this?

Choose the correct sequence of actions when moving assets from main chain to sidechain and back.

hard

A. Issue on sidechain -> Lock on main chain -> Unlock on main chain -> Burn on sidechain

B. Burn on main chain -> Issue on sidechain -> Lock on sidechain -> Unlock on main chain

C. Lock on main chain -> Issue on sidechain -> Burn on sidechain -> Unlock on main chain

D. Unlock on main chain -> Burn on sidechain -> Lock on main chain -> Issue on sidechain

Solution

1. Step 1: Understand asset safety steps

   To avoid duplication, assets must be locked on the main chain before issuing on sidechain, and burned on sidechain before unlocking main chain.

2. Step 2: Match correct sequence

   Lock on main chain -> Issue on sidechain -> Burn on sidechain -> Unlock on main chain follows the correct order: lock -> issue -> burn -> unlock, ensuring assets exist only in one place at a time.

3. Final Answer:

   Lock on main chain -> Issue on sidechain -> Burn on sidechain -> Unlock on main chain -> Option C

4. Quick Check:

   Lock, issue, burn, unlock = B [OK]

Hint: Lock before issue; burn before unlock to avoid duplicates [OK]

Common Mistakes:

• Issuing before locking assets
• Unlocking main chain too early
• Burning assets on wrong chain