Why data location affects cost in Blockchain / Solidity - Performance Analysis

Time Complexity: Why data location affects cost

O(n)

Understanding Time Complexity

In blockchain, where data is stored can change how much work the system does.

We want to see how data location affects the cost of running code.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

contract Example {
    uint[] storageData;
    uint[] memoryData;

    function updateStorage() public {
        for (uint i = 0; i < storageData.length; i++) {
            storageData[i] = storageData[i] + 1;
        }
    }

    function updateMemory() public {
        uint[] memory temp = memoryData;
        for (uint i = 0; i < temp.length; i++) {
            temp[i] = temp[i] + 1;
        }
    }
}
    

This code updates numbers stored in two places: storage (permanent) and memory (temporary).

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each element in the array to update its value.
• How many times: Once for each element in the array (n times).

How Execution Grows With Input

As the array gets bigger, the loop runs more times, so the work grows with the number of items.

Input Size (n)	Approx. Operations
10	10 updates
100	100 updates
1000	1000 updates

Pattern observation: The work grows directly with the number of elements.

Final Time Complexity

Time Complexity: O(n)

This means the time to update grows in a straight line as the data size grows.

Common Mistake

[X] Wrong: "Updating data in memory costs the same as updating data in storage."

[OK] Correct: Storage updates are more expensive because they change permanent data on the blockchain, while memory updates are temporary and cheaper.

Interview Connect

Understanding how data location affects cost helps you write efficient blockchain code and shows you know how the system works behind the scenes.

Self-Check

"What if we copied storage data to memory before updating, then wrote back once? How would the time complexity change?"

Practice

1. Why does storing data directly on the blockchain usually cost more than storing it off-chain?

easy

A. Because off-chain data is always public and on-chain data is private

B. Because on-chain data uses shared network resources and requires consensus from all nodes

C. Because on-chain data is stored only temporarily

D. Because off-chain data is encrypted and on-chain data is not

Solution

1. Step 1: Understand blockchain data storage

   On-chain data is stored by all nodes in the network, requiring consensus and replication.

2. Step 2: Recognize resource usage impact

   This replication uses shared network resources, making on-chain storage more expensive than off-chain.

3. Final Answer:

   Because on-chain data uses shared network resources and requires consensus from all nodes -> Option B

4. Quick Check:

   On-chain storage costs more due to network resource use [OK]

Hint: On-chain means shared network storage, so it costs more [OK]

Common Mistakes:

• Thinking off-chain data is always public
• Assuming on-chain data is temporary
• Confusing encryption with cost

2. Which of the following is the correct way to describe storing data off-chain in a blockchain app?

easy

A. Storing data on the blockchain ledger directly

B. Storing data only in smart contract variables

C. Storing data in external databases or storage systems linked to the blockchain

D. Storing data by broadcasting it to all network nodes without consensus

Solution

1. Step 1: Define off-chain storage

   Off-chain means data is stored outside the blockchain, often in external databases or storage systems.

2. Step 2: Match options to definition

   Storing data in external databases or storage systems linked to the blockchain correctly describes off-chain storage as external linked storage, unlike on-chain ledger or smart contract variables.

3. Final Answer:

   Storing data in external databases or storage systems linked to the blockchain -> Option C

4. Quick Check:

   Off-chain = external storage linked to blockchain [OK]

Hint: Off-chain means outside blockchain, usually external databases [OK]

Common Mistakes:

• Confusing on-chain ledger with off-chain storage
• Thinking smart contract variables are off-chain
• Believing broadcasting without consensus is off-chain storage

3. Consider a blockchain app that stores user profiles. If storing 1 KB on-chain costs 0.01 ETH and storing off-chain costs 0.001 ETH, what is the cost difference for storing 100 KB on-chain vs off-chain?

medium

A. 0.9 ETH more for on-chain storage

B. 0.01 ETH more for on-chain storage

C. 1 ETH more for on-chain storage

D. No cost difference

Solution

1. Step 1: Calculate on-chain cost for 100 KB

   100 KB * 0.01 ETH/KB = 1 ETH total on-chain cost.

2. Step 2: Calculate off-chain cost for 100 KB

   100 KB * 0.001 ETH/KB = 0.1 ETH total off-chain cost.

3. Step 3: Find cost difference

   1 ETH - 0.1 ETH = 0.9 ETH more for on-chain.

4. Final Answer:

   0.9 ETH more for on-chain storage -> Option A

5. Quick Check:

   On-chain cost > off-chain cost by 0.9 ETH [OK]

Hint: Multiply size by cost per KB, compare totals [OK]

Common Mistakes:

• Multiplying incorrectly or mixing units
• Confusing which cost is higher
• Ignoring multiplication by 100 KB

4. A developer wrote this code snippet to store user data:

storeData(userData) {
  blockchain.save(userData);
  offchain.save(userData);
}

Why might this cause unnecessary cost?

medium

A. Because offchain.save() should be called before blockchain.save()

B. Because blockchain.save() is asynchronous and offchain.save() is synchronous

C. Because userData is not encrypted before saving

D. Because storing data both on-chain and off-chain duplicates storage cost unnecessarily

Solution

1. Step 1: Analyze storage calls

   The code stores the same data both on-chain and off-chain, duplicating storage.

2. Step 2: Understand cost impact

   On-chain storage is costly, so duplicating data on both increases unnecessary cost.

3. Final Answer:

   Because storing data both on-chain and off-chain duplicates storage cost unnecessarily -> Option D

4. Quick Check:

   Duplicate storage increases cost [OK]

Hint: Avoid storing same data twice on-chain and off-chain [OK]

Common Mistakes:

• Thinking async vs sync affects cost here
• Assuming encryption affects storage cost directly
• Believing call order changes cost

5. You want to design a blockchain app that stores transaction logs. To minimize cost, which approach is best?

hard

A. Store only transaction hashes on-chain and full logs off-chain

B. Store all transaction logs fully on-chain for transparency

C. Store all logs off-chain and never record anything on-chain

D. Store logs on-chain but compress them with lossy compression

Solution

1. Step 1: Consider cost and transparency

   Storing full logs on-chain is costly; storing nothing on-chain loses trust.

2. Step 2: Use hashes on-chain for verification

   Storing hashes on-chain keeps proof of logs without full data cost.

3. Step 3: Keep full logs off-chain for detail

   Full logs off-chain save cost but remain accessible and verifiable.

4. Final Answer:

   Store only transaction hashes on-chain and full logs off-chain -> Option A

5. Quick Check:

   Hashes on-chain + full off-chain = cost-effective and verifiable [OK]

Hint: Keep proofs on-chain, full data off-chain to save cost [OK]

Common Mistakes:

• Storing all data on-chain ignoring cost
• Storing nothing on-chain losing trust
• Using lossy compression risking data integrity