Return values in Blockchain / Solidity - Time & Space Complexity

Time Complexity: Return values

O(1)

Understanding Time Complexity

When we look at return values in blockchain code, we want to know how the time to get that value changes as the input grows.

We ask: How long does it take to produce the return value when the input size changes?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

function getBalance(address user) public view returns (uint) {
    return balances[user];
}

This code returns the balance of a user from a stored mapping.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Direct lookup in a mapping (like a dictionary).
• How many times: Exactly once per call, no loops or repeated steps.

How Execution Grows With Input

Getting the balance is a simple lookup that does not depend on how many users or balances exist.

Input Size (n)	Approx. Operations
10	1
100	1
1000	1

Pattern observation: The time stays the same no matter how many users there are.

Final Time Complexity

Time Complexity: O(1)

This means the time to get a return value is constant and does not grow with input size.

Common Mistake

[X] Wrong: "Looking up a user's balance takes longer if there are more users."

[OK] Correct: The lookup uses a direct key access, so it takes the same time regardless of total users.

Interview Connect

Understanding that return values from mappings are constant time helps you explain efficient data access in blockchain contracts clearly and confidently.

Self-Check

"What if the return value was computed by summing all balances instead of a direct lookup? How would the time complexity change?"

Practice

1.

What does the return statement do in a blockchain smart contract function?

easy

A. It sends a value back to the caller of the function.

B. It stops the contract from deploying.

C. It creates a new transaction on the blockchain.

D. It changes the contract's address.

Solution

1. Step 1: Understand the purpose of return

   The return statement is used inside a function to send a value back to whoever called the function.

2. Step 2: Identify what return does in blockchain functions

   In smart contracts, returning a value allows the caller to receive data from the function execution.

3. Final Answer:

   It sends a value back to the caller of the function. -> Option A

4. Quick Check:

   Return sends value back [OK]

Hint: Return sends data back to caller, not change contract [OK]

Common Mistakes:

• Thinking return creates transactions
• Confusing return with contract deployment
• Believing return changes contract address

2.

Which of the following is the correct syntax to specify a function that returns an uint in Solidity?

function getValue() _____ { return 42; }

easy

A. returns uint

B. return uint

C. return (uint)

D. returns (uint)

Solution

1. Step 1: Recall Solidity function return syntax

   In Solidity, the correct way to specify a return type is returns (type) after the function parentheses.

2. Step 2: Match the syntax with options

   returns (uint) uses returns (uint), which is the correct syntax.

3. Final Answer:

   returns (uint) -> Option D

4. Quick Check:

   Solidity uses returns (type) [OK]

Hint: Remember: returns keyword with parentheses for type [OK]

Common Mistakes:

• Omitting parentheses around type
• Using return instead of returns
• Placing return type inside function body

3.

What will be the output of this Solidity function call?

function multiply(uint a, uint b) public pure returns (uint) { return a * b; }

Calling multiply(3, 4) returns:

medium

A. 7

B. 12

C. 34

D. Error

Solution

1. Step 1: Understand the function logic

   The function multiplies two unsigned integers a and b and returns the product.

2. Step 2: Calculate the product of 3 and 4

   3 multiplied by 4 equals 12, so the function returns 12.

3. Final Answer:

   12 -> Option B

4. Quick Check:

   3 * 4 = 12 [OK]

Hint: Multiply inputs and return result [OK]

Common Mistakes:

• Adding instead of multiplying
• Concatenating numbers as strings
• Expecting syntax error

4.

Identify the error in this Solidity function that is supposed to return a bool:

function isEven(uint num) public pure returns (bool) { if (num % 2 == 0) { true; } else { false; } }

medium

A. Missing return statements before true and false.

B. The function should return uint instead of bool.

C. The modulus operator % is not allowed in Solidity.

D. The function should be marked as view instead of pure.

Solution

1. Step 1: Check the return statements

   The function uses true; and false; without return, so it does not actually return any value.

2. Step 2: Understand Solidity return requirements

   Every return value must be preceded by the return keyword to send the value back.

3. Final Answer:

   Missing return statements before true and false. -> Option A

4. Quick Check:

   Return keyword needed before values [OK]

Hint: Always use return before the value to send back [OK]

Common Mistakes:

• Omitting return keyword
• Confusing pure and view modifiers
• Thinking modulus operator is invalid

5.

You want to write a Solidity function that returns the sum of all elements in a uint[] array. Which of the following implementations correctly returns the sum?

function sumArray(uint[] memory arr) public pure returns (uint) { uint total = 0; for (uint i = 0; i < arr.length; i++) { total += arr[i]; } _____ }

hard

A. return arr.length;

B. return i;

C. return total;

D. return arr;

Solution

1. Step 1: Understand the function logic

   The function sums all elements in the array by adding each element to total.

2. Step 2: Identify the correct return value

   After the loop, the sum is stored in total, so returning total gives the correct sum.

3. Final Answer:

   return total; -> Option C

4. Quick Check:

   Return the sum variable total [OK]

Hint: Return the accumulator variable holding the sum [OK]

Common Mistakes:

• Returning array length instead of sum
• Returning loop index variable
• Returning the whole array instead of a value