Gas usage testing in Blockchain / Solidity - Time & Space Complexity

Time Complexity: Gas usage testing

O(n)

Understanding Time Complexity

When testing gas usage in blockchain smart contracts, we want to know how the cost changes as the input grows.

We ask: How does the gas needed increase when the contract processes more data?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

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

This function adds up all numbers in an array and returns the total sum.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop that adds each number to the total.
• How many times: It runs once for every element in the input array.

How Execution Grows With Input

As the array gets bigger, the number of additions grows the same way.

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

Pattern observation: The work grows directly with the number of items in the array.

Final Time Complexity

Time Complexity: O(n)

This means the gas cost grows in a straight line as the input size increases.

Common Mistake

[X] Wrong: "Gas cost stays the same no matter how many items are processed."

[OK] Correct: Each item requires work, so more items mean more gas is used.

Interview Connect

Understanding how gas usage grows helps you write efficient contracts and explain your code clearly in interviews.

Self-Check

"What if we changed the function to sum only the first half of the array? How would the time complexity change?"

Practice

1. What is the main purpose of gas usage testing in blockchain smart contracts?

easy

A. To check if the smart contract code has syntax errors

B. To increase the gas price for faster transactions

C. To verify the correctness of smart contract logic

D. To measure how much gas a function consumes when executed

Solution

1. Step 1: Understand gas usage testing

   Gas usage testing measures the amount of gas consumed by smart contract functions during execution.

2. Step 2: Differentiate from other tests

   It is not about syntax errors, logic correctness, or changing gas prices but about cost measurement.

3. Final Answer:

   To measure how much gas a function consumes when executed -> Option D

4. Quick Check:

   Gas usage testing = measure gas cost [OK]

Hint: Gas testing measures cost, not correctness or syntax [OK]

Common Mistakes:

• Confusing gas usage testing with syntax or logic testing
• Thinking gas usage testing changes gas prices
• Assuming gas usage testing verifies contract correctness

2. Which of the following is the correct way to get gas used from a transaction receipt in Solidity testing frameworks?

easy

A. const gasUsed = receipt.gasUsed;

B. const gasUsed = receipt.gas_price;

C. const gasUsed = receipt.gasLimit;

D. const gasUsed = receipt.gasCost;

Solution

1. Step 1: Identify the correct property for gas used

   Transaction receipts have a property called gasUsed that shows the gas consumed.

2. Step 2: Eliminate incorrect properties

   gas_price is gas price per unit, gasLimit is max gas allowed, and gasCost is not a standard property.

3. Final Answer:

   const gasUsed = receipt.gasUsed; -> Option A

4. Quick Check:

   Gas used = receipt.gasUsed [OK]

Hint: Gas used is in receipt.gasUsed property [OK]

Common Mistakes:

• Using gas_price instead of gasUsed
• Confusing gasLimit with gas used
• Trying to access non-existent gasCost property

3. Consider this JavaScript test snippet for a smart contract function:

const receipt = await contract.methods.myFunction().send({ from: user });
console.log(receipt.gasUsed);

What will this code output?

medium

A. An error because gasUsed is undefined

B. The gas price set for the transaction

C. The amount of gas used by myFunction execution

D. The total gas limit of the block

Solution

1. Step 1: Understand what receipt.gasUsed represents

   The receipt.gasUsed property contains the gas consumed by the transaction.

2. Step 2: Confirm the code logs gas used

   The code logs receipt.gasUsed, so it outputs the gas used by myFunction.

3. Final Answer:

   The amount of gas used by myFunction execution -> Option C

4. Quick Check:

   receipt.gasUsed logs gas used [OK]

Hint: receipt.gasUsed shows gas consumed by function call [OK]

Common Mistakes:

• Thinking gasUsed is gas price or block gas limit
• Expecting gasUsed to be undefined or cause error
• Confusing gasUsed with transaction cost in ether

4. You wrote this test code to measure gas usage:

const receipt = await contract.methods.transfer(to, amount).send({ from: sender });
const gasUsed = receipt.gasPrice;
console.log(gasUsed);

What is the error here?

medium

A. Using receipt.gasPrice instead of receipt.gasUsed to get gas consumed

B. Missing await keyword before contract method call

C. Incorrect method name; should be transferFrom

D. send() does not return a receipt object

Solution

1. Step 1: Check property used for gas consumption

   The code uses receipt.gasPrice, which is gas price per unit, not gas used.

2. Step 2: Identify correct property for gas used

   The correct property to get gas consumed is receipt.gasUsed.

3. Final Answer:

   Using receipt.gasPrice instead of receipt.gasUsed to get gas consumed -> Option A

4. Quick Check:

   Gas used = receipt.gasUsed, not gasPrice [OK]

Hint: Use receipt.gasUsed, not gasPrice, for gas consumption [OK]

Common Mistakes:

• Confusing gasPrice with gasUsed
• Omitting await causing promise issues
• Assuming send() returns something other than receipt

5. You want to compare gas usage of two smart contract functions, funcA and funcB, to find which is cheaper. You run:

const receiptA = await contract.methods.funcA().send({ from: user });
const receiptB = await contract.methods.funcB().send({ from: user });
console.log(receiptA.gasUsed < receiptB.gasUsed ? 'funcA cheaper' : 'funcB cheaper');

What is a potential issue with this approach?

hard

A. You cannot compare gasUsed values directly; must convert to ether

B. Gas usage can vary due to blockchain state; single runs may mislead

C. You must add gasPrice to gasUsed to get total cost

D. send() does not return gasUsed in receipt

Solution

1. Step 1: Understand gas usage variability

   Gas used depends on blockchain state and inputs; single runs may not reflect average cost.

2. Step 2: Identify why single comparison can mislead

   Different states or conditions can cause gas usage to fluctuate, so multiple tests or averaging is better.

3. Final Answer:

   Gas usage can vary due to blockchain state; single runs may mislead -> Option B

4. Quick Check:

   Gas varies by state; test multiple times [OK]

Hint: Gas varies; test multiple times for accurate comparison [OK]

Common Mistakes:

• Assuming gasUsed is fixed for all runs
• Adding gasPrice to gasUsed incorrectly
• Thinking gasUsed must convert to ether for comparison