Short-circuiting in conditions in Blockchain / Solidity - Time & Space Complexity

Time Complexity: Short-circuiting in conditions

O(n)

Understanding Time Complexity

When we use conditions that stop checking early, it can change how long the code runs.

We want to see how this early stopping affects the time it takes as inputs grow.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

function checkTransactions(transactions) {
  for (let i = 0; i < transactions.length; i++) {
    if (transactions[i].isValid && transactions[i].isConfirmed) {
      return true;
    }
  }
  return false;
}

This code checks a list of transactions and stops as soon as it finds one that is valid and confirmed.

Identify Repeating Operations

• Primary operation: Loop through the transactions array.
• How many times: Up to the length of the transactions list, but may stop early.

How Execution Grows With Input

As the number of transactions grows, the loop might check fewer items if it finds a match early.

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

Pattern observation: The loop can stop early, so the work done depends on where the first valid transaction appears.

Final Time Complexity

Time Complexity: O(n)

This means in the worst case, the code checks every transaction once as the list grows.

Common Mistake

[X] Wrong: "Because of short-circuiting, the code always runs fast no matter the input size."

[OK] Correct: Sometimes the matching transaction is at the end or missing, so the loop checks all items, making time grow with input size.

Interview Connect

Understanding how early stopping affects time helps you explain code efficiency clearly and shows you think about real-world data behavior.

Self-Check

"What if the condition checked two separate arrays instead of one? How would the time complexity change?"

Practice

1. What does short-circuiting mean in blockchain condition checks using && and ||?

easy

A. It stops checking further conditions once the result is decided.

B. It always checks all conditions regardless of the first result.

C. It reverses the order of condition checks.

D. It only works with numeric conditions.

Solution

1. Step 1: Understand short-circuiting concept

   Short-circuiting means the program stops checking conditions as soon as the final result is known.

2. Step 2: Apply to && and ||

   For &&, if the first condition is false, no need to check further. For ||, if the first condition is true, no need to check further.

3. Final Answer:

   It stops checking further conditions once the result is decided. -> Option A

4. Quick Check:

   Short-circuiting = Stops early [OK]

Hint: Stop checking when outcome is certain [OK]

Common Mistakes:

• Thinking all conditions always run
• Confusing && and || behavior
• Assuming short-circuiting only applies to numbers

2. Which of the following is the correct syntax for short-circuit AND in a blockchain smart contract condition?

easy

A. if (condition1 | condition2) { execute(); }

B. if (condition1 & condition2) { execute(); }

C. if (condition1 || condition2) { execute(); }

D. if (condition1 && condition2) { execute(); }

Solution

1. Step 1: Identify correct AND operator syntax

   The short-circuit AND operator is &&, which checks the second condition only if the first is true.

2. Step 2: Compare options

   if (condition1 && condition2) { execute(); } uses &&, correct for short-circuit AND. Options B and D use single & or | which are bitwise operators, not short-circuit. if (condition1 || condition2) { execute(); } uses OR operator.

3. Final Answer:

   if (condition1 && condition2) { execute(); } -> Option D

4. Quick Check:

   Short-circuit AND = && [OK]

Hint: Use double ampersand for AND short-circuit [OK]

Common Mistakes:

• Using single & instead of &&
• Confusing AND (&&) with OR (||)
• Using bitwise operators by mistake

3. Consider this blockchain code snippet:

bool a = false;
bool b = true;
if (a && (b = false)) { }
return b;

What is the returned value?

medium

A. false

B. Syntax error

C. true

D. Runtime error

Solution

1. Step 1: Analyze short-circuit AND behavior

   Since a is false, the b = false part is not executed due to short-circuiting.

2. Step 2: Determine final value of b

   b remains true because the assignment did not happen. So, return b; returns true.

3. Final Answer:

   true -> Option C

4. Quick Check:

   False && skips second = b stays true [OK]

Hint: False && skips right side, no assignment [OK]

Common Mistakes:

• Assuming b becomes false anyway
• Ignoring short-circuit effect
• Thinking code throws error

4. Find the error in this blockchain condition:

if (isValid || checkStatus()) {
  execute();
}

where checkStatus() is a function that must run always.

medium

A. Function checkStatus() may not run due to short-circuiting.

B. No error, code is correct.

C. Syntax error: missing semicolon.

D. Logical AND should be used instead of OR.

Solution

1. Step 1: Understand short-circuit OR behavior

   If isValid is true, checkStatus() will not run because of short-circuiting.

2. Step 2: Identify problem with function call

   Since checkStatus() must always run, using || causes it to sometimes skip, which is an error.

3. Final Answer:

   Function checkStatus() may not run due to short-circuiting. -> Option A

4. Quick Check:

   OR short-circuit skips right if left true [OK]

Hint: OR skips right if left true, function may not run [OK]

Common Mistakes:

• Assuming function always runs
• Confusing syntax error with logic error
• Using AND instead of OR without reason

5. You want to check two blockchain conditions: isOwner and hasBalance. You must run logAccess() always, but only execute transfer() if both conditions are true. Which code correctly uses short-circuiting?

hard

A. if (isOwner && hasBalance) { logAccess(); transfer(); }

B. logAccess(); if (isOwner && hasBalance) { transfer(); }

C. if (isOwner & hasBalance) { logAccess(); transfer(); }

D. if (isOwner && hasBalance && logAccess()) { transfer(); }

Solution

1. Step 1: Identify when logAccess() must run

   logAccess() must run always, so it should be called outside the condition.

2. Step 2: Check condition for transfer()

   transfer() runs only if both isOwner and hasBalance are true, so use && inside the if.

3. Step 3: Analyze options

   if (isOwner && hasBalance) { logAccess(); transfer(); } puts logAccess() inside the if, so it only runs if conditions true. if (isOwner && hasBalance && logAccess()) { transfer(); } calls logAccess() inside condition, so it may not run due to short-circuiting. if (isOwner & hasBalance) { logAccess(); transfer(); } uses single & which is bitwise, not short-circuit. logAccess(); if (isOwner && hasBalance) { transfer(); } calls logAccess() first always, then conditionally transfer().

4. Final Answer:

   logAccess(); if (isOwner && hasBalance) { transfer(); } -> Option B

5. Quick Check:

   Call always outside, conditionally inside [OK]

Hint: Call always-run functions outside conditions [OK]

Common Mistakes:

• Putting always-run function inside condition
• Using bitwise & instead of &&
• Calling functions in wrong order