For those of you who haven't heard - coingecko HBD price feed is a mess, based on tens of dollars in volume from shut down exchange Bittrex and Korean low-volume exchange Upbit. Imagining that yelling in public is the right way to get things done in an open-source ecosystem, I made the previous post, and was completely validated by @crimsonclad - who basically said,
We know. We are working on it. And apps should adjust, just like Eco said.
Okay you can read what she actually said here, but I think that is a good summary. Its the top comment on the previous post.
What's happened since I raised the alarm?
Well, in a way - nothing. The post did not get the attention of any of the devs, but I didn't stop there. I went into PeakD support and tagged them directly, and got an answer and an update from @asgarth.
Its still not as good as I think it can or should be, but something was done! Information is present, even if the (super much) lower volume feed is more prominantely displayed, and the internal robust price is included as an afterthought - something did change. Should I let @asgarth and @jarvie off the hook now?
I also went into the Splinterlands Support site, and I raised a ticket - here is what I told them:
And I got a quick answer back from @grapthar - here is his response:
You might remember from the original post, that @jfang003 was the one who brought to my attention the exploit of converting HBD into Credits when the (fake) price feed was high. This is a really important point, as the Splinterlands community has warred amongst each other about such exploits before.
Its important to note that the real price is always represented by the market with the highest volume. This is the science of markets, its how things work.
I responded to @grapthar with happy noises, and got another positive response, and today the ticket was closed. I think this is likely another success! Although I hope I haven't delayed land any (I haven't right @farpetrad? right?)
No noises have been made about HivePay - aparently owned by @hashkings now. If anyone is using HivePay, or knows someone who does, we need to get some attention about this. The API documentation linked in the first post has everything a developer needs to solve this in a few hours. The situation as it is now WILL lead to a bad experience, either a customer losing money or a business losing money by using/accepting HBD. This is not what we want for our prized stable coin.
@balaz chimed in that Muterra doesn't even use feeds, it just treats HBD like one dollar always. This is another solution, perhaps even more elegant.
Another post?
I have promised to shout about this until it gets fixed. I am not sure I will make another post, but these things are good fresh - to push as hard as we can, exert social pressure quickly and make the necessary changes. This one is particularily easy - there is no excuse. Plus I got 39 comments on my last post - what engagement!
HivePay could be an ecosystem leader, a 'killer' payment dApp for the HIVE ecosystem. Isn't that what they want? If you know @hashkings, the people behind it, or how to get ahold of them, please let me know - and help me succeed - let's get this fixed NOW.