Data types (uint, int, bool, address, string) in Blockchain / Solidity - Time & Space Complexity

Time Complexity: Data types (uint, int, bool, address, string)

O(n)

Understanding Time Complexity

When working with blockchain data types, it's important to know how operations on them grow as data size changes.

We want to see how the time to handle these types changes when the input gets bigger.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

contract Example {
    string public name;
    uint[] public numbers;

    function addNumber(uint num) public {
        numbers.push(num);
    }

    function getNameLength() public view returns (uint) {
        return bytes(name).length;
    }
}
    

This code stores a string and a list of numbers, adds numbers to the list, and gets the length of the string.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Accessing the length of the string by converting it to bytes.
• How many times: The length operation checks each byte once, so it depends on the string size.

How Execution Grows With Input

As the string gets longer, counting its length takes more steps.

Input Size (n)	Approx. Operations
10	10 steps to count bytes
100	100 steps to count bytes
1000	1000 steps to count bytes

Pattern observation: The time grows directly with the string length.

Final Time Complexity

Time Complexity: O(n)

This means the time to get the string length grows linearly with the string size.

Common Mistake

[X] Wrong: "Getting the length of a string is always instant and does not depend on size."

[OK] Correct: In blockchain, strings are stored as byte arrays, so counting length requires checking each byte, which takes more time for longer strings.

Interview Connect

Understanding how data types affect operation time helps you write efficient smart contracts and explain your reasoning clearly.

Self-Check

"What if we changed the string to a fixed-size byte array? How would the time complexity change?"

Practice

1. Which data type should you use in Solidity to store a number that can only be zero or positive?

easy

A. bool

B. uint

C. int

D. address

Solution

1. Step 1: Understand the difference between uint and int

   uint stands for unsigned integer, meaning it can only hold zero or positive numbers. int can hold both positive and negative numbers.

2. Step 2: Identify the correct type for only zero or positive numbers

   Since the question asks for numbers that are zero or positive only, uint is the correct choice.

3. Final Answer:

   uint -> Option B

4. Quick Check:

   Positive numbers = uint [OK]

Hint: Use uint for non-negative numbers only [OK]

Common Mistakes:

• Choosing int for positive-only numbers
• Confusing bool with numeric types
• Using address for numbers

2. Which of the following is the correct way to declare a boolean variable named isActive in Solidity?

easy

A. bool isActive = 0;

B. bool isActive = 1;

C. bool isActive = "true";

D. bool isActive = true;

Solution

1. Step 1: Recall the correct boolean values in Solidity

   Boolean variables can only be assigned true or false, not numbers or strings.

2. Step 2: Check each option for correct boolean assignment

   bool isActive = true; assigns true correctly. Options B and D use numbers, and C uses a string, which are invalid for bool.

3. Final Answer:

   bool isActive = true; -> Option D

4. Quick Check:

   Boolean = true or false [OK]

Hint: Assign true or false to bool variables [OK]

Common Mistakes:

• Using 1 or 0 instead of true/false
• Assigning strings like "true"
• Missing semicolon at the end

3. What will be the output of this Solidity code snippet?

int x = -5;
uint y = 10;
bool flag = (x < 0);
string memory text = "Hello";
address addr = 0x1234567890123456789012345678901234567890;

// Output values
x
flag
text
addr

medium

A. Compilation error due to address format

B. 5, false, Hello, 0x1234567890123456789012345678901234567890

C. -5, true, Hello, 0x1234567890123456789012345678901234567890

D. -5, false, "Hello", 0x0

Solution

1. Step 1: Analyze each variable's value

   x is -5 (signed int), flag is true because x < 0, text is "Hello", and addr is a valid address.

2. Step 2: Confirm output matches variable values

   -5, true, Hello, 0x1234567890123456789012345678901234567890 correctly lists all values as expected. 5, false, Hello, 0x1234567890123456789012345678901234567890 incorrectly changes x and flag. -5, false, "Hello", 0x0 has wrong flag and addr. Compilation error due to address format is wrong because the address format is valid.

3. Final Answer:

   -5, true, Hello, 0x1234567890123456789012345678901234567890 -> Option C

4. Quick Check:

   Variable values printed as is [OK]

Hint: Check variable types and values carefully [OK]

Common Mistakes:

• Assuming uint can hold negative values
• Confusing string quotes in output
• Thinking address format is invalid

4. Identify the error in this Solidity variable declaration:

address myAddress = "0xAbC1234567890";

medium

A. Address must be assigned without quotes

B. Address must be declared as string

C. Address cannot start with 0x

D. Address must be declared as bool

Solution

1. Step 1: Understand address assignment rules

   In Solidity, addresses are assigned as hexadecimal literals without quotes, not as strings.

2. Step 2: Identify the error in the code

   The code uses quotes around the address, making it a string, which is invalid for address type.

3. Final Answer:

   Address must be assigned without quotes -> Option A

4. Quick Check:

   Address literals have no quotes [OK]

Hint: Assign addresses without quotes to avoid errors [OK]

Common Mistakes:

• Using quotes around addresses
• Declaring address as string
• Removing 0x prefix from address

5. You want to store user information in a Solidity contract with these fields: user ID (positive number), username (text), active status (true/false), and wallet address. Which data types should you use for these fields?

hard

A. uint for user ID, string for username, bool for active status, address for wallet

B. int for user ID, string for username, uint for active status, address for wallet

C. uint for user ID, address for username, bool for active status, string for wallet

D. string for user ID, string for username, bool for active status, address for wallet

Solution

1. Step 1: Match each field to the correct data type

   User ID is a positive number, so uint fits. Username is text, so string. Active status is true/false, so bool. Wallet address is a blockchain address, so address.

2. Step 2: Verify options against these matches

   uint for user ID, string for username, bool for active status, address for wallet matches all fields correctly. Other options mix types incorrectly, like using int for user ID or swapping string and address.

3. Final Answer:

   uint for user ID, string for username, bool for active status, address for wallet -> Option A

4. Quick Check:

   Match field types carefully [OK]

Hint: Match data types to field meaning exactly [OK]

Common Mistakes:

• Using int for positive-only IDs
• Confusing string and address
• Using uint for boolean values