oh well... the 15º on Saturday doesn't look that bad ;)
btw, does BLURT inherit the 0.02 dust limit from hive... I assume so?! And if yes, does the (virtual) dollar value count or the BLURT estimate?
RE: My Actifit Report Card: April 13 2022
You are viewing a single comment's thread from:
My Actifit Report Card: April 13 2022
Yes. It inherited that minimum payout value (from Steem, actually), and I think it's still set to 0.02 BLURT. That threshold doesn't mean much on Blurt since you don't need all that much power to pass the threshold with a vote.
We're also still on the convergent linear curve, but we modified some of the variables. We changed the content_constant to 1e9 instead of 1e12, and we eliminated the 50 k Rshares dust threshold. The transaction fees pretty much eliminates the need for that part.
The price estimate in USD is done through an API that I built. You might laugh when you hear how I made it. I made a price tracker app in Python that gets the prices from Ionomy, Hive-Engine, and CoinGecko, and it saves it in a JSON file. Then I wrote web server in Go for the API. The web server fetches the prices from the JSON file and serves it to the clients. Hehe!
The API endpoint is here: https://api.blurt.world/price_info
The source code is here: https://gitlab.com/blurt/openblurt/blurt-price-info-api
0.02 BLURT... gotcha! That's what I had suspected and I am glad I can already beat that, too.
That API approach sounds reasonable enough. Capsuling price pulling from the webservice sounds a bit like doing things twice but I can see how that makes error handling external sources and keeping the service up reliable easier, too.