Memory allocation in Blockchain / Solidity - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is memory allocation in blockchain programming?

Memory allocation is the process of reserving space in a blockchain's storage or memory to store data during smart contract execution.

beginner

Why is efficient memory allocation important in blockchain smart contracts?

Efficient memory allocation reduces gas costs and prevents out-of-gas errors, making smart contracts cheaper and more reliable.

intermediate

What are the two main types of memory in Ethereum smart contracts?

The two main types are memory (temporary, erased between calls) and storage (persistent, stored on blockchain).

intermediate

How does dynamic memory allocation differ from static memory allocation in smart contracts?

Static allocation reserves fixed size memory at compile time, while dynamic allocation reserves memory during execution based on needs.

beginner

What happens if a smart contract runs out of allocated memory during execution?

The contract execution fails, and all changes are reverted. This wastes gas and can cause transaction failure.

Which type of memory in Ethereum smart contracts is persistent across function calls?

A Memory

B Stack

C Storage

D Cache

Storage is persistent and saved on the blockchain, while memory is temporary and cleared after function execution.

What is a consequence of inefficient memory allocation in blockchain smart contracts?

A Faster execution

B Higher gas costs

C More storage space

D Automatic optimization

Inefficient memory allocation uses more gas, making contract execution more expensive.

Dynamic memory allocation in smart contracts happens:

A During contract execution

B During contract deployment only

C At compile time

D Never

Dynamic allocation happens during execution when the contract needs variable-sized memory.

If a smart contract runs out of memory during execution, what happens?

A Execution continues normally

B Contract is deleted

C Memory is automatically increased

D Execution fails and reverts

Running out of memory causes execution failure and reverts all changes.

Which memory type is erased after each function call in Ethereum smart contracts?

A Memory

B Disk

C Storage

D Cache

Memory is temporary and erased after each function call, unlike storage.

Explain the difference between memory and storage in blockchain smart contracts.

Think about what happens to data after a function finishes.

Describe why managing memory allocation efficiently is important in blockchain programming.

Consider the cost and reliability of running smart contracts.

Practice

1. What is the main purpose of memory in blockchain smart contracts?

easy

A. To temporarily store data during function execution

B. To permanently save user data on the blockchain

C. To allocate gas for contract deployment

D. To encrypt data before storing

Solution

1. Step 1: Understand memory role in smart contracts

   Memory is used to hold data temporarily while a function runs.

2. Step 2: Differentiate memory from storage

   Storage saves data permanently on the blockchain, memory does not.

3. Final Answer:

   To temporarily store data during function execution -> Option A

4. Quick Check:

   Memory = Temporary data space [OK]

Hint: Memory is temporary, storage is permanent [OK]

Common Mistakes:

• Confusing memory with storage
• Thinking memory saves data permanently
• Assuming memory costs more gas

2. Which of the following is the correct syntax to declare a dynamic array in memory in Solidity?

easy

A. uint[] myArray = memory new uint[](5);

B. uint[] storage myArray = new uint[](5);

C. memory uint[] myArray = new uint[](5);

D. uint[] memory myArray = new uint[](5);

Solution

1. Step 1: Recall correct memory array declaration syntax

   In Solidity, dynamic memory arrays are declared as type[] memory var = new type[](size);

2. Step 2: Check each option

   uint[] memory myArray = new uint[](5); matches the correct syntax exactly.

3. Final Answer:

   uint[] memory myArray = new uint[](5); -> Option D

4. Quick Check:

   Memory array syntax = uint[] memory myArray = new uint[](5); [OK]

Hint: Use 'memory' keyword before variable name for memory arrays [OK]

Common Mistakes:

• Using 'storage' instead of 'memory' for temporary arrays
• Placing 'memory' after variable name incorrectly
• Omitting 'new' keyword for dynamic arrays

3. What will be the output of this Solidity function snippet?

function test() public pure returns (uint) {
    uint[] memory arr = new uint[](3);
    arr[0] = 10;
    arr[1] = 20;
    arr[2] = 30;
    return arr[1];
}

medium

A. 10

B. 20

C. 30

D. 0

Solution

1. Step 1: Analyze array assignments

   Array elements are set as arr[0]=10, arr[1]=20, arr[2]=30.

2. Step 2: Identify returned value

   The function returns arr[1], which is 20.

3. Final Answer:

   20 -> Option B

4. Quick Check:

   arr[1] = 20 [OK]

Hint: Remember array indexing starts at 0 [OK]

Common Mistakes:

• Confusing index 1 with index 0
• Assuming default zero value is returned
• Misreading array initialization

4. Identify the error in this Solidity function that tries to copy a storage array to memory:

uint[] public data;

function copyArray() public {
    uint[] memory temp = data;
}

medium

A. Cannot assign storage array directly to memory array

B. Missing visibility keyword for storage array

C. Memory arrays cannot be declared inside functions

D. Function must be marked as pure

Solution

1. Step 1: Understand storage to memory assignment rules

   Direct assignment from storage array to memory array is not allowed in Solidity.

2. Step 2: Identify correct error

   The code tries to assign data (storage) directly to temp (memory), causing a compilation error.

3. Final Answer:

   Cannot assign storage array directly to memory array -> Option A

4. Quick Check:

   Storage to memory direct assignment = Error [OK]

Hint: Copy elements manually from storage to memory [OK]

Common Mistakes:

• Assuming direct assignment copies array
• Ignoring visibility requirements
• Marking function pure incorrectly

5. You want to create a function that returns a new memory array containing only the even numbers from a given storage array. Which approach correctly uses memory allocation?

hard

A. Declare a memory array with length zero, push evens dynamically, then return it

B. Declare a storage array, copy evens, then return it

C. Declare a memory array with max length, copy evens manually, then return a sliced array

D. Declare a memory array with the same length as storage, copy evens, then resize the array

Solution

1. Step 1: Understand memory array limitations

   Memory arrays in Solidity have fixed size; cannot push dynamically.

2. Step 2: Choose correct approach for filtering

   Declare a memory array with max length, copy even numbers manually, then return a sliced array with correct size.

3. Final Answer:

   Declare a memory array with max length, copy evens manually, then return a sliced array -> Option C

4. Quick Check:

   Memory arrays fixed size = Declare a memory array with max length, copy evens manually, then return a sliced array [OK]

Hint: Memory arrays fixed size; slice after copying [OK]

Common Mistakes:

• Trying to push to memory arrays
• Using storage arrays for temporary filtering
• Not resizing array before returning