mirror of
https://github.com/oceanprotocol/docs.git
synced 2024-11-26 19:49:26 +01:00
commit
0a30b5bf90
@ -63,10 +63,12 @@ _Rewards are calculated as follows:_
|
|||||||
1. If the holder is a publisher, 2x the effective allocation
|
1. If the holder is a publisher, 2x the effective allocation
|
||||||
1. Baseline rewards = (% allocation in asset) \* (OCEAN for an asset)
|
1. Baseline rewards = (% allocation in asset) \* (OCEAN for an asset)
|
||||||
1. Bound rewards to the asset by 125% APY
|
1. Bound rewards to the asset by 125% APY
|
||||||
1. Bound rewards by asset’s `DCV` \* `DCV_multiplier`.
|
1. Bound rewards by asset’s `DCV` \* (% allocation in asset) \* `DCV_multiplier`.
|
||||||
|
|
||||||
Step 2.4 is to prevent wash consume. `DCV_multiplier` is a function of fees, with a value of 0.201 for Predictoor feeds, and 0.001 for other data assets.
|
Step 2.4 is to prevent wash consume. `DCV_multiplier` is a function of fees, with a value of 0.201 for Predictoor feeds, and 0.001 for other data assets.
|
||||||
|
|
||||||
|
Any OCEAN budgeted for Volume DF that wasn’t rewarded goes back into the DF pot for future DF rounds.
|
||||||
|
|
||||||
The actual code is in [calcrewards.py](https://github.com/oceanprotocol/df-py/blob/main/df_py/volume/calc_rewards.py) in df-py repo.
|
The actual code is in [calcrewards.py](https://github.com/oceanprotocol/df-py/blob/main/df_py/volume/calc_rewards.py) in df-py repo.
|
||||||
|
|
||||||
When DF restarts each Thursday, the global allocation towards each asset resets back to zero and then starts counting up again until the end of the round. After allocating your veOCEAN to different datasets, it will take time for your voting power to be accounted for.
|
When DF restarts each Thursday, the global allocation towards each asset resets back to zero and then starts counting up again until the end of the round. After allocating your veOCEAN to different datasets, it will take time for your voting power to be accounted for.
|
||||||
|
Loading…
Reference in New Issue
Block a user