Receive and fallback functions in Blockchain / Solidity - Mini Project: Build & Apply

Receive and fallback functions

📖 Scenario: You are creating a simple smart contract on Ethereum that can receive Ether payments. Sometimes, Ether is sent directly without calling any function, and sometimes it is sent with data that does not match any function. Your contract needs to handle both cases safely.

🎯 Goal: Build a Solidity contract that uses receive() and fallback() functions to accept Ether payments and log when each function is called.

📋 What You'll Learn

Create a contract named PaymentReceiver

Add a receive() function to accept plain Ether transfers

Add a fallback() function to accept Ether with unknown data

Emit events inside both functions to log which function was triggered

Test sending Ether with and without data to see which function runs

💡 Why This Matters

🌍 Real World

Smart contracts often need to accept payments safely. Using receive() and fallback() functions ensures the contract can handle Ether sent in different ways.

💼 Career

Understanding receive() and fallback() is essential for blockchain developers to write secure and reliable contracts that interact with Ether transfers.

1

Create the contract and event

Create a contract called PaymentReceiver and inside it, declare an event named ReceivedEther that logs an address sender and a uint amount.

Blockchain / Solidity

contract PaymentReceiver {
    // Your code here
}

Hint

Use the event keyword to declare an event inside the contract.

2

Add the receive() function

Inside the PaymentReceiver contract, add a receive() external payable function that emits the ReceivedEther event with msg.sender and msg.value.

Blockchain / Solidity

contract PaymentReceiver {
    event ReceivedEther(address sender, uint amount);
    
    // Add receive() function below
    // Your code here
}

Hint

The receive() function has no name and no arguments. It must be marked external payable.

3

Add the fallback() function

Inside the PaymentReceiver contract, add a fallback() external payable function that emits an event named FallbackCalled with msg.sender and msg.value. Declare the FallbackCalled event above.

Blockchain / Solidity

contract PaymentReceiver {
    event ReceivedEther(address sender, uint amount);
    
    receive() external payable {
        emit ReceivedEther(msg.sender, msg.value);
    }
    
    // Add fallback() function and event below
    // Your code here
}

Hint

The fallback() function is called when no other function matches. It must be external payable to accept Ether.

4

Test sending Ether and print logs

Add a public view function named getBalance() that returns the contract's Ether balance as uint. Then add a print statement to display the balance after deployment and after sending Ether (simulate this in your test environment).

Blockchain / Solidity

contract PaymentReceiver {
    event ReceivedEther(address sender, uint amount);
    event FallbackCalled(address sender, uint amount);
    
    receive() external payable {
        emit ReceivedEther(msg.sender, msg.value);
    }
    
    fallback() external payable {
        emit FallbackCalled(msg.sender, msg.value);
    }
    
    // Add getBalance() function below
    // Your code here
}

Hint

Use address(this).balance to get the contract's Ether balance.

Practice

1.

What is the main purpose of the receive() function in a Solidity contract?

easy

A. To reject all incoming Ether transfers

B. To handle calls to unknown functions with data

C. To execute code when a contract is created

D. To handle plain Ether transfers without any data

Solution

1. Step 1: Understand the role of receive()

   The receive() function is designed to accept Ether sent to the contract without any accompanying data.

2. Step 2: Differentiate from fallback function

   The fallback function handles calls with data or unknown function calls, while receive() is only for plain Ether transfers.

3. Final Answer:

   To handle plain Ether transfers without any data -> Option D

4. Quick Check:

   receive() handles plain Ether = C [OK]

Hint: receive() handles Ether with no data, fallback handles calls with data [OK]

Common Mistakes:

• Confusing receive() with fallback()
• Thinking receive() handles calls with data
• Assuming receive() rejects Ether

2.

Which of the following is the correct syntax for a receive() function in Solidity?

?

easy

A. receive() external payable {}

B. function receive() public {}

C. fallback() external payable {}

D. function receive() external {}

Solution

1. Step 1: Recall receive() function syntax

   The receive() function must be declared without the function keyword, must be external and payable.

2. Step 2: Check each option

   receive() external payable {} matches the correct syntax. Options using the function keyword are invalid, as are those lacking payable or using fallback instead of receive.

3. Final Answer:

   receive() external payable {} -> Option A

4. Quick Check:

   receive() syntax requires external payable = B [OK]

Hint: receive() has no function keyword, must be external payable [OK]

Common Mistakes:

• Adding 'function' keyword to receive()
• Omitting 'payable' modifier
• Confusing fallback() with receive()

3.

Consider this Solidity contract snippet:

contract Test {
    event Log(string func);

    receive() external payable {
        emit Log("receive");
    }

    fallback() external payable {
        emit Log("fallback");
    }
}

What event is emitted when someone sends 1 Ether with empty data?

medium

A. "receive"

B. "fallback"

C. No event emitted

D. Compilation error

Solution

1. Step 1: Identify the call type

   Sending Ether with empty data triggers the receive() function if it exists.

2. Step 2: Check which event is emitted

   The receive() function emits the event with "receive" string.

3. Final Answer:

   "receive" -> Option A

4. Quick Check:

   Empty data + Ether triggers receive() = "receive" [OK]

Hint: Empty data + Ether calls receive(), else fallback [OK]

Common Mistakes:

• Assuming fallback() triggers on empty data
• Thinking no event is emitted
• Confusing receive() and fallback() roles

4.

Given this contract snippet, what is the error?

contract Example {
    fallback() external {
        // code
    }

    receive() external {
        // code
    }
}

medium

A. receive() cannot be declared after fallback()

B. Both fallback and receive must be payable to accept Ether

C. fallback() must have the function keyword

D. No error, code is correct

Solution

1. Step 1: Check payable modifiers

   To accept Ether, both receive() and fallback() must be marked payable.

2. Step 2: Analyze given code

   Both functions lack payable, so contract cannot receive Ether via these functions.

3. Final Answer:

   Both fallback and receive must be payable to accept Ether -> Option B

4. Quick Check:

   Missing payable means no Ether acceptance = A [OK]

Hint: Missing payable means no Ether accepted by receive or fallback [OK]

Common Mistakes:

• Thinking order of functions matters
• Assuming fallback needs 'function' keyword
• Ignoring payable requirement

5.

You want your contract to accept Ether sent with or without data, and log which function was called. Which is the best way to implement this?

?

hard

A. Do not implement receive or fallback; use a regular payable function instead

B. Implement only receive() external payable function and ignore fallback

C. Implement both receive() external payable and fallback() external payable functions, each emitting a distinct event

D. Implement only fallback() external payable function to handle all cases

Solution

1. Step 1: Understand Ether transfer scenarios

   Ether can be sent with empty data (calls receive) or with data (calls fallback).

2. Step 2: Implement both functions to handle all cases

   Implementing both receive() and fallback() as external payable lets the contract accept Ether in both cases and emit distinct events.

3. Final Answer:

   Implement both receive() external payable and fallback() external payable functions, each emitting a distinct event -> Option C

4. Quick Check:

   Both functions needed for all Ether types = D [OK]

Hint: Use both receive() and fallback() payable to cover all Ether sends [OK]

Common Mistakes:

• Implementing only one function and missing some Ether transfers
• Ignoring fallback for calls with data
• Using regular payable function instead of receive/fallback