What does the Hive Payout Rewards actually indicate?
There is probably a post somewhere that explains it better, but for now I want to focus on the confusing part. I am talking about the Hive Payouts for posts and comments. When you make a post you can see the potential and realized payouts for posts. We know that the rewards are split up 50/50 on Hive: the author and the curators both get half of the payouts. So far so good. It's also important to know that Hive's inflation of around 6-7% per year makes up the reward pool. This means that the more people blog or comment, the less everyone gets, since more people are tapping into the reward pool. It is actually a really great idea to produce content when Hive's price is low, since price and activity on chain are directly correlated. In other words, you will receive a greater proportion of the reward pool when Hive's price is low since there are less people getting rewards.
Now the confusing part. When you look at your blog you can see the potential payout for posts less than 7 days old (top example) and for posts that are older (bottom example).
This is actually rather clear: for me this would mean that the post "BTC on Track to 35-48k" would receive 6.266 Hive with half of that going to me as the author. For the post "Last chance for HIVE/BTC" I can see the total Hive rewards was 7.832 with 3.928 going to me as the author.
But when I check my wallet this does not add up at all. The rewards that I (and everyone) is receiving is much higher than that.
You can see that the rewards are around 209%-215% higher than what is shown in the preview! I am sure that there is a good answer for this, but the question I have: why isn't the potential and actual payout displayed to more closely represent the actual payout?
Looking at the payout value on posts does not mean anything (again, I might be wrong). The only thing that you could do is add around 50% to that number which would give you around the actual realized payout.
So why do frontends display the payout so confusingly? @peakd @ecency