Library contracts in Blockchain / Solidity - Step-by-Step Execution

Concept Flow - Library contracts

Define Library Contract

↓

Deploy Library

↓

Link Library Address to Main Contract

↓

Deploy Main Contract

↓

Main Contract Calls Library Functions

↓

Library Code Executes in Main Contract Context

↓

End

Library contracts are deployed once and linked to main contracts, allowing code reuse without copying, executing in the caller's context.

Execution Sample

Blockchain / Solidity

library MathLib {
  function add(uint a, uint b) internal pure returns (uint) {
    return a + b;
  }
}

contract Calculator {
  function sum(uint x, uint y) public pure returns (uint) {
    return MathLib.add(x, y);
  }
}

This code defines a library with an add function and a contract that uses it to sum two numbers.

Execution Table

Step	Action	Evaluation	Result
1	Deploy MathLib library	Library code stored on blockchain	MathLib address assigned
2	Deploy Calculator contract linked to MathLib	Calculator knows MathLib address	Calculator deployed with link
3	Call Calculator.sum(3, 4)	Calls MathLib.add(3, 4)	7 returned
4	MathLib.add executes in Calculator context	Adds 3 + 4	7 computed
5	Return result to caller	7 returned from sum	7 output
6	End	No more steps	Execution complete

💡 Execution stops after returning the sum result from the library function.

Variable Tracker

Variable	Start	After sum call	After add call	Final
a	undefined	3	3	3
b	undefined	4	4	4
result	undefined	undefined	7	7

Key Moments - 3 Insights

Why does the library code run in the main contract's context?

Because library functions are called using delegatecall, they execute with the main contract's storage and context, as shown in step 4 of the execution_table.

Does the library get deployed every time the main contract is deployed?

No, the library is deployed once separately (step 1), and the main contract links to its address (step 2), avoiding code duplication.

What happens if the library address is not linked correctly?

The main contract will fail to call the library functions, causing runtime errors or failed transactions, as linking is essential (step 2).

Visual Quiz - 3 Questions

Look at the execution_table, what is the result returned by MathLib.add at step 4?

A 7

B 3

C 4

D 0

💡 Hint

Check the 'Result' column at step 4 in the execution_table.

At which step does the Calculator contract get linked to the MathLib library?

A Step 1

B Step 3

C Step 2

D Step 5

💡 Hint

Look for the step mentioning linking in the execution_table.

If the library was not deployed first, which step would fail?

A Step 1

B Step 2

C Step 3

D Step 6

💡 Hint

Refer to the execution_table step where linking happens.

Concept Snapshot

Library contracts are reusable code blocks deployed once.
Main contracts link to libraries by address.
Library functions run in caller's context using delegatecall.
This saves gas and avoids code duplication.
Always deploy libraries before linking.

Full Transcript

Library contracts in blockchain are special contracts that hold reusable code. They are deployed once and then linked to other contracts that want to use their functions. When a main contract calls a library function, the library code runs in the main contract's context, meaning it uses the main contract's storage and environment. This is done using a special call called delegatecall. The process starts by deploying the library contract, then deploying the main contract linked to the library's address. When the main contract calls a library function, the library executes and returns the result. This approach saves space and gas because the library code is not copied into every contract. If the library is not deployed or linked correctly, calls to it will fail. The example code shows a MathLib library with an add function and a Calculator contract that uses it to sum two numbers. The execution table traces deployment, linking, calling, and returning results step by step.

Practice

1. What is the main purpose of a library contract in blockchain development?

easy

A. To reuse code across multiple smart contracts

B. To store user data permanently

C. To mine new blocks

D. To create new tokens

Solution

1. Step 1: Understand the role of library contracts

   Library contracts contain reusable code that can be called by other contracts to avoid duplication.

2. Step 2: Compare options with library purpose

   Only To reuse code across multiple smart contracts correctly describes code reuse, while others describe unrelated blockchain functions.

3. Final Answer:

   To reuse code across multiple smart contracts -> Option A

4. Quick Check:

   Library = Code reuse [OK]

Hint: Library contracts are for sharing code, not storing data [OK]

Common Mistakes:

• Confusing libraries with data storage contracts
• Thinking libraries create tokens
• Assuming libraries mine blocks

2. Which of the following is the correct way to declare a library in Solidity?

easy

A. library MyLib {}

B. contract MyLib {}

C. interface MyLib {}

D. struct MyLib {}

Solution

1. Step 1: Recall Solidity keywords for libraries

   Solidity uses the keyword library to declare a library contract.

2. Step 2: Check each option's keyword

   Only library MyLib {} uses library. Others declare contract, interface, or struct, which are different constructs.

3. Final Answer:

   library MyLib {} -> Option A

4. Quick Check:

   Keyword for library = library [OK]

Hint: Use 'library' keyword to declare libraries in Solidity [OK]

Common Mistakes:

• Using 'contract' instead of 'library'
• Confusing interfaces with libraries
• Trying to declare libraries as structs

3. Given the following Solidity code, what will be the output of test.getDouble(5)?

library MathLib {
    function double(uint x) internal pure returns (uint) {
        return x * 2;
    }
}

contract Test {
    using MathLib for uint;
    function getDouble(uint value) public pure returns (uint) {
        return value.double();
    }
}

medium

A. 5

B. 10

C. Compilation error

D. 0

Solution

1. Step 1: Understand the library function call

   The library MathLib defines a function double that multiplies input by 2.

2. Step 2: Analyze the usage in contract Test

   Using using MathLib for uint; allows calling double() on uint variables. So value.double() returns 5 * 2 = 10.

3. Final Answer:

   10 -> Option B

4. Quick Check:

   5 * 2 = 10 [OK]

Hint: Library functions called with 'using for' act on the type [OK]

Common Mistakes:

• Expecting the original value instead of doubled
• Thinking 'using for' is optional for calling library functions
• Confusing internal and public function visibility

4. Identify the error in the following Solidity code using a library:

library Utils {
    function increment(uint x) public pure returns (uint) {
        return x + 1;
    }
}

contract Counter {
    using Utils for uint;
    uint count;
    function increase() public {
        count = count.increment();
    }
}

medium

A. Cannot use 'using for' with uint type

B. Missing constructor in contract

C. Library function must be internal, not public

D. Function increase should be view

Solution

1. Step 1: Check library function visibility

   Library functions used with 'using for' must be internal, not public.

2. Step 2: Verify other options

   No constructor is needed here, 'using for' works with uint, and increase modifies state so cannot be view.

3. Final Answer:

   Library function must be internal, not public -> Option C

4. Quick Check:

   Library function visibility = internal [OK]

Hint: Library functions called via 'using for' cannot be public [OK]

Common Mistakes:

• Declaring library functions as public
• Thinking 'using for' can't be used with uint
• Marking state-changing functions as view

5. You want to create a library that provides a function to safely add two unsigned integers without overflow. Which of the following code snippets correctly implements this using Solidity 0.8+ features and can be used with using for in other contracts?

hard

A. library SafeMath {
function safeAdd(uint a, uint b) internal view returns (uint) {
return a + b;
}
}

B. library SafeMath {
function safeAdd(uint a, uint b) public pure returns (uint) {
return a + b;
}
}

C. library SafeMath {
function safeAdd(uint a, uint b) internal pure returns (uint) {
unchecked {
return a + b;
}
}
}

D. library SafeMath {
function safeAdd(uint a, uint b) internal pure returns (uint) {
uint c = a + b;
require(c >= a, "Overflow");
return c;
}
}

Solution

1. Step 1: Check function visibility and usage

   Library functions used with 'using for' must be internal. library SafeMath { function safeAdd(uint a, uint b) public pure returns (uint) { return a + b; } } uses public (invalid), D uses view which is incorrect for pure functions. library SafeMath { function safeAdd(uint a, uint b) internal pure returns (uint) { uint c = a + b; require(c >= a, "Overflow"); return c; } } uses internal pure.

2. Step 2: Verify overflow check and Solidity 0.8+ behavior

   Solidity 0.8+ has built-in overflow checks, so unchecked block in C disables protection and returns wrapped value on overflow. library SafeMath { function safeAdd(uint a, uint b) internal pure returns (uint) { uint c = a + b; require(c >= a, "Overflow"); return c; } } correctly relies on built-in checks with additional require guard and no unchecked block.

3. Final Answer:

   library SafeMath { function safeAdd(uint a, uint b) internal pure returns (uint) { uint c = a + b; require(c >= a, "Overflow"); return c; } } -> Option D

4. Quick Check:

   Internal pure function with overflow check = library SafeMath { function safeAdd(uint a, uint b) internal pure returns (uint) { uint c = a + b; require(c >= a, "Overflow"); return c; } } [OK]

Hint: Use internal pure functions with require for safe math [OK]

Common Mistakes:

• Using public visibility in library functions
• Using view instead of pure for math functions
• Unnecessary unchecked blocks in Solidity 0.8+