All right Hivizens, listen up!

in #leodex7 months ago

It has come to my attention that it has been made possible to set your voting strength for the various hive-engine coins in the leodex.io user interface.

One clicks on the the rewards tab, clicks the lightning bolt icon, sets the multiplier, and viola!, manageable h-e voting power.

image.png

I usually vote with 20 and 25% votes, so I figure a 5x multiplier will do the trick.

Luckily, leodex includes a scale so you can keep tabs on your multiplier and adjust accordingly.

image.png

Other than having to do each coin individually, that is a rockin' deal.

All hail, Leodex!!

crap pyramid.jfif

Sort:  

I find myself using at least 8 different accounts instead.

Yeah, I can barely keep up with the two I use.
It seems to be working just fine.

It's the curse of the tribes.

I feel your pain. Best of luck. Hope LeoDex starts including all the coins at some point.

It does get pretty annoying, but it is what it is.

Ohh thanks so much for this initiative. I really didn't have an idea about the keodex before now you brought it to our lamplight.

I just found out about it, too, it's been open at least 3 months.
It is doing wonders on not wasting my h-e voting power.

Ohhh that's nice I will low to learn about it

Congratulations @antisocialist! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s) :

You distributed more than 22000 upvotes.
Your next target is to reach 23000 upvotes.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

Check out the last post from @hivebuzz:

False-Positive phishing alert reported by antivirus software
Feedback from the May 1st Hive Power Up Day
Support the HiveBuzz project. Vote for our proposal!

Yeah, the rewards claim for h-e tokens is a black hole.
Some sites claim once a day, others are manual, none seem to line up on rewards.
I'm gonna presume that it is in the observer, or the various api's lag, and not nefarious.