From e71e11b9495282063fc86beecd9c9b94dcbcf3bc Mon Sep 17 00:00:00 2001 From: trentmc Date: Thu, 21 Mar 2024 15:33:54 +0100 Subject: [PATCH] Fix #1430: Update Volume DF based on bug --- data-farming/volumedf.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/data-farming/volumedf.md b/data-farming/volumedf.md index d3de31ad..3d169038 100644 --- a/data-farming/volumedf.md +++ b/data-farming/volumedf.md @@ -63,10 +63,12 @@ _Rewards are calculated as follows:_ 1. If the holder is a publisher, 2x the effective allocation 1. Baseline rewards = (% allocation in asset) \* (OCEAN for an asset) 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. +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. 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.