Upgrade strategies in Blockchain / Solidity - Step-by-Step Execution

Concept Flow - Upgrade strategies

Identify Need for Upgrade

↓

Choose Upgrade Strategy

↓

Hard Fork

↓

Implement New Rules

↓

Network Consensus

↓

Upgrade Complete

Shows the decision and implementation flow of blockchain upgrade strategies: hard fork, soft fork, and proxy/delegate methods.

Execution Sample

Blockchain / Solidity

def upgrade_strategy(current_version, target_version):
    if target_version > current_version:
        return "Hard Fork"
    elif target_version == current_version:
        return "Soft Fork"
    else:
        return "No Upgrade Needed"

Simple function deciding upgrade type based on version comparison.

Execution Table

Step	current_version	target_version	Condition	Branch Taken	Output
1	1	2	2 > 1	True	"Hard Fork"
2	2	2	2 > 2	False	Check next condition
3	2	2	2 == 2	True	"Soft Fork"
4	3	2	2 > 3	False	Check next condition
5	3	2	2 == 3	False	Return "No Upgrade Needed"

💡 Function returns upgrade type based on version comparison.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
current_version	varies	1	2	2	3	3
target_version	varies	2	2	2	2	2
Output	None	"Hard Fork"	None	"Soft Fork"	None	"No Upgrade Needed"

Key Moments - 2 Insights

Why does the function return 'Soft Fork' when current_version equals target_version?

Because in the execution_table at Step 3, the condition 'target_version == current_version' is True, so the function returns 'Soft Fork' indicating a backward-compatible upgrade.

What happens if target_version is less than current_version?

As shown in Steps 4 and 5, both conditions fail, so the function returns 'No Upgrade Needed', meaning no upgrade is performed.

Visual Quiz - 3 Questions

Look at the execution_table, what output does the function produce when current_version is 1 and target_version is 2?

A "Soft Fork"

B "Hard Fork"

C "No Upgrade Needed"

D Error

💡 Hint

Check Step 1 in the execution_table where current_version=1 and target_version=2.

At which step does the function decide to return 'No Upgrade Needed'?

A Step 5

B Step 3

C Step 1

D Step 2

💡 Hint

Look at the last row in the execution_table where both conditions fail.

If target_version is increased beyond current_version, how does the output change?

A Output changes to 'Soft Fork'

B Output remains 'No Upgrade Needed'

C Output changes to 'Hard Fork'

D Output is undefined

💡 Hint

Refer to Step 1 where target_version > current_version returns 'Hard Fork'.

Concept Snapshot

Upgrade strategies in blockchain:
- Hard Fork: new rules, incompatible, requires all nodes to upgrade.
- Soft Fork: backward compatible, old nodes accept new rules.
- Proxy/Delegate: redirect calls to new logic without changing consensus.
Choose strategy based on version comparison and network consensus.

Full Transcript

This visual execution trace shows how blockchain upgrade strategies work by comparing current and target versions. The function upgrade_strategy returns 'Hard Fork' if the target version is higher, indicating a major incompatible upgrade. It returns 'Soft Fork' if versions are equal, meaning a backward-compatible upgrade. If the target version is lower, it returns 'No Upgrade Needed'. The execution table walks through these conditions step-by-step, showing variable values and decisions. Key moments clarify why certain branches are taken. The quiz tests understanding by referencing specific steps and outputs. This helps beginners see how upgrade decisions happen in code.

Practice

1. Which of the following is a common upgrade strategy in blockchain development?

easy

A. Changing the blockchain consensus algorithm without notifying nodes

B. Using proxy contracts to allow logic changes without changing the contract address

C. Deleting old blocks to save space

D. Ignoring backward compatibility during upgrades

Solution

1. Step 1: Understand upgrade strategies

   Common upgrade strategies include proxy contracts, hard forks, and soft forks.

2. Step 2: Identify the correct method

   Proxy contracts allow changing logic while keeping the same address, enabling safe upgrades.

3. Final Answer:

   Using proxy contracts to allow logic changes without changing the contract address -> Option B

4. Quick Check:

   Proxy contracts = safe upgrade method [OK]

Hint: Proxy contracts keep address same for upgrades [OK]

Common Mistakes:

• Confusing hard forks with proxy contracts
• Thinking deleting blocks is an upgrade
• Ignoring backward compatibility

2. Which syntax correctly declares a proxy contract upgrade function in Solidity?

easy

A. function upgradeTo(address newImplementation) external onlyOwner {}

B. upgradeTo(address newImplementation) public {}

C. function upgrade(address newImplementation) private {}

D. function upgradeTo() external {}

Solution

1. Step 1: Check function declaration syntax

   In Solidity, functions must start with 'function' keyword and specify visibility.

2. Step 2: Match upgrade function signature

   The upgrade function usually takes an address and is external with access control like 'onlyOwner'.

3. Final Answer:

   function upgradeTo(address newImplementation) external onlyOwner {} -> Option A

4. Quick Check:

   Correct Solidity function syntax = function upgradeTo(address newImplementation) external onlyOwner {} [OK]

Hint: Solidity functions need 'function' and visibility keywords [OK]

Common Mistakes:

• Omitting 'function' keyword
• Using wrong visibility like private for upgrade
• Missing function parameters

3. Given this Solidity proxy upgrade snippet, what will be the output of implementation() after calling upgradeTo(newAddress)?

contract Proxy {
  address private _implementation;
  function implementation() public view returns (address) {
    return _implementation;
  }
  function upgradeTo(address newImplementation) public {
    _implementation = newImplementation;
  }
}

medium

A. Compilation error due to missing visibility

B. Always zero address (0x0)

C. The address of the Proxy contract itself

D. The address stored in _implementation after upgradeTo is called

Solution

1. Step 1: Understand state variable update

   The function upgradeTo sets _implementation to newImplementation address.

2. Step 2: Check implementation() return value

   implementation() returns the current _implementation address, which changes after upgradeTo call.

3. Final Answer:

   The address stored in _implementation after upgradeTo is called -> Option D

4. Quick Check:

   State variable updated = returned address [OK]

Hint: State variable returns updated address after upgrade [OK]

Common Mistakes:

• Assuming implementation() returns Proxy address
• Thinking _implementation stays zero
• Confusing visibility keywords

4. Identify the bug in this upgrade function and how to fix it:

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

medium

A. Incorrect parameter type; should be uint256 instead of address

B. Function should be private to prevent external calls

C. Missing access control; add 'onlyOwner' modifier to restrict upgrades

D. No bug; function is correct as is

Solution

1. Step 1: Analyze function security

   The function allows anyone to call upgradeTo and change implementation, which is unsafe.

2. Step 2: Add access control

   Adding 'onlyOwner' modifier restricts upgrades to contract owner, preventing unauthorized changes.

3. Final Answer:

   Missing access control; add 'onlyOwner' modifier to restrict upgrades -> Option C

4. Quick Check:

   Access control needed for upgrade functions [OK]

Hint: Always restrict upgrade functions with access control [OK]

Common Mistakes:

• Ignoring security risks of public upgrade functions
• Changing parameter type incorrectly
• Making function private disables upgrades

5. You want to upgrade a deployed smart contract without changing its address or losing stored data. Which upgrade strategy should you use and why?

hard

A. Use a proxy contract pattern to separate logic and data storage

B. Perform a hard fork to replace the entire blockchain state

C. Deploy a new contract and ask users to switch manually

D. Delete the old contract and deploy a new one at the same address

Solution

1. Step 1: Understand upgrade goals

   We want to keep the same contract address and preserve stored data during upgrade.

2. Step 2: Evaluate upgrade strategies

   Proxy contracts separate logic and data, allowing logic upgrades without changing address or data loss.

3. Step 3: Compare other options

   Hard forks replace blockchain state, deploying new contracts requires user action, deleting contracts is impossible on blockchain.

4. Final Answer:

   Use a proxy contract pattern to separate logic and data storage -> Option A

5. Quick Check:

   Proxy pattern = upgrade without address or data loss [OK]

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

Common Mistakes:

• Thinking hard forks preserve contract address
• Assuming users will always switch to new contract
• Trying to delete deployed contracts