ERC-721 implementation in Blockchain / Solidity - Time & Space Complexity

Time Complexity: ERC-721 implementation

O(1)

Understanding Time Complexity

When working with ERC-721 tokens, it is important to understand how the time to execute key functions changes as the number of tokens grows.

We want to know how the cost of minting, transferring, or checking ownership changes when more tokens exist.

Scenario Under Consideration

Analyze the time complexity of the following simplified ERC-721 transfer function.

function transferFrom(address from, address to, uint256 tokenId) public {
    require(ownerOf[tokenId] == from, "Not owner");
    ownerOf[tokenId] = to;
    balances[from] -= 1;
    balances[to] += 1;
}
    

This code transfers ownership of a single token from one address to another and updates balances.

Identify Repeating Operations

Look for loops or repeated steps that depend on input size.

• Primary operation: Direct access and update of token ownership and balances.
• How many times: Each transfer handles exactly one token, so operations happen once per call.

How Execution Grows With Input

The function always does a fixed number of steps regardless of how many tokens exist.

Input Size (number of tokens)	Approx. Operations
10	4
100	4
1000	4

Pattern observation: The number of operations stays the same no matter how many tokens exist.

Final Time Complexity

Time Complexity: O(1)

This means the transfer function runs in constant time, doing the same amount of work no matter how many tokens there are.

Common Mistake

[X] Wrong: "Transferring a token takes longer as more tokens exist because the contract must check all tokens."

[OK] Correct: The contract uses direct lookups by token ID, so it does not check all tokens. It only updates the specific token involved.

Interview Connect

Understanding how smart contract functions scale with data size is a key skill. It shows you can write efficient blockchain code that saves gas and runs smoothly.

Self-Check

"What if the transfer function needed to check a list of all tokens owned by the sender? How would the time complexity change?"

Practice

1.

What is the main purpose of the ERC-721 standard in blockchain?

easy

A. To create fungible tokens like cryptocurrencies

B. To manage smart contract ownership

C. To create unique, non-fungible tokens (NFTs)

D. To enable fast transaction processing

Solution

1. Step 1: Understand ERC-721 token type

   ERC-721 defines a standard for unique tokens, unlike fungible tokens which are identical.

2. Step 2: Identify the purpose of ERC-721

   It is used to create NFTs, which are unique digital assets on the blockchain.

3. Final Answer:

   To create unique, non-fungible tokens (NFTs) -> Option C

4. Quick Check:

   ERC-721 = Unique NFTs [OK]

Hint: ERC-721 is for unique tokens, not identical ones [OK]

Common Mistakes:

• Confusing ERC-721 with ERC-20 fungible tokens
• Thinking ERC-721 manages contract ownership
• Assuming ERC-721 speeds up transactions

2.

Which of the following is the correct way to inherit OpenZeppelin's ERC721 contract in Solidity?

contract MyNFT is ? {}

easy

A. SafeMath

B. ERC721

C. Ownable

D. ERC20

Solution

1. Step 1: Identify the correct base contract for NFTs

   ERC721 is the OpenZeppelin contract for NFTs, ERC20 is for fungible tokens.

2. Step 2: Confirm inheritance syntax

   Using is ERC721 correctly inherits the NFT functionality.

3. Final Answer:

   ERC721 -> Option B

4. Quick Check:

   Inherit ERC721 for NFTs [OK]

Hint: Use ERC721 to inherit NFT features [OK]

Common Mistakes:

• Using ERC20 instead of ERC721
• Confusing Ownable with ERC721
• Trying to inherit SafeMath for NFTs

3.

What will be the output of the following Solidity function when called?

function mintToken(address to, uint256 tokenId) public {
    _mint(to, tokenId);
}

// Assume _mint works as expected and tokenId = 1, to = 0x123...

What happens after calling mintToken(0x123..., 1)?

medium

A. A new NFT with tokenId 1 is assigned to address 0x123...

B. The tokenId 1 is burned from address 0x123...

C. The function throws a syntax error

D. The tokenId 1 is transferred from 0x123... to the caller

Solution

1. Step 1: Understand the _mint function

   _mint creates a new token with the given tokenId and assigns it to the 'to' address.

2. Step 2: Analyze the function call

   Calling mintToken with address 0x123... and tokenId 1 creates that NFT for 0x123....

3. Final Answer:

   A new NFT with tokenId 1 is assigned to address 0x123... -> Option A

4. Quick Check:

   mintToken creates NFT for 'to' address [OK]

Hint: _mint assigns new token to given address [OK]

Common Mistakes:

• Thinking _mint burns tokens
• Assuming _mint transfers tokens
• Expecting syntax errors from correct code

4.

Identify the error in this Solidity snippet for minting an ERC-721 token:

function mint(address to, uint256 tokenId) public {
    _mint(tokenId, to);
}

medium

A. Function must be named mintToken, not mint

B. _mint cannot be called inside a public function

C. tokenId must be a string, not uint256

D. _mint parameters are reversed; should be (to, tokenId)

Solution

1. Step 1: Check _mint function parameter order

   OpenZeppelin's _mint expects (address to, uint256 tokenId).

2. Step 2: Compare with given code

   The code uses _mint(tokenId, to), reversing the parameters.

3. Final Answer:

   _mint parameters are reversed; should be (to, tokenId) -> Option D

4. Quick Check:

   _mint(to, tokenId) correct order [OK]

Hint: _mint needs (address, tokenId) order [OK]

Common Mistakes:

• Swapping parameters of _mint
• Thinking _mint can't be public
• Confusing tokenId type

5.

You want to create an ERC-721 contract that only allows the contract owner to mint new tokens. Which of these Solidity code snippets correctly enforces this?

contract MyNFT is ERC721, Ownable {
    function mint(address to, uint256 tokenId) public {
        ?
        _mint(to, tokenId);
    }
}

hard

A. require(msg.sender == owner(), "Not owner");

B. require(to == owner(), "Not owner");

C. require(tokenId > 0, "Invalid tokenId");

D. require(msg.sender != owner(), "Owner cannot mint");

Solution

1. Step 1: Understand ownership check

   Only the contract owner should mint, so check if msg.sender equals owner().

2. Step 2: Analyze each require statement

   require(msg.sender == owner(), "Not owner"); correctly checks sender is owner; others check wrong conditions.

3. Final Answer:

   require(msg.sender == owner(), "Not owner"); -> Option A

4. Quick Check:

   Owner check uses msg.sender == owner() [OK]

Hint: Check msg.sender equals owner() before minting [OK]

Common Mistakes:

• Checking 'to' address instead of sender
• Allowing anyone to mint without checks
• Using wrong require conditions