-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HIP38: Validator Oracles #282
Comments
@cvolkernick would you be willing to quick present & field questions about your HIP on this week's community call? Weds @ noon ET |
Sure thing. |
I am curious as to how the conversation above went. I'm currently writing an overview of this HIP and my immediate thought is that this proposal cannot move forward. Whether there is a fixed number of validators added as oracles (either by election or something else) or an everyone-can-opt-in oracle pool, this would put way too much power in the hands of large validator pools. According to the current algo for determining price, large validator pools could easily manipulate the oracle price by submitting inaccurate prices. My understanding is that this proposal does not deal with the speed at which these price changes are calculated (every 10 blocks) but rather the accuracy of the median price that ends up getting set. It's understood that if we had, say, 1000 oracles that we'd probably end up with a more precise number when taking the median but I can't intuit how far off you currently think we might be or why this is important. Running such a simulation to prove your case would probably require implementing multiple different price discovery methods so as to not bias your results. I could actually see a case for increasing the update frequency or slowly expanding the # of anonymous oracles but it's not clear to me what that case currently is or the disadvantages of the existing approach. |
I also don't disagree with you that there is a more root problem of the validator pool being too much of a walled garden. I've written previous HIPs on this but basically got a general response of "life isn't fair" non-rebuttal. |
@cvolkernick any updates on this proposal? Have heard some fun ideas for things we could do in this vein, although I don't know if they'd fit into the current proposal |
From the sound of it the community felt like this was not something that was a high-priority for the time being, and I don't necessarily disagree with that -- so might be best to put on ice until more pressing issues are resolved. Thank you @jamiew |
Info
#hip-38-validator-oracles
on https://discord.gg/heliumRendered view
https://github.com/helium/HIP/blob/master/0038-validator-oracles.md
Summary
From Helium Docs:
This HIP proposes not only changing this number, but also expanding the pool of those who are able to make submissions. It proposes empowering any staked validators with the existing
price_oracle_submission
& allowing them to commit price oracle submissions as chain-blessed Oracles.The text was updated successfully, but these errors were encountered: