Curators match bot - Waiviogit/waivio GitHub Wiki

Main task #2197

Curators match bot repeats the curators' voices with a specified coefficient (from 1% to 10 000%).

By default, the bot repeats only positive votes, but if the user specifies (ticks the check box), then downvotes are repeated with the same coefficient. In this case, the table uses the ± symbol in front of Vote ratio to indicate that negative votes are also repeated.

For each curator, min Voting Power is set (upvote / downvote mana).

If the estimated value of the vote is less than 0.01 HBD, then such a vote will not be played.

Authorization like a sponsored match bot https://github.com/Waiviogit/waivio/wiki/Match-bot-(Sponsor)#how-to-become-a-match-bot

1. User adds an curator
2. The curator puts likes and dislikes.
3. User's like and dislikes have appeared on the post automatically.

• "Authorize now" changes to "Remove authorization" in AUTH_BLOCK, if bot is active.

• after adding a curator, a notification of success appears ("Curator was successfully added"), and the author appears in the list without reloading the page;
• after update a rule, a notification of success appears ("Curator was successfully updated"), and the author appears in the list without reloading the page;
• immediately after adding an author, the checkbox is active, the rule is activated.

https://www.notion.so/Research-2e1a84d2ab3f80988108cefc04f19bbf

It turns out that curation rewards on HIVE depend on the voting time via vote_weight.

• First 24 hours (early_voting_seconds) — weight is 100%
• Next 48 hours (mid_voting_seconds) — weight is divided by 2
• Up to day 7 — weight is divided by 8

A post receives 10 HBD in total rewards.

• 50% (5 HBD) goes to curators
• 50% (5 HBD) goes to the author

Your vote_weight after division by 8 = X
Total total_vote_weight of all votes = Y

Your share of the curation reward:

(5 HBD * X) / Y

The author always receives their 5 HBD, regardless of when you voted.

If you vote after 72 hours, your vote_weight is divided by 8:

// hive_evaluator.cpp Lines 2080–2083
if( _seconds < ( dgpo.early_voting_seconds + dgpo.mid_voting_seconds ) )
  vote_weight /= phase_1_factor;
else
  vote_weight /= phase_2_factor;

• Your weight in total_vote_weight becomes smaller
• Your share of the curation reward decreases
• The remaining reward is redistributed among other curators
  (especially those who voted earlier)

Total curation reward: 10 HBD

Early curator

• vote_weight = 1000
• total_vote_weight = 2000

Reward:

(10 * 1000) / 2000 = 5 HBD

You (late vote)

• vote_weight = 1000 / 8 = 125
• total_vote_weight = 2000 + 125 = 2125

Reward:

(10 * 125) / 2125 = 0.588 HBD

If you had voted early

(10 * 1000) / 3000 = 3.33 HBD

With late voting:

• Your reward decreases
• Early curators gain a relatively larger share

1. Competition With Other Posts If multiple posts are cashed out at the same time, total_claims increases, and your reward share decreases.

2. Different rshares If posts have different rshares (even with 100% vote weight), rewards differ due to the non-linear reward curve.

• No explicit time-based penalties
• If non-linear parameters are used (e.g. 0.5), early votes gain more weight due to marginal calculations, not time coefficients

On WAIV

curationRewardCurveParameter = 1

This is a linear function, meaning:

It does not matter when you vote — first or last curator, the curation reward will be the same.

• [Bots / Curator] there were 3 accounts that repeated coffee.time's votes, but only shoppingguide voted. VP on bookguide and localguide 100%. #6253
• Check the engine of the node for lags; if it lags behind by more than 100 blocks, do not request data from it. #6574
• Should work with guest users. #7033
• Add hasMore. #7033
• [curators / vote] Add the ability to choose a vote option as a radio button. Add new absolute type. #7913
• [match bot / curator] Add ability to vote in the last block (before post payout) for curator bot. #7915 #7916