Cowrie Research

redstone-primary-sources-2026-04-23

4 min read

RedStone primary-source snapshot

Fetched: 2026-04-23 UTC

1) Docs introduction

Source: https://docs.redstone.finance/docs/introduction

Selected excerpts from the docs introduction:

There is a growing need for decentralized applications (dApps) to access data feeds that are frequently updated, reliable, and secure. RedStone is a leading blockchain data provider directly fulfilling this need. Trusted by 100+ dApps and securing billions of dollars of value, RedStone provides customizable and cost-efficient data streams for builders empowering the next generation of dApps.

RedStone’s modular architecture separates data collection from data delivery, creating a flexible system that scales efficiently across blockchain networks.

This architectural approach has proven highly successful, enabling RedStone to expand its service to more than 70 different blockchain networks while ensuring reliable price data delivery and maintaining the same rigorous security measures across all integrations.

Additional signals from this page:

  • RedStone is best categorized as a cross-chain oracle and data-delivery network rather than only a token or app-layer product
  • The docs emphasize architectural modularity as the key differentiator
  • The page explicitly frames RedStone as serving both EVM and non-EVM environments

2) Pull-model integration docs

Source: https://docs.redstone.finance/docs/dapps/redstone-pull/

Selected excerpts from the pull-model docs:

RedStone’s Pull Model injects data directly into user transactions, maximizing gas efficiency while simplifying dApp data access.

This streamlined approach handles the entire process in a single transaction, significantly reducing costs.

You need to apply a minimum change to the source code to enable smart contract to access data. Your contract needs to extend one of our base contracts, depending on which data service are you going to use.

Additional signals from this page:

  • The pull model appears to be the clearest technical primitive that distinguishes RedStone from more traditional always-on storage-heavy oracle patterns
  • The documentation is highly implementation-oriented, which makes the docs themselves a primary source of truth for how RedStone is meant to be integrated
  • The page shows RedStone as both a network/service and a developer-tooling stack exposed through Solidity and JavaScript packages

3) GitHub monorepo

Source: https://github.com/redstone-finance/redstone-oracles-monorepo

Selected excerpts from the monorepo README:

Monorepo containing all the main components of the RedStone oracles ecosystem.

RedStone is a data ecosystem that delivers frequently updated, reliable and diverse data for your dApp and smart contracts.

It uses a radically different way of putting data on-chain. The data is automatically attached to a user’s transaction and erased afterwards thus reducing gas fees without touching the expensive evm storage.

Additional signals from this page:

  • The repo structure reinforces that RedStone is a multi-component infrastructure stack, not a single narrow oracle contract
  • Public packages include oracle-node, cache-service, evm-connector, protocol, sdk, and eth-contracts
  • The README usefully corroborates the pull-model/gas-efficiency framing from the docs

4) Audits index

Source: https://docs.redstone.finance/docs/security/audits/

Selected excerpts from the audits page:

RedStone maintains a rigorous external security audit program as a cornerstone of its security assurance framework.

Multiple independent security firms specializing in blockchain infrastructure conduct comprehensive audits of both core protocol components and significant system modifications prior to production deployment.

Additional signals from this page:

  • The page lists a relatively broad public audit trail across components such as oracle phases, EVM connector, token and vesting, adapter contracts, Fuel connector, Sui connector, and aggregator-related work
  • Named auditors on the page include ABDK, AuditOne, Halborn, Codespect, Cantina (SpearBit), and BitsLab
  • This audit index is a meaningful primary diligence surface even though each linked report would need separate review for deeper security conclusions

Notes

  • This pass did not locate a classic whitepaper or litepaper from official RedStone materials.
  • The strongest primary sources were RedStone’s docs portal and GitHub monorepo, supplemented by the public audit index.
  • RedStone is worth cataloging because it occupies an important oracle/data-infrastructure niche and has a distinctive transaction-attached pull-model design that differs from the default mental model many readers have for oracle systems.
  • Adoption, value-secured, uptime, and incident-free claims should still be treated as vendor claims unless independently verified.

Graph View