Cross-chain bridges in Blockchain / Solidity

Introduction

Cross-chain bridges let different blockchains talk to each other. This helps move tokens or data between them easily.

You want to send tokens from Ethereum to Binance Smart Chain.

You need to use a dApp on another blockchain without selling your assets.

You want to combine features from two blockchains in one app.

You want to trade tokens that exist on different blockchains.

You want to increase your options for decentralized finance (DeFi) across chains.

Syntax

Blockchain / Solidity

bridge.transfer(fromChain, toChain, asset, amount, userAddress)

fromChain: The blockchain you send assets from.

toChain: The blockchain you send assets to.

Examples

Sends 100 USDC tokens from Ethereum to Polygon for the user.

Blockchain / Solidity

bridge.transfer('Ethereum', 'Polygon', 'USDC', 100, '0xUserAddress')

Sends 50 BNB tokens from Binance Smart Chain to Avalanche.

Blockchain / Solidity

bridge.transfer('BinanceSmartChain', 'Avalanche', 'BNB', 50, '0xUserAddress')

Sample Program

This simple program shows moving USDC tokens from Ethereum to Polygon. It checks if enough tokens exist, then updates balances and prints the result.

Blockchain / Solidity

class SimpleBridge:
    def __init__(self):
        self.balances = {
            'Ethereum': {'USDC': 1000},
            'Polygon': {'USDC': 200}
        }

    def transfer(self, fromChain, toChain, asset, amount, user):
        if self.balances.get(fromChain, {}).get(asset, 0) < amount:
            print(f"Not enough {asset} on {fromChain} to transfer.")
            return
        self.balances[fromChain][asset] -= amount
        self.balances.setdefault(toChain, {}).setdefault(asset, 0)
        self.balances[toChain][asset] += amount
        print(f"Transferred {amount} {asset} from {fromChain} to {toChain} for {user}.")

bridge = SimpleBridge()
bridge.transfer('Ethereum', 'Polygon', 'USDC', 150, '0xUserAddress')
print('Ethereum balance:', bridge.balances['Ethereum']['USDC'])
print('Polygon balance:', bridge.balances['Polygon']['USDC'])

Important Notes

Cross-chain bridges often lock tokens on one chain and mint wrapped tokens on another.

Security is important because bridges can be targets for hacks.

Some bridges use validators or smart contracts to confirm transfers.

Summary

Cross-chain bridges connect different blockchains to move assets or data.

They help users use tokens and apps across multiple blockchains.

Bridges work by locking tokens on one chain and releasing or minting on another.

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