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

GITBOOK-623: change request with no subject merged in GitBook

Browse Source
This commit is contained in:
Ana Loznianu 2023-06-27 11:06:51 +00:00 committed by gitbook-bot
parent 13fc06d726
commit 67998aed23
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
2 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
infrastructure/README.md
View File

@ -1,20 +1,20 @@
---
description: Infrastructure
description: Learn how to deploy Ocean components in your environment.
cover: ../.gitbook/assets/cover/infrastructure_banner.png
coverY: 0
---
# 🔨 Infrastructure
Now that you know the components of the Ocean Protocol stack and what each does, it's time to learn how to deploy these components in your environment. There are many ways in which the components can be deployed, from simple configurations used for development and testing to complex configurations, used for production systems. 
There are many ways in which the components can be deployed, from simple configurations used for development and testing to complex configurations, used for production systems. 
All the Ocean Protocol components (Provider, Aquarius, Subgraph) are designed to run in Docker containers, on a Linux operating system. For simple configurations, we rely on Docker Engine and Docker Compose products to deploy and run our components, while for complex configurations we use Kubernetes. The guides included in this section will present both deployment options. 
All the Ocean Protocol components ([Provider](../developers/provider/), [Aquarius](../developers/aquarius/), [Subgraph](../developers/subgraph/)) are designed to run in Docker containers, on a Linux operating system. For simple configurations, we rely on Docker Engine and Docker Compose products to deploy and run our components, while for complex configurations we use Kubernetes. The guides included in this section will present both deployment options. 
Please note that deploying the Ocean components requires a good understanding of:
* Linux operating system;
* Docker Engine; 
* Docker Compose or Kubernetes (depending on the configuration chosen for the component deployment). 
* Linux operating system
* Docker Engine
* Docker Compose or Kubernetes (depending on the configuration chosen for the component deployment)
Please note that although Ocean Marketplace is not a core component of our stack but rather an example of what can be achieved with our technology, in this section we included a guide on how to deploy it. 

18
rewards/df-max-out-yield.md
View File

@ -21,13 +21,13 @@ Thus, if you really want to max out your APY:
### Those assets don't sell themselves!
Marketing your assets to buyers is your challenge. Just because you publish them in the Ocean ecosystem doesn't mean that they will sell. It will take real work. Your reward is great APY. It’s incentives all the way down :)
Marketing your assets to buyers is your challenge. Just because you publish them in the Ocean ecosystem doesn't mean that they will sell. It will take real work. Your reward is great APY. Its incentives all the way down 🙂
<figure><img src="../.gitbook/assets/gif/hustlin.gif" alt=""><figcaption></figcaption></figure>
### Measuring Data Farming's Success
**Data Consume Volume (DCV)** is a our term for **the total $ amount spent on purchases of Ocean ecosystem assets**, transaction fees, and more. The higher DCV of Ocean ecosystem assets, then the more OCEAN rewards are distributed to Data Farmers. It's that simple!
**Data Consume Volume (DCV)** is our term for **the total $ amount spent on purchases of Ocean ecosystem assets**, transaction fees, and more. The higher DCV of Ocean ecosystem assets, then the more OCEAN rewards are distributed to Data Farmers. It's that simple!
### How Rewards are Calculated
@ -35,8 +35,8 @@ The Reward Function (RF) governs how active rewards are allocated to Data Farmer
**Rewards are calculated as follows:**
1. Distribute OCEAN across each asset **based on rank**: highest-DCV asset gets most OCEAN, etc.
2. For each asset and each veOCEAN holder: If the holder is a publisher, 2x the effective allocation – Baseline rewards = (% allocation in asset) \* (OCEAN for asset) – Bound rewards to the asset by 125% APY – Bound rewards by asset’s DCV \* 0.1%.
1. Distribute OCEAN across each asset **based on rank**: highest-DCV asset gets the most OCEAN, etc.
2. For each asset and each veOCEAN holder: If the holder is a publisher, 2x the effective allocation – Baseline rewards = (% allocation in asset) \* (OCEAN for an asset) – Bound rewards to the asset by 125% APY – Bound rewards by asset’s DCV \* 0.1%.
For mathematicians and coders, 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/)!
@ -46,11 +46,11 @@ In Data Farming Round 23 Ranked Rewards were introduced to smooth out the reward
**Since rewards are distributed across the Top 100 assets, all data farmers (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 top-end, this helps increase the quality and diversification of inventory.
At the bottom-end, this eliminates some potential free-rider issues and smooths out the reward distribution.
![Ranked Rewards](../.gitbook/assets/rewards/ranked_rewards_study.png)
![Ranked Rewards](../.gitbook/assets/rewards/ranked\_rewards\_study.png)
You can read more about the why, what, and how of Ranked Rewards [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/1HIA2zV8NUPpCELmi2WFwnAbHmFFrcXjNQiCpEqJ2Jdg/).
@ -58,11 +58,11 @@ You can read more about the why, what, and how of Ranked Rewards [in this blog p
Data assets that have veOCEAN allocated towards them get Data Farming active rewards.
The asset may be of any type — dataset, algorithm for Compute-to-Data, or any other Datatoken token-gated system. The asset may be fixed price or free price. If fixed price, any token of exchange is alright (OCEAN, H2O, USDC, etc).
The asset may be of any type — dataset, an algorithm for Compute-to-Data, or any other Datatoken token-gated system. The asset may be fixed price or free price. If fixed price, any token of exchange is alright (OCEAN, H2O, USDC, etc).
To qualify for DF, an asset must also:
* Have been created by Ocean Smart contracts [deployed](https://github.com/oceanprotocol/contracts/blob/v4main/addresses/address.json) by OPF to [production networks](https://docs.oceanprotocol.com/discover/networks)
* Have been created by Ocean Smart contracts [deployed](https://github.com/oceanprotocol/contracts/blob/v4main/addresses/address.json) by OPF to [production networks](../discover/networks/)
* Can’t be in [purgatory](https://github.com/oceanprotocol/list-purgatory/blob/main/policies/README.md)
### A Brief History of Data Farming
@ -76,7 +76,7 @@ Data Farming has evolved over time and will continue to do so as the Emission Cu
10K OCEAN rewards were budgeted per week. Counting started Thu Sep 29, 2022 and ended Oct 27, 2022. Rewards were distributed at the end of every week, for the activity of the previous week. It ran for 4 weeks. The aim was to resume Data Farming along with veOCEAN, test the technology, onboard data publishers, and keep learning.
**DF Beta - Rounds 9-28 (20 wks)**\
Up to 100K OCEAN rewards were budget per week. Counting started Thu Oct 27, 2022 and ended March 15, 2023. It ran for 20 weeks. The aim was to test the effect of larger incentives, support ecosystem participation, while continue refining the underlying technology.
Up to 100K OCEAN rewards were budgeted per week. Counting started Thu Oct 27, 2022, and ended on March 15, 2023. It ran for 20 weeks. The aim was to test the effect of larger incentives, and support ecosystem participation, while continually refining the underlying technology.
**DF Main - Rounds 29-1000+**\
We are now in DF Main which immediately followed the release of DF Beta on Thu Mar 16, 2023. Rewards begin at 150k per week and go to 1.1M OCEAN per week. DF Main emits 503.4M OCEAN worth of rewards and lasts for decades. Expected APY is 125% over many months (once fully ramped), staying generous over the long term.