Cross-chain bridges in Blockchain / Solidity - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a cross-chain bridge in blockchain?

A cross-chain bridge is a tool that connects two different blockchain networks, allowing tokens or data to move between them securely.

intermediate

How does a cross-chain bridge typically transfer tokens?

It locks tokens on the source chain and mints equivalent tokens on the destination chain, or burns tokens on one chain and releases them on the other.

intermediate

What is the role of validators or relayers in cross-chain bridges?

Validators or relayers verify transactions on one chain and communicate them to the other chain to ensure secure and accurate transfers.

advanced

Name one common security risk associated with cross-chain bridges.

One common risk is the possibility of smart contract bugs or exploits that can lead to loss of funds during token transfers.

beginner

Why are cross-chain bridges important for blockchain ecosystems?

They enable interoperability, allowing users to use assets and data across different blockchains, increasing flexibility and utility.

What does a cross-chain bridge do?

A Encrypts blockchain transactions

B Connects two blockchains to transfer tokens or data

C Mines new blocks faster

D Creates new tokens on a single blockchain

A cross-chain bridge connects two blockchains to allow token or data transfer between them.

Which process is commonly used by bridges to move tokens between chains?

A Lock and mint

B Mining and staking

C Hashing and encrypting

D Forking and merging

Bridges often lock tokens on one chain and mint equivalent tokens on the other.

Who verifies transactions in a cross-chain bridge?

A Validators or relayers

B Miners only

C End users

D Smart contract creators

Validators or relayers check and relay transactions between chains.

What is a major security concern for cross-chain bridges?

A Too many users

B Slow internet connection

C High electricity usage

D Smart contract vulnerabilities

Smart contract bugs can cause loss of funds in bridges.

Why do blockchains need cross-chain bridges?

A To reduce transaction fees on one chain

B To increase block size

C To allow assets to move between different blockchains

D To create new cryptocurrencies

Cross-chain bridges enable asset and data movement across blockchains.

Explain how a cross-chain bridge transfers tokens between two blockchains.

Think about what happens to tokens on both chains during transfer.

Describe one security risk of using cross-chain bridges and how it might affect users.

Consider what could go wrong in the bridge's code.

Practice

1. What is the main purpose of a cross-chain bridge in blockchain technology?

easy

A. To mine new blocks faster on a single blockchain

B. To increase the block size limit on a blockchain

C. To create new cryptocurrencies from scratch

D. To connect different blockchains and allow asset transfers between them

Solution

1. Step 1: Understand the role of cross-chain bridges

   Cross-chain bridges enable communication and asset transfers between different blockchains.

2. Step 2: Compare options with this role

   Only To connect different blockchains and allow asset transfers between them describes connecting blockchains and transferring assets, which matches the bridge's purpose.

3. Final Answer:

   To connect different blockchains and allow asset transfers between them -> Option D

4. Quick Check:

   Cross-chain bridge = connect blockchains [OK]

Hint: Bridges connect blockchains to move tokens or data [OK]

Common Mistakes:

• Confusing bridges with mining or block creation
• Thinking bridges create new cryptocurrencies
• Assuming bridges only increase block size

2. Which of the following is the correct basic step in a cross-chain bridge operation?

easy

A. Lock tokens on the source chain and mint equivalent tokens on the destination chain

B. Mint tokens on the source chain and burn on the destination chain

C. Burn tokens on the source chain and mine new tokens on the same chain

D. Transfer tokens directly without locking or minting

Solution

1. Step 1: Recall how cross-chain bridges work

   They lock tokens on the source chain to prevent double spending and mint equivalent tokens on the destination chain.

2. Step 2: Match this with the options

   Lock tokens on the source chain and mint equivalent tokens on the destination chain correctly describes locking on source and minting on destination, which is the standard process.

3. Final Answer:

   Lock tokens on the source chain and mint equivalent tokens on the destination chain -> Option A

4. Quick Check:

   Lock then mint = bridge step [OK]

Hint: Tokens are locked first, then minted on another chain [OK]

Common Mistakes:

• Mixing up minting and burning order
• Thinking tokens transfer directly without locking
• Assuming minting happens on source chain

3. Consider this simplified pseudocode for a cross-chain bridge function:

function bridgeTransfer(amount, sourceChain, destChain) {
  lockTokens(sourceChain, amount);
  mintTokens(destChain, amount);
  return 'Transfer complete';
}

What will be the output when calling bridgeTransfer(100, 'ChainA', 'ChainB')?

medium

A. 'Transfer complete'

B. Error: lockTokens undefined

C. 'Tokens locked on ChainA'

D. 100

Solution

1. Step 1: Analyze the function steps

   The function calls lockTokens and mintTokens, then returns the string 'Transfer complete'.

2. Step 2: Determine the output of the function call

   Assuming lockTokens and mintTokens work correctly, the function returns 'Transfer complete'.

3. Final Answer:

   'Transfer complete' -> Option A

4. Quick Check:

   Function returns 'Transfer complete' [OK]

Hint: Look at the return statement for output [OK]

Common Mistakes:

• Confusing function calls with return value
• Assuming intermediate functions print output
• Ignoring the return statement

4. The following code snippet is intended to lock tokens on the source chain and mint on the destination chain, but it has a bug:

function bridgeTransfer(amount, sourceChain, destChain) {
  lockTokens(destChain, amount);
  mintTokens(sourceChain, amount);
  return 'Transfer complete';
}

What is the bug in this code?

medium

A. The function uses incorrect function names

B. The lockTokens and mintTokens calls have swapped chain arguments

C. The function does not return any value

D. The amount parameter is missing

Solution

1. Step 1: Check the order of locking and minting

   Tokens should be locked on the source chain and minted on the destination chain.

2. Step 2: Identify the argument mismatch

   The code locks tokens on destChain and mints on sourceChain, which is reversed.

3. Final Answer:

   The lockTokens and mintTokens calls have swapped chain arguments -> Option B

4. Quick Check:

   Lock on source, mint on destination [OK]

Hint: Lock on source chain, mint on destination chain [OK]

Common Mistakes:

• Swapping source and destination chains
• Forgetting to return a value
• Using wrong function names

5. You want to design a cross-chain bridge that prevents double spending by ensuring tokens are locked before minting on the destination chain. Which approach best achieves this in a smart contract environment?

hard

A. Allow users to mint tokens on destination chain without locking on source chain

B. Mint tokens on destination chain first, then lock tokens on source chain

C. Use an event listener to confirm tokens are locked on source chain before minting on destination chain

D. Transfer tokens directly between chains without any locking or minting

Solution

1. Step 1: Understand double spending prevention

   Tokens must be locked on the source chain before minting on the destination chain to avoid duplicates.

2. Step 2: Evaluate approaches for enforcing this

   Using an event listener to confirm locking before minting ensures the correct order and security.

3. Final Answer:

   Use an event listener to confirm tokens are locked on source chain before minting on destination chain -> Option C

4. Quick Check:

   Confirm lock event before minting [OK]

Hint: Confirm lock event before minting tokens [OK]

Common Mistakes:

• Minting before locking causes double spending
• Allowing mint without lock breaks security
• Skipping locking or minting steps