# RedStone Classic Model

**Published by:** [Warior](https://paragraph.com/@warior/)
**Published on:** 2024-01-15
**URL:** https://paragraph.com/@warior/redstone-classic-model

## Content

A Time-Honored Approach to On-Chain Data Feeds In the ever-evolving landscape of decentralized finance (DeFi), RedStone presents an innovative Oracle system designed to cater to diverse protocol preferences. While the on-demand fetching model (RedStone Core) stands out for its efficiency and scalability, RedStone Classic embraces a more traditional design, where data is pushed on-chain. Let's explore the nuances of the Classic Model and how it caters to specific protocol needs. Understanding the Need for the Classic Model Despite the efficiency and scalability offered by the pure on-demand fetching model (RedStone Core), RedStone acknowledges that certain protocols may opt for a more traditional design. The Classic Model, where data is pushed on-chain, becomes a viable choice under certain conditions: Existing Well-Audited Codebase: If a protocol boasts an existing well-audited codebase, the team might prefer not to make even minor amendments. The Classic Model seamlessly integrates with such setups without necessitating significant changes. Deployment on Private Networks or Low-Gas Chains: In scenarios where the protocol operates on a private network or a blockchain with minimal gas costs, the Classic Model becomes a reasonable choice. The lowered transaction costs make on-chain data pushing more feasible. Infrequent Price Updates: For protocols where prices don't need to be updated frequently, the Classic Model provides a streamlined approach. It caters to scenarios where real-time price updates are not a critical requirement. How RedStone Classic Operates RedStone Classic is an extension of the RedStone Core model, ensuring the security of on-chain validation for data providers and timestamps. The Classic Model comprises two key components: Off-Chain Relayer: The off-chain relayer serves as the engine for pushing data on-chain in a customized manner based on environment variables. It periodically checks predefined conditions and initiates the price update process when these conditions are satisfied. The relayer's customizable nature allows for flexibility in defining conditions for price updates. On-Chain Contracts: The on-chain contracts form the second part of the Classic Model, enabling the storage of prices and facilitating their retrieval through familiar interfaces like the Chainlink Aggregator. This seamless integration with widely used interfaces enhances the adaptability of RedStone Classic across various blockchain ecosystems. RedStone Classic Compatibility RedStone Classic is not limited by blockchain boundaries; it can seamlessly operate on all EVM-compatible L1s & L2s, including Starknet and the Fuel Network. This cross-chain compatibility ensures that RedStone Classic can integrate with a wide array of protocols and platforms within the decentralized landscape. Relayer Functionality and Customization: The relayer operates in a customizable manner, driven by environment variables. Two primary conditions govern the relayer's functionality: Time Condition: Governed by the UPDATE_PRICE_INTERVAL variable in milliseconds, this condition dictates how often prices should be updated—an interval commonly referred to as a heartbeat. Value-Deviation Condition: Dictated by the MIN_DEVIATION_PERCENTAGE variable, this condition specifies the magnitude of value change required to trigger a price update. RedStone Classic's thoughtful design ensures compatibility with protocols that adhere to a more traditional approach, offering a seamless and secure solution for on-chain data feeds. As the decentralized ecosystem continues to evolve, RedStone Classic stands as a testament to flexibility and adaptability in the ever-expanding DeFi universe.

## Publication Information

- [Warior](https://paragraph.com/@warior/): Publication homepage
- [All Posts](https://paragraph.com/@warior/): More posts from this publication
- [RSS Feed](https://api.paragraph.com/blogs/rss/@warior): Subscribe to updates