Factory pattern in Blockchain / Solidity - Time & Space Complexity

Time Complexity: Factory pattern

O(n)

Understanding Time Complexity

When using the factory pattern in blockchain code, it's important to know how the time needed to create objects grows as we create more of them.

We want to understand how the cost changes when making many objects through the factory.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

contract TokenFactory {
    Token[] public tokens;

    function createToken(string memory name) public {
        Token newToken = new Token(name);
        tokens.push(newToken);
    }
}

contract Token {
    string public name;
    constructor(string memory _name) {
        name = _name;
    }
}
    

This code creates new Token contracts using a factory contract and stores them in an array.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Creating a new Token contract and adding it to the tokens array.
• How many times: Once per call to createToken, repeated as many times as tokens are created.

How Execution Grows With Input

Each time we create a token, the factory does a fixed amount of work: deploy one Token and add it to the array.

Input Size (n)	Approx. Operations
10	10 token creations and 10 array insertions
100	100 token creations and 100 array insertions
1000	1000 token creations and 1000 array insertions

Pattern observation: The work grows directly with the number of tokens created, increasing steadily.

Final Time Complexity

Time Complexity: O(n)

This means the time to create tokens grows linearly with how many tokens you make.

Common Mistake

[X] Wrong: "Creating many tokens at once is just as fast as creating one token."

[OK] Correct: Each token creation requires deploying a new contract and updating the array, so the total time adds up with each new token.

Interview Connect

Understanding how factory patterns scale helps you explain how smart contract deployments affect blockchain performance and costs.

Self-Check

"What if the factory stored tokens in a mapping instead of an array? How would the time complexity change?"

Practice

1.

What is the main purpose of the Factory pattern in blockchain development?

easy

A. To create multiple similar contracts easily and manage their addresses

B. To encrypt data on the blockchain

C. To mine new blocks faster

D. To validate transactions off-chain

Solution

1. Step 1: Understand the Factory pattern role

   The Factory pattern is used to create many similar contracts efficiently.

2. Step 2: Identify its key feature

   It also stores the addresses of these created contracts for easy access later.

3. Final Answer:

   To create multiple similar contracts easily and manage their addresses -> Option A

4. Quick Check:

   Factory pattern = create and manage contracts [OK]

Hint: Factory pattern creates and tracks contracts easily [OK]

Common Mistakes:

• Confusing factory with encryption or mining
• Thinking factory validates transactions
• Assuming factory works off-chain

2.

Which of the following is the correct Solidity syntax to deploy a new contract inside a factory contract?

function create() public returns (address) {
    address newContract = new ?();
    return newContract;
}

easy

A. ContractName

B. contractname

C. new ContractName()

D. ContractName()

Solution

1. Step 1: Recall Solidity contract creation syntax

   To create a new contract instance, use new ContractName().

2. Step 2: Match syntax with code snippet

   The placeholder new ?() expects the contract name without 'new' repeated.

3. Final Answer:

   ContractName -> Option A

4. Quick Check:

   Use 'new ContractName()' but only 'ContractName' inside parentheses [OK]

Hint: Use contract name only inside new keyword parentheses [OK]

Common Mistakes:

• Writing 'new' twice
• Using lowercase contract names
• Omitting parentheses

3.

Consider this Solidity factory contract snippet:

contract Simple {
    uint public value;
    constructor(uint _value) {
        value = _value;
    }
}

contract Factory {
    Simple[] public simples;
    function createSimple(uint _val) public {
        Simple s = new Simple(_val);
        simples.push(s);
    }
    function getValue(uint index) public view returns (uint) {
        return simples[index].value();
    }
}

What will getValue(0) return after calling createSimple(42) once?

medium

A. Address of the contract

B. 0

C. 42

D. Compilation error

Solution

1. Step 1: Understand contract creation and storage

   Calling createSimple(42) creates a new Simple contract with value = 42 and stores it in simples array.

2. Step 2: Check what getValue(0) returns

   It returns the value of the first Simple contract, which is 42.

3. Final Answer:

   42 -> Option C

4. Quick Check:

   Created contract value = 42 [OK]

Hint: Created contract stores value; getValue returns it [OK]

Common Mistakes:

• Confusing contract address with stored value
• Assuming default zero value
• Thinking it returns array length

4.

Identify the error in this factory contract code snippet:

contract Product {
    uint public id;
    constructor(uint _id) {
        id = _id;
    }
}

contract ProductFactory {
    Product[] public products;
    function createProduct(uint _id) public {
        Product p = Product(_id);
        products.push(p);
    }
}

medium

A. Array products should be a mapping

B. Missing new keyword when creating Product

C. Constructor should not have parameters

D. Function createProduct must be view

Solution

1. Step 1: Check contract instantiation syntax

   In Solidity, to create a new contract instance, you must use the new keyword.

2. Step 2: Identify the missing keyword

   The line Product p = Product(_id); misses new, it should be Product p = new Product(_id);.

3. Final Answer:

   Missing new keyword when creating Product -> Option B

4. Quick Check:

   Contract creation requires 'new' keyword [OK]

Hint: Always use 'new' to create contracts in Solidity [OK]

Common Mistakes:

• Forgetting 'new' keyword
• Changing array to mapping unnecessarily
• Marking create function as view incorrectly

5.

You want to build a factory contract that creates multiple token contracts with different initial supplies and keeps track of them. Which approach best applies the factory pattern to save gas and organize your project?

hard

A. Use a single token contract and change its supply dynamically for each user

B. Deploy all token contracts manually and hardcode their addresses in the factory

C. Create token contracts but do not store their addresses anywhere

D. Create each token contract separately and store their addresses in an array inside the factory

Solution

1. Step 1: Understand factory pattern benefits

   The factory pattern helps create many similar contracts and keeps track of them efficiently.

2. Step 2: Evaluate options for managing multiple tokens

   Creating each token contract inside the factory and storing their addresses allows easy management and gas savings.

3. Step 3: Reject other options

   Hardcoding addresses is inflexible, using one contract for all tokens breaks isolation, and not storing addresses loses track.

4. Final Answer:

   Create each token contract separately and store their addresses in an array inside the factory -> Option D

5. Quick Check:

   Factory creates and tracks contracts for organization [OK]

Hint: Factory creates and stores contracts for easy management [OK]

Common Mistakes:

• Hardcoding addresses reduces flexibility
• Using one contract for all tokens causes conflicts
• Not storing addresses loses track of contracts