Oracle integration (Chainlink) in Blockchain / Solidity - Time & Space Complexity

Time Complexity: Oracle integration (Chainlink)

O(n)

Understanding Time Complexity

When using Chainlink oracles, we want to know how the time to get data changes as we ask for more information.

We ask: How does the number of oracle requests affect the time our smart contract takes?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

contract PriceConsumer {
  address[] public oracles;

  function requestPrices() public {
    for (uint i = 0; i < oracles.length; i++) {
      Chainlink.Request memory req = buildChainlinkRequest(...);
      sendChainlinkRequestTo(oracles[i], req, fee);
    }
  }
}
    

This code sends a price request to each oracle in a list one by one.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Loop over the list of oracles to send requests.
• How many times: Once for each oracle in the array.

How Execution Grows With Input

As the number of oracles grows, the contract sends more requests, so the time grows directly with the number of oracles.

Input Size (n)	Approx. Operations
10	10 requests sent
100	100 requests sent
1000	1000 requests sent

Pattern observation: The time increases steadily as more oracles are added.

Final Time Complexity

Time Complexity: O(n)

This means the time to send requests grows in direct proportion to the number of oracles.

Common Mistake

[X] Wrong: "Sending requests to multiple oracles happens instantly all at once."

[OK] Correct: Each request is sent one by one in a loop, so more oracles mean more time spent sending requests.

Interview Connect

Understanding how your contract's time grows with oracle calls shows you can write efficient blockchain code that scales well.

Self-Check

"What if we batch multiple oracle requests into one call? How would the time complexity change?"

Practice

1. What is the main purpose of using Chainlink oracles in smart contracts?

easy

A. To encrypt data stored on the blockchain

B. To fetch real-world data securely into the blockchain

C. To create new tokens automatically

D. To speed up transaction processing on the blockchain

Solution

1. Step 1: Understand what oracles do

   Oracles connect smart contracts to external data sources outside the blockchain.

2. Step 2: Identify the main use of Chainlink oracles

   Chainlink oracles securely fetch real-world data like prices or weather into smart contracts.

3. Final Answer:

   To fetch real-world data securely into the blockchain -> Option B

4. Quick Check:

   Oracle purpose = fetch external data [OK]

Hint: Oracles bring outside data inside smart contracts [OK]

Common Mistakes:

• Thinking oracles speed up blockchain transactions
• Confusing oracles with token creation
• Assuming oracles encrypt blockchain data

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

easy

A. Chainlink.Request memory req = buildChainlinkRequest(jobId, address(this), this.fulfill.selector);

B. Chainlink.Request req = new Chainlink.Request(jobId, address(this), fulfill);

C. Request memory req = Chainlink.buildRequest(jobId, this, fulfill);

D. ChainlinkRequest req = buildRequest(jobId, this, fulfill.selector);

Solution

1. Step 1: Recall Chainlink request syntax

   The correct syntax uses Chainlink.Request memory and buildChainlinkRequest function.

2. Step 2: Match the correct parameters

   Parameters are jobId, contract address (address(this)), and fulfill function selector (this.fulfill.selector).

3. Final Answer:

   Chainlink.Request memory req = buildChainlinkRequest(jobId, address(this), this.fulfill.selector); -> Option A

4. Quick Check:

   Correct request syntax = Chainlink.Request memory req = buildChainlinkRequest(jobId, address(this), this.fulfill.selector); [OK]

Hint: Use buildChainlinkRequest with memory and fulfill.selector [OK]

Common Mistakes:

• Omitting 'memory' keyword
• Using 'new' keyword incorrectly
• Wrong function selector syntax

3. Given this Solidity snippet, what will be the value of data after fulfillment?

uint256 public data;

function fulfill(bytes32 _requestId, uint256 _value) public recordChainlinkFulfillment(_requestId) {
    data = _value;
}

// Assume fulfill is called with _value = 42

medium

A. 0

B. RequestId bytes32 value

C. Compilation error

D. 42

Solution

1. Step 1: Understand fulfill function behavior

   The fulfill function sets the contract's data variable to the passed _value.

2. Step 2: Apply given input value

   Since fulfill is called with _value = 42, data becomes 42.

3. Final Answer:

   42 -> Option D

4. Quick Check:

   fulfill sets data = _value = 42 [OK]

Hint: fulfill sets data to passed _value parameter [OK]

Common Mistakes:

• Confusing _requestId with _value
• Assuming data stays zero
• Thinking function causes error

4. Identify the error in this Chainlink oracle request code snippet:

Chainlink.Request memory req = buildChainlinkRequest(jobId, address(this), this.fulfill.selector);
req.add("get", "https://api.example.com/data");
req.add("path", "price");
sendChainlinkRequest(req, fee);

medium

A. Missing LINK token approval before sending request

B. Incorrect function name: should be sendChainlinkRequestTo

C. Missing import for Chainlink library

D. Using 'add' instead of 'addString' for parameters

Solution

1. Step 1: Review Chainlink request sending requirements

   Before sending a request, the contract must have LINK tokens approved to pay the oracle fee.

2. Step 2: Check code for LINK approval

   The snippet does not show LINK token approval, which is required to avoid failure.

3. Final Answer:

   Missing LINK token approval before sending request -> Option A

4. Quick Check:

   LINK approval needed before sendChainlinkRequest [OK]

Hint: Always approve LINK tokens before sending requests [OK]

Common Mistakes:

• Assuming sendChainlinkRequestTo is correct function
• Confusing add and addString methods
• Ignoring LINK token approval step

5. You want to fetch the current ETH/USD price using Chainlink in your smart contract. Which steps must you combine to do this correctly?

hard

A. Use Chainlink request but omit fulfill function to save gas

B. Directly call the price feed contract without Chainlink oracles

C. Build a Chainlink request with jobId and URL, send request with fee, implement fulfill to store price

D. Send request without specifying jobId and rely on default oracle

Solution

1. Step 1: Build and send Chainlink request

   Create a request specifying jobId and data source URL, then send it with the required fee.

2. Step 2: Implement fulfill function

   Define fulfill to receive the oracle response and store the ETH/USD price in your contract.

3. Final Answer:

   Build a Chainlink request with jobId and URL, send request with fee, implement fulfill to store price -> Option C

4. Quick Check:

   Request + fee + fulfill = correct Chainlink usage [OK]

Hint: Request data, pay fee, handle response in fulfill [OK]

Common Mistakes:

• Skipping fulfill function implementation
• Not specifying jobId in request
• Assuming default oracle without jobId