Difficult times, but it will pass soon. I just wanted to sketch out how some of the Blurt blockchain numbers are playing out, as some people have mentioned them.
The reward pool is very resilient; assuming the chain works, the rpool cannot break, either upwards or downwards. We now see the rpool growing, and it currently stands at 1.50 million BLURT. Even with the new economic system, I expected the rpool to double from what it was previously, to possibly around 2 million BLURT.
The increase we see in pending rewards is not just due to the increasing rpool but also the decreasing recent-claims, which are a 15-day forward measure of voting activity. Such claims can decrease thereby making each vote more valuable.
We must assume that HF5 will behave the same way as HF4 in that posts that are due a payout are paid out using the new formula - and not the formula when they were first published. It will thus be immediately obvious whether our fix has worked.
One thing to bear in mind is that the actual payouts that will (hopefully) be seen may be different to what the front-ends currently show. As I mentioned before, those front-ends will need to change their internal algorithms.
The blockchain itself does not store "pending rewards"; those are calculated right at the end at the point of payout. What it does store is rshares and curation-weights and claims. What the front-ends do is simulate the final payout process so that humans have an estimate of that final payout - but if their formulas are different to what is on the chain then their estimate will be wrong. Your wallet is always correct!
One thing that is unrelated to the economic formulas yet vital to the well-being of the chain is the number of RPC nodes. It is very important Blurt has more than one RPC node. When you see front-ends going down during a HF, this is not a glitch in the HF process itself, but that the RPC nodes need to also update and replay. This is usually done in sequence, so that at least one node is working at all times. So, one aspect that has held up HF5 is the setup and stability of new nodes.
This last paragraph proved to be quite the prophecy - as I couldn't post when I went to try!
This is really well written and a clear explanation for those who are wondering what is going. Some think there is something wrong with Blurt, but it seems that everything is in order and I'm glad Blurt has witnesses to support the RPC nodes necessary.
I also like this sentence for clarification:
"Your Wallet is always correct!"
This post is very important and has come just in time, many people are looking at astronomical votes and for a moment they think they will get all this in their wallet, we are seeing wrong amounts that will be updated in the near future.
Yes, thank you! I forgot to add, that post was written minutes before the recent front-end problems! lol.
And yes, we've gone from gloom to joy, but I need to put some reality back into view so users don't then start complaining, "how did my payout shrink?!" It didn't "shrink", it was just being inflated by a magnifying lens! ;-)
Thank you for transmitting the information so that we can replicate it to the general public, who are sometimes lost because they do not know what is going on.
the current main rpc config is:
You shouldn't have rpc issues, and if you do, you should screenshot the hell out of them please.
The actual pending payout value should be accurate since that value comes from the RPC node. The individual votes are just stored with rshares and weight values, so you have to do the calculations on the frontend to show the values of those.
For example, if I ask the RPC for my vote on this post, this is what it returns:
But when I retrieve a comment operation form the RPC node (posts are comment operations), there is a field called "pending_payout_value" and it looks like this:
The front end would use that information to display the payout value as 168.816 BLURT.
So you are correct about the votes, but not 100% correct about the frontend calculating the pending payout. That comes from the RPC node. So I'm pretty certain it should be accurate since it uses the same formula as the one that will be used when the payout occurs.
OK thanks. Now I wonder why I've seen some UIs actually code the calculation (as I said) rather than calling the API - perhaps it is to reduce such API calls as a page full of votes could be 100s of data points.
At some point, we may need an API def page or section in the wiki - just as the other chains have, although I see the number of APIs has grown hugely there.
Now I also wonder where pending_payout_value is within the code! lol
Am I understanding correctly that the fork is now live and payouts will resume?
I've been hawking the Gitlab and it appeared Jacobs last several pushes either failed or were canceled (around 16 and 17 hours ago respectively).
Also, was curious if Julian Gonzalez had a Blurt account and a witness server. I noticed they have been working hard on this as well and would love to show appreciation. I saw the acknowledgement of your assessment the issue involved integers. A huge thank you to you for looking through and having the understanding of both math and code to see the issue.
Will be curious to see what my first payout will actually be, as you caution they are overinflated based on old math. Will surely take the sting a little out of losing some of what appeared to be my largest payout posts in the last week. But at least for appearances it looked like I was a Blurt all-star rocking those large stake account votes. :D
Yes, I tracked down the error, rewrote the code to avoid the integer-maths zero-calc, then @jga OK'd the maths and inserted the code into the chain so that it would activate properly at the next HF. The last step is to merge those changes with the existing code.
Is all fiddly so that when a chain replays it always has the same history as before, and the forks are landmarks at which some rules change, but not before then!
So will we have to wait another 7 days before any rewards ? Longer ?
I think that whatever post are still pending payout at the time the fork goes live will get their payout as they should. So let's hope the fork goes live sooner than later.
yes
where does it say that?
No where... I am just trying to figure out when rewards will start to be sent.
I am also a victim. Even after showing the percentage of reward in some of my posts, it is finally showing zero. Again, we have all received many awards before some tags but now no one is getting such awards anymore. Finally I hope all of problems we solve soon.
Many thanks. I hope I can relax a bit about the economics and look at updating the information about Blurt, such as the wiki, FAQ, whitepaper etc, so that new users can find such info without searching for posts.
mmm... the comment was edited, so my reply now makes no sense!
I'm not sure what you're referring to - past present or future - you should now be seeing both author and curation rewards.
I don't know what you men by "tags" - is there a "community tag" that is no longer working? If so then please let mods know in Discord, or even reply here.
Congratulations, your post has been curated by @r2cornell
Also, find us on Discord (https://discord.gg/BAn2amn)
https://discord.gg/BAn2amn