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

Fix #1371: [DF] In Volume DF, all 20 prediction feeds are worth allocating to (not 18)

This commit is contained in:
Trent McConaghy 2023-11-13 08:44:51 +01:00 committed by GitHub
parent dc2a38f407
commit fa0bf18031
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -59,7 +59,7 @@ Predictoor DF makes [Active DF](../data-farming/activedf.md) more attractive, an
**Predictoor DF makes Volume DF more attractive than status quo**, because the volume-based bounds on weekly rewards trends tend to be markedly higher for prediction feeds. (The Appendix has details.)
**Curating is straightforward.** Ocean assets with high DCV are easy to identify: it's the 20 OPF-published prediction feeds (minus the two free ones). This makes the choice of veOCEAN allocation easy: point to those 20-2=18 assets. (Only OPF-published feeds are eligible.)
**Curating is straightforward.** Ocean assets with high DCV are easy to identify: it's the 20 OPF-published prediction feeds. This makes the choice of veOCEAN allocation easy: point to those 20 assets [1].
**Doing Volume DF gives Passive DF rewards too**, of course.
@ -86,3 +86,8 @@ Predictoor DF makes both `DCV` and `m` higher!
Therefore `DCV_bound` is higher. Specifically: `DCV_bound = 37000 * (0.001 + 0.20) = 7437 OCEAN`. In other words, at least 7437 OCEAN is available for Volume DF in any given week.
## Notes
[1] The BTC/USDT 5m and 1h feeds follow the same Volume DF mechanics as the other feeds, despite being free on the webapp.
Details: the BTC feeds _are_ priced at the smart contract level. The webapp receives datatokens for those feeds and makes the prediction values public. Because the BTC feeds _are_ priced, then: their DCV is non-negligible; allocating veOCEAN to them makes sense; and Volume DF rewards accrue to them as well.