BYTE Token Curation Explained

A request was made for a post explaining BYTE token curation. Hopefully this will be informative. If I miss anything please feel free to ask in a reply to this post.

BYTE is similar to other Hive-Engine tokens. There are at least two key differences though:

1. 8 day recharge for BYTE voting power from 0% to 100%
2. You can't upvote in fractions of a BYTE. BYTE has zero precision so there's no decimal point after a BYTE amount value

To be eligible for BYTE reward a post must have at least one of the following tags: #hive-188262, #learntocode, #hardware, #software, or #dev. If you have staked BYTE and you upvote a post without any of those tags there will be no BYTE reward for the curation of that post.

The amount of BYTE reward depends on the amount of BYTE staked by the curator, the upvote percentage given by the curator, and the amount of BYTE voting power the curator has at the moment of the upvote. BYTE voting power is very similar to Hive Power. If you use up all of your BYTE voting power making many upvotes in a short amount of time, it takes 8 days to recharge from 0% to 100%. Each upvote consumes some of your BYTE voting power. At 100% BYTE voting power with a 100% upvote 2% of your BYTE voting power would be consumed.

I guess eventually we'll need a BYTE upvote calculator. That will be on the list for future projects.

BYTE reward is a 50%/50% split. The upvoting curator and the post or reply author both get BYTE. The user that has staked BYTE and upvotes the content gets half of the reward with the other half going to the creator of the content being upvoted.

Image Source: Stable Diffusion