Proxy pattern (upgradeable contracts) in Blockchain / Solidity - Time & Space Complexity

Time Complexity: Proxy pattern (upgradeable contracts)

O(n)

Understanding Time Complexity

When using the proxy pattern in blockchain, we want to know how the cost of calling functions changes as the contract grows.

We ask: How does the number of steps grow when the proxy forwards calls to the logic contract?

Scenario Under Consideration

Analyze the time complexity of the following proxy contract code snippet.

contract Proxy {
  address implementation;

  fallback() external payable {
    (bool success, ) = implementation.delegatecall(msg.data);
    require(success);
  }
}

This code forwards any call to the current implementation contract using delegatecall.

Identify Repeating Operations

Look for repeated actions that affect time cost.

• Primary operation: The delegatecall forwards the call data to the implementation contract.
• How many times: Once per external call to the proxy.

How Execution Grows With Input

The proxy adds a small fixed overhead for forwarding calls, regardless of the size of the implementation contract.

Input Size (n)	Approx. Operations
10	~10 + small fixed overhead
100	~100 + small fixed overhead
1000	~1000 + small fixed overhead

Pattern observation: The cost grows roughly in direct proportion to the size of the called function's work, with a small constant added by the proxy.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete a call grows linearly with the work done in the implementation contract, plus a small fixed cost from the proxy.

Common Mistake

[X] Wrong: "The proxy adds a big extra cost that grows with the implementation contract size."

[OK] Correct: The proxy only forwards calls once per call, so its overhead is constant, not growing with the implementation contract size.

Interview Connect

Understanding how proxy contracts affect execution cost helps you explain upgradeable contract design clearly and confidently.

Self-Check

"What if the proxy added multiple delegatecalls in a single fallback? How would the time complexity change?"

Practice

1.

What is the main purpose of using the Proxy pattern in smart contracts?

easy

A. To upgrade contract logic without changing the contract address

B. To reduce gas fees by optimizing code

C. To create multiple copies of the same contract

D. To prevent any changes to the contract after deployment

Solution

1. Step 1: Understand the Proxy pattern role

   The Proxy pattern allows a contract to forward calls to another contract, enabling upgrades.

2. Step 2: Identify the main benefit

   This forwarding lets you change the logic contract without changing the proxy's address.

3. Final Answer:

   To upgrade contract logic without changing the contract address -> Option A

4. Quick Check:

   Proxy pattern = Upgrade logic without address change [OK]

Hint: Proxy pattern upgrades logic, keeps address same [OK]

Common Mistakes:

• Thinking proxy reduces gas fees
• Believing proxy creates contract copies
• Assuming proxy prevents all changes

2.

Which Solidity keyword is used inside a proxy contract to forward calls to the implementation contract?

easy

A. delegatecall

B. call

C. transfer

D. send

Solution

1. Step 1: Recall Solidity call types

   Solidity has several low-level calls: call, delegatecall, send, transfer.

2. Step 2: Identify forwarding call for proxy

   Proxy contracts use delegatecall to run implementation code in proxy's context.

3. Final Answer:

   delegatecall -> Option A

4. Quick Check:

   Proxy forwarding uses delegatecall [OK]

Hint: Proxy uses delegatecall to keep storage context [OK]

Common Mistakes:

• Confusing call with delegatecall
• Using transfer or send which are for Ether
• Not knowing delegatecall preserves storage

3.

Consider this simplified proxy contract snippet in Solidity:

contract Proxy {
    address implementation;
    
    fallback() external payable {
        (bool success, ) = implementation.delegatecall(msg.data);
        require(success);
    }
}

What happens if implementation address is zero?

medium

A. The contract will self-destruct

B. The call will succeed but do nothing

C. The fallback function will be ignored

D. The call will fail and revert the transaction

Solution

1. Step 1: Understand delegatecall to zero address

   Calling delegatecall on address zero means no code to execute.

2. Step 2: Effect of delegatecall failure

   delegatecall returns false on failure; require(success) then reverts transaction.

3. Final Answer:

   The call will fail and revert the transaction -> Option D

4. Quick Check:

   delegatecall to zero address = revert [OK]

Hint: delegatecall to zero address always fails [OK]

Common Mistakes:

• Assuming call succeeds silently
• Thinking fallback is skipped
• Believing contract self-destructs

4.

Identify the bug in this proxy upgrade function:

function upgradeTo(address newImplementation) public {
    implementation = newImplementation;
}

What is the main issue?

medium

A. Implementation address is not validated

B. Missing event emission after upgrade

C. No access control, anyone can upgrade implementation

D. Function should be external, not public

Solution

1. Step 1: Check function access control

   The function is public, so anyone can call it and change implementation.

2. Step 2: Understand security risk

   Without restricting access, attackers can hijack the contract logic.

3. Final Answer:

   No access control, anyone can upgrade implementation -> Option C

4. Quick Check:

   Upgrade function needs access control [OK]

Hint: Always restrict upgrade function access [OK]

Common Mistakes:

• Ignoring access control importance
• Focusing only on event emission
• Thinking public vs external affects security

5.

You want to upgrade a proxy contract to a new implementation that adds a new state variable. What must you ensure to avoid breaking storage layout?

hard

A. Rearrange all variables in the new implementation for optimization

B. Add new variables only at the end of existing storage variables

C. Remove unused variables from the old implementation

D. Change variable types to reduce storage size

Solution

1. Step 1: Understand storage layout importance

   Proxy pattern requires storage layout consistency between implementations.

2. Step 2: Correct way to add variables

   New variables must be appended to avoid overwriting existing storage slots.

3. Final Answer:

   Add new variables only at the end of existing storage variables -> Option B

4. Quick Check:

   Storage layout consistency = append variables [OK]

Hint: Append new variables to preserve storage layout [OK]

Common Mistakes:

• Rearranging variables breaks storage
• Removing old variables causes data loss
• Changing types shifts storage slots