Stork

• Name: Stork
• URL: https://www.stork.network/
• Category: oracle / low-latency market-data infrastructure / pull-oracle delivery layer
• Summary: Stork is signed-payload delivery for low-latency feeds, not a new oracle center of gravity. Publishers sign raw data, Stork-run aggregators decide the delivered aggregate, and users choose whether to keep that payload offchain or drag it onchain at the moment of use. Useful delivery layer, still below the main oracle anchors.
• 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

Internal linkages

• Best upward reads for the same low-latency oracle branch: pyth-network and redstone.

Control surface

• The leverage sits in publisher admission, aggregator operation, weighting policy, freshness thresholds, and which fetch or submission path downstream apps treat as normal.

• Real delivery middleware, still not the category center.

• 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.

• Sources:

  • https://www.stork.network/
  • https://docs.stork.network/
  • https://docs.stork.network/introduction/core-concepts
  • https://docs.stork.network/introduction/how-it-works
  • https://github.com/Stork-Oracle
  • https://github.com/Stork-Oracle/stork-external

• Last reviewed: 2026-06-15 UTC