Proxy pattern (upgradeable contracts) in Blockchain / Solidity

Introduction

The proxy pattern helps you upgrade smart contracts without losing data or changing the contract address. It separates logic from data, so you can fix bugs or add features easily.

You want to fix bugs in a deployed smart contract without losing user data.

You want to add new features to a contract without forcing users to switch to a new address.

You want to save gas by reusing logic contracts for multiple proxies.

You want to keep a stable contract address for integrations while upgrading logic behind it.

Syntax

Blockchain / Solidity

contract Proxy {
    address implementation;

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

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

The fallback function forwards calls to the logic contract using delegatecall.

The upgradeTo function changes the logic contract address to upgrade functionality.

Examples

Basic proxy contract that forwards calls to an implementation contract and allows upgrading it.

Blockchain / Solidity

contract Proxy {
    address implementation;

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

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

First version of logic contract with a simple state variable and setter.

Blockchain / Solidity

contract LogicV1 {
    uint public x;

    function setX(uint _x) public {
        x = _x;
    }
}

Second version of logic contract that changes behavior by doubling the input.

Blockchain / Solidity

contract LogicV2 {
    uint public x;

    function setX(uint _x) public {
        x = _x * 2;
    }
}

Sample Program

This example shows a proxy contract that forwards calls to a logic contract using delegatecall. The owner can upgrade the logic contract address. LogicV1 sets a value directly, LogicV2 doubles the value before setting it.

Blockchain / Solidity

pragma solidity ^0.8.0;

contract Proxy {
    address public implementation;
    address public owner;

    constructor(address _implementation) {
        implementation = _implementation;
        owner = msg.sender;
    }

    fallback() external payable {
        address impl = implementation;
        assembly {
            calldatacopy(0, 0, calldatasize())
            let result := delegatecall(gas(), impl, 0, calldatasize(), 0, 0)
            let size := returndatasize()
            returndatacopy(0, 0, size)
            switch result
            case 0 { revert(0, size) }
            default { return(0, size) }
        }
    }

    function upgradeTo(address newImplementation) external {
        require(msg.sender == owner, "Only owner can upgrade");
        implementation = newImplementation;
    }
}

contract LogicV1 {
    uint public x;

    function setX(uint _x) public {
        x = _x;
    }
}

contract LogicV2 {
    uint public x;

    function setX(uint _x) public {
        x = _x * 2;
    }
}

Important Notes

Storage layout must be the same between logic versions to avoid corrupting data.

Only the proxy holds the data; logic contracts are stateless.

Use access control on upgrade functions to prevent unauthorized upgrades.

Summary

The proxy pattern separates data and logic to allow contract upgrades.

Calls to the proxy are forwarded to the current logic contract using delegatecall.

Upgrading means changing the logic contract address without changing the proxy address.

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