e.g. to @sbi4 ? How much HP for how many HSBI? !wine
You are viewing a single comment's thread from:
Sort: Trending
You have to delegato to @steembasicincome for bonus units. We don't monitor delegation changes on the other accounts except for a couple people that delegate >5200 for weekly payments.
The ratio is 1 bonus unit for each 2 HP delegation. We recommend you have enough HP to consistently deliver 0.02 on a comment before you delegate to any third party unless you are rarely curating.
Please explain why the structure of the HSBI vote values don't total to 100% according to HSBI bots, such as this. 😅
That's a very old functionality that we thought would provide users with more insight into their votes, but it has never been accurate.
Originally it had subscription, bonus units, and upvote rewards. It didn't add to 100% because every account starts with enough pending value to receive their first upvote immediately. That was added as a fourth section, but there is no field in the DB that stores that value. Users that transferred their units and pending value across from Steem would also have a boost in that category.
It should just be 100% less the other three values, but in any case... most people don't have bonus units, and there is no reward for upvoting for the last four years or more. It doesn't provide much in the way of information; people mostly ignore it, and it hasn't been a priority to fix.
Maybe you should just add an "other sources" field on the HSBI bot's response so that the total percentage will always be 100%. 😅
Thanks for the response! 😀 I believe @svanbo would find your official answer useful. 😎
You already got an official answer there. 😎 !wine
However, I haven't checked if delegating Hive Power with a fractional part (such as 1.500 HP) will provide you with 0.75 bonus HSBI units, or if it will be rounded down to the lower whole number. 🤔😅
There are no partial units, so it always rounds down to the lower whole number.
I saw it, but I don't understand the "weekly payments" in "a couple people that delegate >5200 for weekly payments." !wine
Maybe he means that the other HSBI Hive accounts (that isn't steembasicincome) aren't monitored for Hive Power delegations (which will award bonus HSBI units) except for those who have delegated huge amounts (more than 5,200 HP). 🤔 !LUV
Maybe if you want to delegate to a random HSBI bot, try to make it more than 5,200 HP. 😆😅 !WEED
Don't delegate to random HSBI bots without discussing it with me first. The bot only checks delegation on the main account, and I look at the delegating accounts to confirm delegation is unchanged each week for the negotiated leases, not at the accounts they delegate to.
If you delegate to any HSBI account other than @steembasicincome, nobody will ever see it and you will get no direct benefit, unless you plan to delegate more than 5200 and discuss it with me first.
It's not like I or @svanbo has more than 5,200 Hive Power to delegate right now to the other HSBI bots. 😅
Anyway, thanks for the information about why we need to delegate to the steembasicincome Hive account for bonus HSBI units (unless we have more than 5,200 Hive Power and prior arrangements have been made)! 🤓
I don't know why I would delegate to other accounts than the main account for the same purpose? I'll delegate some more to @steembasicincome as soon as I upvote in 12 days... !wine
It's because I saw other HSBI bots curating on behalf of the main HSBI curation account (steembasicincome), until the HSBI founder strongly advised not to do so without prior arrangements. 🤯😅 !PIZZA !wine
I assume that the main steembasicincome bot can already do the job of curating for Hive users with HSBI shares even without the HSBI curation alt accounts. 🤔🤓 !LUV
The setup made more sense when it was believed that HIVE would eventually have a high market price. Everyone is used to there being a maximum deliverable upvote (100% upvote) but there is also a minimum (0.01% upvote). We had some concerns that as Hive SBI grew, the minimum upvote value would exceed the desired 0.021 threshold and create weird issues. That has never happened because of HIVE underperformance, but it could still happen as HP grows.
There are also edge considerations around blockchain behavior. It was not possible for an account to upvote more than one post per block (I'm unsure whether this technical limitation still exists), so having multiple voting accounts bypassed this restriction. In practice we self-throttle so that RPC nodes don't cut off our access, so we rarely deliver more than a single upvote per block anyway. Being fast is less important with straight-line curation for the first 24 hour of each post.
Finally, there are legacy reasons. When the program was first begun, we did not have our own voting bot and we were using third party software that had a limitation of 100 target accounts scheduled for each voter. We were required to scale up to 10 voting accounts as we reached nearly 1000 accounts on our vote list before we were able to get out our initial full automation release at about the 8-month mark. When we did release full automation, we chose to keep all 10 accounts and scale our HP across them for the reasons detailed above.
@svanbo!
@savvytester passed you the virtual joint!If you do not want to receive these comments, please reply with !STOP