1
0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-26 19:49:26 +01:00

Made various small edits and restructuring to again, try to smooth out the onboard/UX. Added a section on Ranked Rewards.

This commit is contained in:
idiom-bytes 2023-03-23 12:17:46 -07:00
parent a2c2c832cf
commit 9b59f5b014
3 changed files with 47 additions and 33 deletions

View File

@ -12,6 +12,20 @@ Thus, if you really want to max out your APY:
Driving DCV for publishing & consuming is your challenge. It will take real work. And then the reward is APY. Its incentives all the way down:)
## Reward Function
The Reward Function (RF) governs how active rewards are allocated to stakers.
Rewards are calculated as follows:
1. Distribute OCEAN across each asset based on rank: highest-DCV asset gets most OCEAN, etc.
1. For each asset and each veOCEAN holder:
If the holder is a publisher, 2x the effective stake
Baseline rewards = (% stake in asset) * (OCEAN for asset)
Bound rewards to the asset by 125% APY
Bound rewards by assets DCV * 0.1%. This prevents wash consume.
You can find this code inside [calcrewards.py](https://github.com/oceanprotocol/df-py/blob/main/util/calcrewards.py) in the Ocean Protocol [df-py repo](https://github.com/oceanprotocol/df-py/)
## Data Assets that Qualify for DF
Data assets that have veOCEAN allocated towards them get DF rewards.
@ -23,21 +37,6 @@ To qualify for DF, a data asset must also:
- Be visible on [Ocean Market](https://market.oceanprotocol.com/)
- Cant be in [purgatory](https://github.com/oceanprotocol/list-purgatory/blob/main/policies/README.md)
## Reward Function
The Reward Function (RF) governs how active rewards are allocated to stakers.
Rewards are calculated as follows:
First, distribute OCEAN across each asset based on rank: highest-DCV asset gets most OCEAN, etc.
Then, for each asset and each veOCEAN holder:
If the holder is a publisher, 2x the effective stake
Baseline rewards = (% stake in asset) * (OCEAN for asset)
Bound rewards to the asset by 125% APY
Bound rewards by assets DCV * 0.1%. This prevents wash consume.
Here is the code from [calcrewards.py](https://github.com/oceanprotocol/df-py/blob/main/util/calcrewards.py) in the Ocean Protocol [df-py repo](https://github.com/oceanprotocol/df-py/)
## 3 Phases of Data Farming
Data Farming has evolved over time and will continue to do so as the Emission Curve progresses. Below are important dates and parameters incurred during the evolution of the Data Farming program.

View File

@ -39,6 +39,38 @@ The nerdy version: if you lock OCEAN on day x, youll be able to claim rewards
This behavior is inherited from [veCRV](https://curve.readthedocs.io/dao-fees.html); [heres the code](https://github.com/oceanprotocol/contracts/blob/main/contracts/ve/veFeeDistributor.vy#L240-L256).
## DF Main
DF Main started Mar 16, 2023 in DF Round 29. DF29 has 150K OCEAN rewards available (a 2x increase from DF28). As DF Main progresses, rewards will increase to 300K (another 2x), then 600K (another 2x), then beyond 1.1M OCEAN/week (near 2x) then decaying over time.
As of DF29, wash consuming will no longer be profitable. So, organically-generated Data Consume Volume will be the main driver of active DF rewards.
[Example APYs are 520%](emissions-apys.md#example-apys) between Passive & Active rewards.
Full implementation of DF Main will be over many months, after which DF will be decentralized.
DF Main lasts for decades.
## Reward Schedule
The table below cross-references DF Round Number, Start Date, Phase & Week, Sub-Phase & Week, and OCEAN Rewards/Week.
![](./images/reward_schedule.png)
_Ocean Reward Schedule for the next 20+ years_
## Ranked Rewards
In DF23 Ranked Rewards were introduced and smooth the reward distribution by using a logarithmic function.
**Since rewards are distributed across the Top 100 assets (current tuning Mar — 2023), all participants (Publishers & Curators) are now incentivized to support a broader range of assets rather than optimizing on a single asset.**
At the top-end, this helps increase quality and diversification of inventory.
At the bottom-end, this eliminates some potential free-rider issues and smooths out the reward distribution.
![](images/ranked_rewards_study.png)
You can read more about the implementation [in this blog post](https://blog.oceanprotocol.com/data-farming-df22-completed-df23-started-reward-function-tuned-ffd4359657ee) and find the full study [in these slides](https://docs.google.com/presentation/d/1zZdWfywruMPt6r7vfl0nQD8Fgj4wkfuMslZcWJmy3GE/edit?usp=sharing).
## 2x Bonus - Publisher Rewards
As part of our efforts to increase the efficiency of the Reward Function, we researched a broad range of improvements that could be implemented and discussed their many outcomes.
@ -50,21 +82,4 @@ We explored dozens of possible ways to do it. In the end, we arrived at this app
For Data Farming, we want to incentivize publishers to create more data sets, build more token-gated product, innovate how builders can consume Data-tokens.
*All the veOCEAN a publisher has allocated to an asset theyve published (“staked”) is treated as 2x the stake for rewards calculation.*
## DF Main
DF Main started Mar 16, 2023 in DF Round 29. DF29 has 150K OCEAN rewards available (a 2x increase from DF28). As DF Main progresses, rewards will increase to 300K (another 2x), then 600K (another 2x), then beyond 1.1M OCEAN/week (near 2x) then decaying over time.
As of DF29, wash consuming will no longer be profitable. So, organically-generated Data Consume Volume will be the main driver of active DF rewards.
[Example APYs are 520%](emissions-apys.md#example-apys) between Passive & Active rewards.
Full implementation of DF Main will be over many months, after which DF will be decentralized. DF Main lasts for decades.
## Reward Schedule
The table below cross-references DF Round Number, Start Date, Phase & Week, Sub-Phase & Week, and OCEAN Rewards/Week.
![](./images/reward_schedule.png)
_Ocean Reward Schedule for the next 20+ years_
*All the veOCEAN a publisher has allocated to an asset theyve published (“staked”) is treated as 2x the stake for rewards calculation.*

Binary file not shown.

After

Width:  |  Height:  |  Size: 182 KiB