Library contracts in Blockchain / Solidity - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a library contract in blockchain development?

A library contract is a reusable piece of code deployed once on the blockchain that other contracts can call to save space and gas costs. It contains common functions shared across multiple contracts.

beginner

How do library contracts help reduce gas costs?

Library contracts reduce gas costs by allowing multiple contracts to share the same code deployed once, instead of each contract having its own copy. This saves deployment and execution costs.

intermediate

Can library contracts hold state variables?

No, library contracts cannot hold state variables because they are stateless. They only contain reusable functions and cannot store data on the blockchain themselves.

intermediate

What is the difference between a library contract and an inherited contract?

A library contract is deployed separately and linked at deployment time, while an inherited contract's code is copied into the child contract. Libraries save space and gas by sharing code, whereas inheritance duplicates code.

beginner

How do you call a function from a library contract in Solidity?

You call a library function by linking the library to your contract and then calling the function as if it were part of your contract. Solidity handles the linking automatically during deployment.

What is the main benefit of using library contracts in blockchain?

A Reusing code to save gas and deployment costs

B Storing user data securely

C Creating new tokens

D Managing contract ownership

Library contracts allow code reuse, reducing gas and deployment costs by sharing common functions.

Can a library contract have state variables?

A Only if inherited

B Yes, always

C No, libraries are stateless

D Only if deployed separately

Library contracts cannot have state variables because they are stateless and only contain reusable functions.

How is a library contract linked to another contract in Solidity?

A By copying its code into the contract

B By importing its source code only

C By inheritance

D By deploying it separately and linking at deployment time

Libraries are deployed separately and linked to contracts at deployment time to enable code reuse.

Which of these is NOT a characteristic of library contracts?

A Can hold Ether

B Reusable code

C Stateless

D Deployed once and shared

Library contracts cannot hold Ether or state; they only provide reusable functions.

Why might you choose inheritance over a library contract?

A To save gas costs

B To share code without deploying separately

C To reuse stateless functions

D To reduce contract size

Inheritance copies code into the child contract, avoiding separate deployment but increasing contract size.

Explain what a library contract is and how it helps in blockchain development.

Think about sharing common functions across contracts.

Describe the differences between using a library contract and inheritance in Solidity.

Consider deployment and code duplication.

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+