Gas optimization with storage in Blockchain / Solidity - Deep Dive

Overview - Gas optimization with storage

What is it?

Gas optimization with storage means making smart choices to reduce the cost of saving and accessing data on a blockchain. Storage operations are expensive because they use a lot of blockchain resources. By optimizing how and when data is stored, developers can save money and make their smart contracts more efficient. This helps blockchain applications run faster and cheaper.

Why it matters

Without gas optimization, blockchain transactions become costly and slow, discouraging users and developers. High storage costs can make decentralized apps too expensive to use or maintain. Optimizing storage reduces fees, making blockchain technology more accessible and practical for everyday use. It also helps networks stay scalable and sustainable as more people use them.

Where it fits

Before learning gas optimization with storage, you should understand basic blockchain concepts, smart contracts, and how gas fees work. After this, you can explore advanced optimization techniques, security best practices, and layer-2 scaling solutions. This topic is a key step in writing efficient and cost-effective smart contracts.

Mental Model

Core Idea

Saving and changing data on a blockchain costs gas, so using storage wisely and minimizing writes saves money and improves performance.

Think of it like...

Imagine a notebook where every time you write or erase a word, you pay a fee. Writing less or using shorthand saves money, just like optimizing storage saves gas on the blockchain.

┌───────────────┐
│   Smart       │
│   Contract    │
└──────┬────────┘
       │
       ▼
┌───────────────┐
│ Storage Layer │
│ (Expensive)   │
└──────┬────────┘
       │
       ▼
┌───────────────┐
│ Gas Cost      │
│ (Based on     │
│ Storage Usage)│
└───────────────┘

Build-Up - 8 Steps

1

Foundation

Understanding Blockchain Storage Costs

Concept: Storage operations on blockchain consume gas and are more expensive than simple calculations.

On blockchains like Ethereum, storing data permanently costs gas because it uses network resources. Writing new data (storing) costs more gas than reading data. Deleting data can refund some gas but still costs operations. Knowing this helps you plan how to handle data efficiently.

Result

You learn that storage is the main driver of gas costs in smart contracts.

Understanding that storage is expensive is the foundation for all gas optimization strategies.

2

Foundation

Difference Between Memory, Stack, and Storage

Concept: Smart contracts use different places to hold data, each with different gas costs.

Memory is temporary and cheaper but lost after function ends. Stack holds small data during execution. Storage is permanent and costly. Use memory for temporary data and storage only for data that must persist between transactions.

Result

You can decide where to put data to save gas.

Knowing the cost difference between memory and storage guides efficient data handling.

3

Intermediate

Minimizing Storage Writes

🤔Before reading on: do you think updating storage multiple times costs the same as updating once? Commit to your answer.

Concept: Each write to storage costs gas, so reducing the number of writes saves gas.

Instead of updating a storage variable multiple times in a function, calculate the final value first, then write once. For example, accumulate changes in memory variables and write the result to storage at the end.

Result

Fewer storage writes reduce gas consumption significantly.

Knowing that each storage write costs gas motivates batching updates to save money.

4

Intermediate

Packing Variables to Save Space

🤔Before reading on: do you think storing multiple small variables separately costs more gas than storing them packed together? Commit to your answer.

Concept: Combining multiple small variables into one storage slot reduces gas costs.

Storage slots are 32 bytes. If you store several small variables (like booleans or uint8) separately, each uses a full slot. Packing them into one slot saves space and gas. Solidity automatically packs variables declared consecutively if their types fit.

Result

Packed variables use less storage and cost less gas.

Understanding storage slot size helps you organize variables to minimize gas.

5

Intermediate

Using Immutable and Constant Variables

Concept: Immutable and constant variables reduce storage gas costs by storing data differently.

Constants are fixed at compile time and stored in bytecode, costing no storage gas. Immutable variables are set once during contract creation and stored efficiently. Using these reduces gas compared to regular storage variables.

Result

Gas costs drop when using constants and immutables for fixed data.

Knowing when to use constants or immutables avoids unnecessary storage gas.

6

Advanced

Deleting Storage to Get Gas Refunds

🤔Before reading on: do you think deleting storage variables always saves gas or sometimes costs more? Commit to your answer.

Concept: Clearing storage variables refunds some gas, lowering overall transaction cost.

When you set a storage slot from non-zero to zero, the blockchain refunds gas. This encourages cleaning up unused data. However, refunds have limits and only apply if you delete after writing. Use this to optimize contracts that update or remove data.

Result

Proper deletion can reduce net gas cost of transactions.

Knowing gas refunds helps design contracts that manage storage lifecycle efficiently.

7

Advanced

Using External Storage Contracts

Concept: Separating storage into dedicated contracts can optimize gas and upgradeability.

Instead of storing all data in one contract, use a separate storage contract accessed via calls. This can reduce gas by reusing storage logic and enable upgrades without losing data. It also helps organize data access patterns for efficiency.

Result

More flexible and potentially cheaper storage management.

Understanding modular storage design unlocks advanced optimization and upgrade patterns.

8

Expert

Storage Layout and Slot Collision Risks

🤔Before reading on: do you think changing contract code always keeps storage safe? Commit to your answer.

Concept: Storage layout must be carefully managed to avoid overwriting data when upgrading contracts.

In upgradeable contracts, storage slots must remain consistent. Changing variable order or types can cause slot collisions, corrupting data. Experts use fixed slot assignments or storage gaps to prevent this. Tools like storage layout analyzers help detect risks.

Result

Avoiding storage collisions prevents costly bugs and data loss.

Knowing storage layout internals is critical for safe contract upgrades and long-term optimization.

Under the Hood

Blockchain storage is a key-value store where each key is a 32-byte slot. Writing to a slot changes the blockchain state and costs gas proportional to the operation. Reading is cheaper but still costs gas. The Ethereum Virtual Machine manages storage with a Merkle Patricia Trie, ensuring data integrity and consensus. Gas costs reflect the computational and storage resources used by nodes to maintain the blockchain.

Why designed this way?

Storage is expensive because it must be replicated and stored by every node forever, ensuring decentralization and security. The gas cost model discourages wasteful storage to keep the network scalable. Alternatives like off-chain storage exist but sacrifice decentralization. The design balances usability with resource limits.

┌───────────────┐
│ Smart Contract│
│  Storage Map  │
│  (Key → Value)│
└──────┬────────┘
       │
       ▼
┌───────────────┐
│ EVM Storage   │
│  Slots (32B)  │
└──────┬────────┘
       │
       ▼
┌───────────────┐
│ Merkle Trie   │
│  State Root   │
└───────────────┘

Myth Busters - 4 Common Misconceptions

Quick: Does reading storage cost more gas than writing? Commit to yes or no before reading on.

Common Belief: Reading storage costs the same or more gas than writing.

Reality: Reading storage costs less gas than writing because it doesn't change blockchain state.

Why it matters: Misunderstanding this leads to unnecessary optimization of reads and ignoring costly writes.

Quick: Do you think deleting storage always refunds all gas spent on writing? Commit to yes or no.

Common Belief: Deleting storage always refunds all gas spent on storing data.

Reality: Gas refunds are partial and capped per transaction; deleting doesn't fully recover all gas spent.

Why it matters: Overestimating refunds can cause unexpected high gas costs and failed transactions.

Quick: Can you reorder storage variables freely in upgradeable contracts without issues? Commit to yes or no.

Common Belief: You can reorder or add storage variables anywhere in upgradeable contracts safely.

Reality: Changing storage layout can cause slot collisions and corrupt data in upgradeable contracts.

Why it matters: Ignoring this causes critical bugs and loss of contract state after upgrades.

Quick: Is using memory instead of storage always cheaper? Commit to yes or no.

Common Belief: Using memory instead of storage always saves gas regardless of data size or usage.

Reality: Memory is cheaper for temporary data but copying large data to memory can be costly; sometimes storage is better.

Why it matters: Blindly using memory can increase gas costs and reduce contract efficiency.

Expert Zone

1

Storage slot packing depends on variable declaration order and types; subtle changes can affect gas costs significantly.

2

Gas refunds for storage clearing are capped at half the total gas used, limiting refund strategies in large transactions.

3

Using assembly code can optimize storage access patterns beyond Solidity's automatic handling but requires deep expertise.

When NOT to use

Gas optimization with storage is less effective for contracts with minimal storage needs or when using layer-2 solutions that have different cost models. In some cases, off-chain storage or state channels are better alternatives to reduce on-chain storage costs.

Production Patterns

In production, developers use patterns like proxy contracts with fixed storage layouts, storage libraries for reusable data structures, and event logs to minimize on-chain storage. They also batch writes and use constants/immutables extensively to reduce gas.

Connections

Database Indexing

Both optimize data access costs by organizing storage efficiently.

Understanding how databases index data helps grasp why packing and layout matter for blockchain storage gas costs.

Memory Management in Operating Systems

Both manage limited fast-access storage versus slower permanent storage with cost tradeoffs.

Knowing OS memory hierarchy clarifies why blockchain distinguishes between memory and storage with different gas costs.

Environmental Resource Management

Both involve paying a cost to use limited resources to encourage efficient usage.

Seeing gas as a resource cost like water or electricity helps understand why optimization is critical for sustainability.

Common Pitfalls

#1 Updating storage variables multiple times in one function.

Wrong approach:

function update() public {
data = data + 1;
data = data + 2;
data = data + 3;
}

Correct approach:

function update() public {
uint temp = data;
temp = temp + 1 + 2 + 3;
data = temp;
}

Root cause:

Not realizing each storage write costs gas, so multiple writes increase cost unnecessarily.

#2 Declaring many small variables separately causing wasted storage slots.

Wrong approach:

bool a;
bool b;
bool c;
uint8 d;

Correct approach:

struct Packed {
bool a;
bool b;
bool c;
uint8 d;
}
Packed data;

Root cause:

Ignoring how Solidity packs variables into 32-byte slots, leading to inefficient storage.

#3 Changing storage variable order in upgradeable contracts.

Wrong approach:

contract V2 {
uint b;
uint a;
}

Correct approach:

contract V2 {
uint a;
uint b;
}

Root cause:

Not understanding that storage slot order must remain consistent to avoid data corruption.

Key Takeaways

Storage operations on blockchain are the most expensive gas consumers, so minimizing writes is crucial.

Using memory for temporary data and packing variables efficiently reduces gas costs significantly.

Constants and immutables help avoid storage gas costs for fixed data.

Deleting storage can refund gas but refunds are limited and must be used carefully.

Careful storage layout management is essential for safe upgrades and long-term contract health.