Summary: Stork is an oracle protocol focused on ultra-low-latency, cryptographically verifiable data delivery for both onchain and offchain applications. The official materials describe a pull-oracle architecture in which publisher-signed data streams move through Stork-run aggregators to subscribers, who can consume the feeds offchain or post fresh signed updates onchain when needed. In this pass, the docs and public repo surface made Stork look less like a generic price-feed brand and more like a low-latency data-transport and verification layer for DeFi and related applications.
What it does:
Connects data publishers, aggregators, subscribers, and onchain contracts into a pull-oracle system for delivering signed market data and other timestamped numeric values
Streams publisher-signed data to aggregators, which compute median / average / weighted-average outputs, sign the aggregate, and expose it over websocket and REST interfaces
Lets subscribers use the data offchain or submit the signed updates onchain, including within the same transaction where a smart contract consumes the data
Supports more than 500 assets across 70+ chains according to the docs, with contract-address directories spanning EVM chains, Solana, Sui, Aptos, and others
Publishes open-source tooling and contracts for publishers and subscribers through the Stork GitHub surface, including the publisher agent and external integration components
Key claims:
Official docs describe Stork as an oracle protocol enabling ultra-low-latency connections between data providers and onchain or offchain applications, with real-time price feeds as the primary use case
The docs position Stork as a pull oracle with sub-second latency, saying aggregators typically provide fresh data every 500ms or whenever aggregate data moves by 0.1%
Core-concepts docs argue that pull-oracle architecture is more latency-efficient and gas-efficient than push-oracle heartbeat models because updates only go onchain when needed
Architecture docs lay out a concrete four-layer design of publishers, subscribers, aggregators, and onchain contracts, with signatures verified in the aggregator, onchain contracts, and optionally by subscribers
The public GitHub materials show Stork shipping open tooling and contracts for external publishers and subscribers rather than operating as a closed black-box oracle service
Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were Stork’s official site, welcome docs, architecture / core-concept docs, and public GitHub repositories; see ../whitepapers/stork-primary-sources-2026-04-25.md.