Enums in Blockchain / Solidity - Time & Space Complexity

Time Complexity: Enums

O(1)

Understanding Time Complexity

Enums help organize related values in blockchain code. Understanding their time complexity shows how fast operations with enums run as the program grows.

We want to know how the time to use enums changes when we work with more data.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

enum Status {
  Pending,
  Confirmed,
  Failed
}

function checkStatus(Status current) public pure returns (string memory) {
  if (current == Status.Pending) {
    return "Waiting";
  } else if (current == Status.Confirmed) {
    return "Success";
  } else {
    return "Error";
  }
}
    

This code defines an enum with three states and a function that checks the current state to return a message.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Simple if-else checks comparing enum values.
• How many times: Each call runs these checks once, no loops or recursion.

How Execution Grows With Input

Checking an enum value takes the same steps no matter how many enum options exist.

Input Size (n)	Approx. Operations
3 (enum states)	3 checks max
10 (if more states)	10 checks max
100 (many states)	100 checks max

Pattern observation: The number of checks grows directly with the number of enum states.

Final Time Complexity

Time Complexity: O(n)

This means the time to check an enum grows linearly with the number of enum options.

Common Mistake

[X] Wrong: "Enums always take constant time to check because they are simple values."

[OK] Correct: If you check enums with many if-else statements, the time grows with the number of options, not constant.

Interview Connect

Knowing how enum checks scale helps you write clear and efficient blockchain code. It shows you understand how small design choices affect speed.

Self-Check

"What if we replaced the if-else chain with a mapping from enum to string? How would the time complexity change?"

Practice

1. What is the main purpose of using enum in blockchain programming?

easy

A. To execute smart contracts faster

B. To create random numbers for cryptography

C. To store large amounts of data efficiently

D. To group related named values together for clarity and safety

Solution

1. Step 1: Understand enum purpose

   Enums group related named values, making code easier to read and safer.

2. Step 2: Compare options

   Only To group related named values together for clarity and safety correctly describes enums' main purpose in blockchain code.

3. Final Answer:

   To group related named values together for clarity and safety -> Option D

4. Quick Check:

   Enums group named values = A [OK]

Hint: Enums group fixed options with names, not data or speed [OK]

Common Mistakes:

• Confusing enums with random number generators
• Thinking enums store large data
• Believing enums speed up contract execution

2. Which of the following is the correct syntax to declare an enum named Status with values Pending, Active, and Closed in Solidity?

easy

A. enum Status: Pending, Active, Closed

B. enum Status = (Pending, Active, Closed);

C. enum Status { Pending, Active, Closed }

D. enum Status { 'Pending', 'Active', 'Closed' }

Solution

1. Step 1: Recall Solidity enum syntax

   In Solidity, enums are declared with enum Name { Value1, Value2, ... } without equals or colons.

2. Step 2: Check each option

   enum Status { Pending, Active, Closed } matches correct syntax; others use invalid symbols or quotes.

3. Final Answer:

   enum Status { Pending, Active, Closed } -> Option C

4. Quick Check:

   Solidity enum syntax uses braces and commas = C [OK]

Hint: Enums use braces and commas, no equals or quotes [OK]

Common Mistakes:

• Using equals sign instead of braces
• Adding quotes around enum values
• Using colons instead of braces

3. Given the Solidity enum declaration:

enum Role { User, Admin, Guest }

and the code:

Role userRole = Role.Admin;
if (userRole == Role.Guest) {
    return "Guest Access";
} else {
    return "Not Guest";
}

What will be the output?

medium

A. "Not Guest"

B. "Guest Access"

C. Compilation error

D. Runtime error

Solution

1. Step 1: Understand enum values and assignment

   Role.Admin is assigned to userRole, which is not equal to Role.Guest.

2. Step 2: Evaluate the if condition

   The condition userRole == Role.Guest is false, so the else branch runs returning "Not Guest".

3. Final Answer:

   "Not Guest" -> Option A

4. Quick Check:

   Role.Admin != Role.Guest, so output = "Not Guest" [OK]

Hint: Compare enum values directly; Admin ≠ Guest means else runs [OK]

Common Mistakes:

• Assuming Admin equals Guest
• Expecting compilation or runtime errors
• Confusing enum names with strings

4. Identify the error in this Solidity enum usage:

enum State { Created, Locked, Inactive }
State public state;
function setState(uint _state) public {
    state = _state;
}

medium

A. Enum declaration syntax is wrong

B. Cannot assign uint directly to enum variable

C. Function setState should be private

D. Missing return type in function

Solution

1. Step 1: Analyze enum assignment

   Enums require assignment from enum values, not raw uint integers.

2. Step 2: Check function assignment

   Assigning _state (uint) directly to state (enum) causes a type mismatch error.

3. Final Answer:

   Cannot assign uint directly to enum variable -> Option B

4. Quick Check:

   Enum variables need enum values, not uints [OK]

Hint: Assign enum values, not integers, to enum variables [OK]

Common Mistakes:

• Assigning integers directly to enums
• Thinking enum syntax is wrong
• Confusing function visibility with errors

5. You want to represent user roles in a blockchain contract using enums. You need to check if a user has either Admin or Moderator role to allow special access. Given:

enum Role { User, Admin, Moderator, Guest }

Which of the following Solidity code snippets correctly checks for this condition?

hard

A. if (userRole == Role.Admin || userRole == Role.Moderator) { /* allow access */ }

B. if (userRole == Role.Admin && userRole == Role.Moderator) { /* allow access */ }

C. if (userRole in [Role.Admin, Role.Moderator]) { /* allow access */ }

D. if (userRole.equals(Role.Admin) || userRole.equals(Role.Moderator)) { /* allow access */ }

Solution

1. Step 1: Understand logical conditions for enums

   To allow access if userRole is Admin OR Moderator, use logical OR (||) between equality checks.

2. Step 2: Evaluate each option

   if (userRole == Role.Admin || userRole == Role.Moderator) { /* allow access */ } uses correct OR condition; B uses AND which is impossible; C uses invalid syntax; A uses non-existent method equals.

3. Final Answer:

   if (userRole == Role.Admin || userRole == Role.Moderator) { /* allow access */ } -> Option A

4. Quick Check:

   Use || for OR between enum comparisons [OK]

Hint: Use || to check multiple enum values, not && or invalid syntax [OK]

Common Mistakes:

• Using && instead of || for OR condition
• Trying to use 'in' keyword for enums
• Calling non-existent methods on enums