Tokenomics update (#112)

* kuba-docs-refactor * fix broken links * fix one icon * old yarn * remove changes from lock file * linting * prettify * fix broken link * delete old pages * new intro * check audit links * prettify * additional audits links * small fixes & tokenomics * fix headings syntax * update docs * prettify * update getting started section * prettify * linting * small fixes / typos * linting * remove model x * formatting * update tokenomics * keep yarn.lock * prettify --------- Co-authored-by: Daniel Szerszeń <szerszen.daniel@gmail.com>
redstone-finance · Feb 27, 2025 · 0927e68 · 0927e68
1 parent a5a4f12
commit 0927e68
Show file tree

Hide file tree

Showing 11 changed files with 152 additions and 14 deletions.
diff --git a/docs/architecture.md b/docs/architecture.md
@@ -20,7 +20,7 @@ The data could be pushed onto the blockchain either by a dedicated relayer opera
 
 ### Context
 
-Transferring data to a blockchain requires packing an extra payload to a user’s transaction and processing the message on the blockchain. Said differently, the data that is put on the blockchain, such as a cryptocurrency’s price, is inserted into part of the data that makes up a user’s transaction. This is accomplishable because blockchains move from state-to-state and contain call data. RedStone is able insert its data into the call data of a user's transaction, thereby putting the data onto the blockchain.
+Transferring data to a blockchain requires packing an extra payload to a user’s transaction and processing the message on the blockchain. Said differently, the data that is put on the blockchain, such as a cryptocurrency’s price, is inserted into part of the data that makes up a user’s transaction. This is accomplishable because blockchains move from state-to-state and contain call data. RedStone is able to insert its data into the call data of a user's transaction, thereby putting the data onto the blockchain.
 
 ### How Data is Encoded Before Being Put on the Blockchain
 

diff --git a/docs/dapps/redstone-pull.mdx b/docs/dapps/redstone-pull.mdx
@@ -135,7 +135,7 @@ For all the supported feeds we provide [UI with charts and historical data](http
 
 💡 Note: You can also override the following functions (do it at your own risk):
 
-- `isTimestampValid(uint256 receivedTimestamp) returns (bool)` - to enable custom logic of timestamp validation. You may specify a shorter delay to accept only the most recent price fees. However, on networks with longer block times you may extend this period to avoid rejecting too many transactions.
+- `isTimestampValid(uint256 receivedTimestamp) returns (bool)` - to enable custom logic of timestamp validation. You may specify a shorter delay to accept only the most recent price fees. However, on networks with longer block times, you may extend this period to avoid rejecting too many transactions.
 
 - `aggregateValues(uint256[] memory values) returns (uint256)` - to enable custom logic of aggregating values from different providers (by default this function takes the median value). For example, you may request values from providers to be strictly equal while dealing with discrete numbers.
 
@@ -219,7 +219,7 @@ We have prepared [repository](https://github.com/redstone-finance/minimal-foundr
 This approach is helpful if you need to pass the pricing data from one contract to another in your protocol.
 
 It's also a solution for a case, where your contracts are written in solidity in a version lower than `0.8.4` it could be problematic to extend from the `RedstoneConsumerBase` contract.
-In that case we recomment to deploy a separate `Extractor` contract that will contain the verification logic:
+In that case, we recomment to deploy a separate `Extractor` contract that will contain the verification logic:
 
 ```sol
 pragma solidity 0.8.4;

diff --git a/docs/dapps/redstone-push.md b/docs/dapps/redstone-push.md
@@ -7,7 +7,7 @@ sidebar_label: "Push model"
 
 Ideal for dApps deeply integrated with existing protocols and traditional data consumption patterns
 
-RedStone's Push Model stores data directly on-chain through periodic updates, following the traditional oracle approach. This model ensures constant data availability and gives applications full control over update conditions and data sources.
+RedStone's Push Model stores data directly on-chain through periodic updates, following the traditional blockchain oracle approach. This model ensures constant data availability and gives applications full control over update conditions and data sources.
 
 Here you can find the [**list of all the feeds**](https://app.redstone.finance/app/feeds/) available with update parameters.
 
@@ -27,7 +27,7 @@ The model consists of two main parts. The first one is the off-chain [relayer](#
 
 ### Relayer
 
-The relayer is a service that works in a customizable way based on [environment variables](#environment-variables). It periodically checks a defined set of conditions, pushing the prices when they are satisfied. It is possible to pass multiple conditions to the `UPDATE_CONDITIONS`, then the relayer will work in the manner that if any conditions are met prices would be updated. Currently, two conditions are implemented:
+The relayer is a service that works in a customizable way based on [environment variables](#environment-variables). It periodically checks a defined set of conditions, pushing the prices when they are satisfied. It is possible to pass multiple conditions to the `UPDATE_CONDITIONS`, then the relayer will work in the manner that if any conditions are met prices will be updated. Currently, two conditions are implemented:
 
 - a `time` condition described by `UPDATE_PRICE_INTERVAL` variable in milliseconds, which states how often prices should be updated (aka heartbeat), [code](https://github.com/redstone-finance/redstone-oracles-monorepo/blob/main/packages/on-chain-relayer/src/core/update-conditions/time-condition.ts)
 

diff --git a/docs/data-providers/deploy.md b/docs/data-providers/deploy.md
@@ -5,10 +5,10 @@ sidebar_label: "Deploy"
 
 # Deploy
 
-In this section you will see how to run a RedStone node using Docker Compose.
+In this section, you will see how to run a RedStone node using Docker Compose.
 
 :::caution
-For production deployments consider using more sofisticated tools, e.g. Kubernetes.
+For production deployments consider using more sophisticated tools, e.g. Kubernetes.
 :::
 
 ### Requirements

diff --git a/docs/data-providers/introduction.md b/docs/data-providers/introduction.md
@@ -5,7 +5,7 @@ sidebar_label: "Introduction"
 
 # Introduction
 
-RedStone is one of the leading oracle providers on the market, but with great power comes great responsibility. In order to minimize the (already small) risk of price manipulation RedStone is allowing other, verified and trusted companies to send oracle data to its gateways. This way we increase safety, transparency and improve data quality.
+RedStone is one of the leading blockchain oracle providers on the market, but with great power comes great responsibility. In order to minimize the (already small) risk of price manipulation RedStone is allowing other, verified and trusted companies to send oracle data to its gateways. This way we increase safety, transparency and improve data quality.
 
 We call those companies **External Oracle Providers** (EOP).
 
@@ -22,7 +22,7 @@ At the end of this stage EOP understands what are the legal consequences of mali
 Now that all legal matters are out of the way EOP will start setting up its own Oracle Node. At this point RedStone’s and EOP’s dev ops contact and set it all up.
 First EOP connects to staging environment where we monitor in detail how stable is the deployment. We record downtime as well as the provided prices - we do everything we can to catch problems before EOP is moved to production.
 
-This stage lasts for as long as it is needed, at least 30 days. RedStone will be in constant contact with EOP's team to inform about the problems so they may be fixed right away.
+This stage lasts for as long as it is needed, at least 30 days. RedStone will be in constant contact with EOP's team to inform them about the problems so they may be fixed right away.
 
 ### Production
 

diff --git a/docs/data/1-data-flow.md b/docs/data/1-data-flow.md
@@ -1,9 +1,9 @@
 ---
 sidebar_position: 1
-sidebar_label: "Fetching process"
+sidebar_label: "Data flow"
 ---
 
-# Fetching process
+# Data flow
 
 ## Data Sources
 
@@ -21,7 +21,7 @@ Integration with more than 50 on-chain trading protocol deployments spans multip
 
 #### Aggregator Service Integration
 
-The framework incorporates data from professional market intelligence providers specializing in cross-source data aggregation, including established entities such as Kaiko, CoinMarketCap and trading venues, supplementing direct exchange feeds with consolidated market metrics.
+The framework incorporates data from professional market intelligence providers specializing in cross-source data aggregation, including established entities such as Kaiko, CoinMarketCap, and trading venues, supplementing direct exchange feeds with consolidated market metrics.
 
 #### Institutional Data Provider Network
 
@@ -37,7 +37,7 @@ Each provider node implements robust cryptographic signing protocols for all dat
 
 ### Quality Assurance Protocol
 
-The system employs comprehensive monitoring mechanisms to evaluate node performance across following parameters:
+The system employs comprehensive monitoring mechanisms to evaluate node performance across the following parameters:
 
 - Continuous monitoring of data consistency and operational uptime
 - Real-time validation of data quality and transmission latency

diff --git a/docs/introduction.md b/docs/introduction.md
@@ -5,7 +5,7 @@ sidebar_label: "What is RedStone?"
 
 # 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 oracle 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 also provides data feeds to blockchains and layer 2 scaling solutions across the entire blockchain ecosystem that are both EVM and non-EVM compatible. The current model of oracle systems suffers from key inefficiencies, all of which RedStone was specifically designed to solve from the bottom up. This makes RedStone a unique oracle service.
+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 also provides data feeds to blockchains and layer 2 scaling solutions across the entire blockchain ecosystem that are both EVM and non-EVM compatible. The current model of blockchain oracle systems suffers from key inefficiencies, all of which RedStone was specifically designed to solve from the bottom up. This makes RedStone a unique oracle service.
 
 ## Mult-chain data delivery
 

diff --git a/docs/token/1-utility.md b/docs/token/1-utility.md
@@ -0,0 +1,26 @@
+---
+sidebar_position: 1
+sidebar_label: "Utility"
+---
+
+# Staking For Economic Security
+
+:::warning
+RED is not live yet
+:::
+
+For oracles to survive and secure DeFi long-term, sustainable tokenomics are essential.
+
+RED is designed as a utility token with an innovative value accrual mechanism, introducing the first truly sustainable oracle economics.
+
+Leveraging RedStone's EigenLayer Actively Validated Service (AVS), RED staking adds a robust layer of economic security to RedStone's oracle stack, utilizing staked RED and potentially tapping into billions of dollars staked in EigenLayer for additional security.
+
+RED can be staked by data providers, who supply data to RedStone's modular oracle network, and by token holders, who enhance network security through direct staking in the RedStone AVS.
+
+RED stakers will earn rewards from RedStone data users across hundreds of blockchains, paid in widely adopted assets like ETH, BTC, SOL, and USDC.
+
+![Staking Accrual Flowchart](https://blog.redstone.finance/wp-content/uploads/2025/02/Staking-Accrual-Flowchart-v2.png)
+
+:::info
+THIS IS FOR INFORMATIONAL PURPOSES ONLY AND NOT AN OFFERING TO SELL, THE SOLICITATION OF AN OFFER TO PURCHASE, OR AN ENCOURAGEMENT TO OFFER TOKENS. YOU SHOULD NOT RELY ON THE CONTENT HEREIN FOR ADVICE OF ANY KIND, INCLUDING LEGAL, INVESTMENT, FINANCIAL, TAX, OR OTHER PROFESSIONAL ADVICE, AND SUCH CONTENT IS NOT A SUBSTITUTE FOR ADVICE FROM A QUALIFIED PROFESSIONAL OR YOUR OWN RESEARCH. THIS DOCUMENT CONTAINS HYPOTHETICAL, FORWARD-LOOKING, AND/OR PROJECTED FIGURES, WHICH ARE APPROXIMATE, NOT GUARANTEED AND ARE SUBJECT TO CHANGE; ACTUAL NUMBERS MAY VARY. REDSTONE DISTRIBUTED DATA ASSOCIATION AND ITS SUBSIDIARIES MAKE NO REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, AS TO THE COMPLETENESS, RELIABILITY, VALIDITY, OR ACCURACY OF THIS INFORMATION. ANY INFORMATION CONTAINED HEREIN IS SUBJECT TO CHANGE WITHOUT NOTICE.
+:::
diff --git a/docs/token/2-supply.md b/docs/token/2-supply.md
@@ -0,0 +1,27 @@
+---
+sidebar_position: 2
+sidebar_label: "Supply"
+---
+
+# Supply
+
+:::warning
+RED is not live yet
+:::
+
+RedStone's blockchain oracle technology has achieved product-market fit, operating on mainnet since January 2023 and attracting users with its reliable, diverse, and robust services. Now, the RedStone Distributed Data Association introduces RED—designed to further decentralize the system and advance the long-term goals of the RedStone Ecosystem.
+
+At the core of RedStone is the mission to support builders with any data they need, on any chain, for any use case. As the RED Token Generation Event (TGE) approaches, we present the utility and token economics of RED below.
+
+| Category                       | Details                                                                                                |
+| ------------------------------ | ------------------------------------------------------------------------------------------------------ |
+| Ticker                         | RED                                                                                                    |
+| Max Supply                     | 1,000,000,000 RED                                                                                      |
+| Percentage to Community Growth | 48.3%                                                                                                  |
+| Float at TGE                   | 28%                                                                                                    |
+| Token Standard                 | Ethereum Network: ERC-20                                                                               |
+| Lock Up                        | 72% of RED are initially locked. These tokens will unlock over 4 years per the Token Release Schedule. |
+
+:::info
+THIS IS FOR INFORMATIONAL PURPOSES ONLY AND NOT AN OFFERING TO SELL, THE SOLICITATION OF AN OFFER TO PURCHASE, OR AN ENCOURAGEMENT TO OFFER TOKENS. YOU SHOULD NOT RELY ON THE CONTENT HEREIN FOR ADVICE OF ANY KIND, INCLUDING LEGAL, INVESTMENT, FINANCIAL, TAX, OR OTHER PROFESSIONAL ADVICE, AND SUCH CONTENT IS NOT A SUBSTITUTE FOR ADVICE FROM A QUALIFIED PROFESSIONAL OR YOUR OWN RESEARCH. THIS DOCUMENT CONTAINS HYPOTHETICAL, FORWARD-LOOKING, AND/OR PROJECTED FIGURES, WHICH ARE APPROXIMATE, NOT GUARANTEED AND ARE SUBJECT TO CHANGE; ACTUAL NUMBERS MAY VARY. REDSTONE DISTRIBUTED DATA ASSOCIATION AND ITS SUBSIDIARIES MAKE NO REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, AS TO THE COMPLETENESS, RELIABILITY, VALIDITY, OR ACCURACY OF THIS INFORMATION. ANY INFORMATION CONTAINED HEREIN IS SUBJECT TO CHANGE WITHOUT NOTICE.
+:::