Off-chain Infrastructure for Blockchain and Web3 Developers
Off-chain infrastructure is everything a contract depends on but cannot do itself. Oracles such as Chainlink bring external data like prices onto the chain, keeper and automation networks trigger functions on a schedule, and decentralised storage such as IPFS or Arweave holds large files, with only a content hash stored on-chain.
Stage: Applications · Part of the Blockchain and Web3 Developer roadmap · Last reviewed 19 November 2026
What to learn in Off-chain Infrastructure
- Read a price feed and check for stale or zero answers
- Explain why a contract cannot call a web API directly
- Store NFT metadata on IPFS and reference it by content identifier
- Trigger a recurring contract function with an automation network
- Weigh the trust assumptions of a single oracle against many
Off-chain Infrastructure interview questions
Why do smart contracts need oracles?
The chain is deterministic, so every node must reach the same result from the same inputs. A contract therefore cannot fetch outside data itself. An oracle network publishes external values, such as asset prices, on-chain where contracts can read them.
What does an IPFS content identifier give you that a normal URL does not?
A content identifier is derived from the file's hash, so the address changes if the content changes. Anyone can verify what they fetched matches what was referenced on-chain, regardless of which node serves it. A normal URL only points to a location.
Where Off-chain Infrastructure fits in the Blockchain and Web3 Developer roadmap
Off-chain Infrastructure belongs to the Applications stage (intermediate level), which takes about 9 hours. From contract to product.
Other units in this stage
Back to the full Blockchain and Web3 Developer roadmap