Efficient data structures in Blockchain / Solidity

Introduction

Efficient data structures help store and manage data quickly and save space. This is very important in blockchain because every byte and operation costs money and time.

When you need to store transaction records in a way that is fast to access and verify.

When you want to keep track of account balances without using too much storage.

When you need to quickly check if a piece of data exists on the blockchain.

When you want to organize smart contract data to reduce gas fees.

When you want to build a blockchain application that handles many users efficiently.

Syntax

Blockchain / Solidity

struct DataStructureName {
    // fields to store data
};

mapping(KeyType => ValueType) public dataMap;

// Example: Using arrays, mappings, structs, or trees depending on need

In blockchain, common data structures include mappings (like dictionaries), arrays, and structs to organize data.

Choosing the right data structure can save gas fees and speed up your smart contract.

Examples

This example shows a struct to hold user data and an array to store many users.

Blockchain / Solidity

struct User {
    uint id;
    string name;
}

User[] public users;

This mapping stores the balance for each user address. It is fast to look up and update.

Blockchain / Solidity

mapping(address => uint) public balances;

This mapping helps quickly check if some data (identified by a hash) exists on the blockchain.

Blockchain / Solidity

mapping(bytes32 => bool) public dataExists;

Sample Program

This smart contract uses a struct and an array to store users and a mapping to store balances. It shows how to add users and check balances efficiently.

Blockchain / Solidity

pragma solidity ^0.8.0;

contract EfficientData {
    struct User {
        uint id;
        string name;
    }

    User[] public users;
    mapping(address => uint) public balances;

    function addUser(uint _id, string memory _name) public {
        users.push(User(_id, _name));
        balances[msg.sender] = 100;
    }

    function getUserCount() public view returns (uint) {
        return users.length;
    }

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

Important Notes

Mappings do not store keys, so you cannot iterate over them directly.

Arrays allow iteration but can be costly if they grow too large.

Structs help group related data together for clarity and efficiency.

Summary

Efficient data structures save space and gas in blockchain apps.

Use mappings for fast lookups by key.

Use structs and arrays to organize complex data.

Practice

1. Which data structure is best for quickly finding a user's balance by their blockchain address?

easy

A. Array

B. Mapping (key-value pairs)

C. Struct

D. Linked list

Solution

1. Step 1: Understand the need for quick lookup

   We want to find a balance by address fast, so we need a structure that supports direct access by key.

2. Step 2: Identify the best data structure

   Mappings provide key-value pairs allowing O(1) access by address, unlike arrays or structs which require searching.

3. Final Answer:

   Mapping (key-value pairs) -> Option B

4. Quick Check:

   Fast key-based lookup = Mapping [OK]

Hint: Use mappings for direct key lookups in blockchain [OK]

Common Mistakes:

• Choosing arrays which require looping to find an address
• Using structs alone without a key for lookup
• Thinking linked lists are efficient for random access

2. Which of the following is the correct syntax to declare a mapping from address to uint in Solidity?

easy

A. mapping(address => uint) balances;

B. mapping(address, uint) balances;

C. mapping[address] uint balances;

D. mapping{address: uint} balances;

Solution

1. Step 1: Recall Solidity mapping syntax

   Mappings use the syntax mapping(keyType => valueType) variableName;

2. Step 2: Match the correct syntax

   mapping(address => uint) balances; matches this exactly: mapping(address => uint) balances;

3. Final Answer:

   mapping(address => uint) balances; -> Option A

4. Quick Check:

   Correct mapping syntax uses '=>' [OK]

Hint: Remember mapping uses '=>' between key and value types [OK]

Common Mistakes:

• Using commas instead of '=>' in mapping
• Using square brackets or curly braces incorrectly
• Omitting the semicolon at the end

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

struct User { uint id; string name; }
User[] users;
users.push(User(1, "Alice"));
users.push(User(2, "Bob"));
string memory name = users[1].name;

medium

A. "Alice"

B. Empty string

C. Compilation error

D. "Bob"

Solution

1. Step 1: Understand array indexing

   Arrays start at index 0, so users[0] is Alice, users[1] is Bob.

2. Step 2: Identify the accessed element

   The code accesses users[1].name, which is "Bob".

3. Final Answer:

   "Bob" -> Option D

4. Quick Check:

   Index 1 in array = "Bob" [OK]

Hint: Remember arrays start at zero index [OK]

Common Mistakes:

• Confusing index 1 with index 0
• Assuming structs print as variable names
• Expecting compilation error due to string usage

4. Identify the error in this Solidity code snippet:

mapping(address => uint) balances;
function addBalance(address user, uint amount) public {
  balances[user] += amount;
}

medium

A. Cannot use '+=' on mapping values

B. Function lacks visibility modifier

C. No initialization needed for mapping values

D. Mapping keys must be uint, not address

Solution

1. Step 1: Check mapping usage

   Mappings default to zero for uint values if key not set, so no initialization needed.

2. Step 2: Verify function and operation

   Using '+=' on balances[user] is valid; function has public visibility.

3. Final Answer:

   No initialization needed for mapping values -> Option C

4. Quick Check:

   Mapping uint defaults to 0, so '+=' works [OK]

Hint: Mapping values default to zero, no init needed [OK]

Common Mistakes:

• Thinking mapping values must be initialized before use
• Confusing visibility modifiers
• Assuming keys must be uint instead of address

5. You want to store user profiles with id, name, and balance, and quickly find a profile by id. Which data structure combination is most efficient in Solidity?

hard

A. Mapping from id to struct

B. Array of structs only

C. Struct with embedded array

D. Linked list of structs

Solution

1. Step 1: Analyze the need for quick lookup by id

   Quick lookup by id requires direct access, which arrays or linked lists cannot provide efficiently.

2. Step 2: Choose the best data structure

   Mapping from id to struct allows O(1) access to user profiles by id, combining grouping (struct) and fast lookup (mapping).

3. Final Answer:

   Mapping from id to struct -> Option A

4. Quick Check:

   Fast key access + grouped data = mapping to struct [OK]

Hint: Use mapping from id to struct for fast profile lookup [OK]

Common Mistakes:

• Using arrays which require looping to find id
• Using linked lists which are slow for random access
• Embedding arrays inside structs without mapping