Receive and fallback functions in Blockchain / Solidity - Time & Space Complexity

Time Complexity: Receive and fallback functions

O(n)

Understanding Time Complexity

When a smart contract receives Ether, it uses special functions called receive and fallback. Understanding how long these functions take to run helps us know how the contract behaves as more transactions come in.

We want to see how the time to handle incoming payments grows as the number of calls increases.

Scenario Under Consideration

Analyze the time complexity of the following Solidity contract snippet.

contract SimpleWallet {
    event Received(address, uint);
    
    receive() external payable {
        emit Received(msg.sender, msg.value);
    }

    fallback() external payable {
        // fallback logic
    }
}
    

This contract uses receive to accept Ether and emit an event, and fallback to handle other calls.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Each call to receive or fallback runs once per transaction.
• How many times: Once per incoming transaction; no loops inside these functions.

How Execution Grows With Input

Each transaction triggers the receive or fallback function once, so the work grows directly with the number of transactions.

Input Size (n)	Approx. Operations
10	10 function calls
100	100 function calls
1000	1000 function calls

Pattern observation: The total work increases in a straight line as more transactions arrive.

Final Time Complexity

Time Complexity: O(n)

This means the time to handle all incoming calls grows directly with the number of calls.

Common Mistake

[X] Wrong: "The receive or fallback function runs multiple times inside one transaction, so complexity is higher."

[OK] Correct: Each transaction triggers these functions only once, so no repeated loops happen inside them by default.

Interview Connect

Knowing how receive and fallback scale helps you design contracts that handle payments efficiently and predict costs as usage grows.

Self-Check

"What if the fallback function included a loop over an array of stored addresses? How would the time complexity change?"

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