You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for configuration.minimum_vote_threshold, we have a value in rshares and we deliver votes only when pending_balance * 3 > minimum_vote_threshold.
We also use this value downstream in API to calculate pending upvote values.
Approximate value is 0.02 (based on minimum payable post threshold on Hive)
In practice, to update this value, I check a voting account weekly (or so) on hiveblockexplorer and identify the lowest % upvotes I can see and compare their value to the 0.02 threshold. I actually target 0.021. For example, if lowest upvote I find has a value estimate of 0.017 then I take 0.017 / 0.021 = 0.8095 and then minimum upvote value by 0.8095 to derive the new minimum upvote value. This subsequently flows into the downstream calculations.
We can automate this by using the logic that front ends use to estimate upvote values (calculate estimated value of minimum upvote, compare to 0.021, and set new minimum upvote accordingly)
Automation will increase the accuracy of downstream value estimates by keeping minimum upvote values in closer alignment with changes in HIVE price
The text was updated successfully, but these errors were encountered:
for configuration.minimum_vote_threshold, we have a value in rshares and we deliver votes only when pending_balance * 3 > minimum_vote_threshold.
We also use this value downstream in API to calculate pending upvote values.
Approximate value is 0.02 (based on minimum payable post threshold on Hive)
In practice, to update this value, I check a voting account weekly (or so) on hiveblockexplorer and identify the lowest % upvotes I can see and compare their value to the 0.02 threshold. I actually target 0.021. For example, if lowest upvote I find has a value estimate of 0.017 then I take 0.017 / 0.021 = 0.8095 and then minimum upvote value by 0.8095 to derive the new minimum upvote value. This subsequently flows into the downstream calculations.
We can automate this by using the logic that front ends use to estimate upvote values (calculate estimated value of minimum upvote, compare to 0.021, and set new minimum upvote accordingly)
Automation will increase the accuracy of downstream value estimates by keeping minimum upvote values in closer alignment with changes in HIVE price
The text was updated successfully, but these errors were encountered: