Steem: `get_content` and `get_blog` return difference `pending_payout_value` for the same post

Created on 19 Sep 2019  路  3Comments  路  Source: steemit/steem

According to my understanding, no matter how we obtain it, the pending_payout_value for the specified post should be consistent.

But when I tried to get pending_payout_value for one of my posts, I got the difference results.

Using get_content:

{"jsonrpc": "2.0", "method": "condenser_api.get_content", "params": ["oflyhigh", "ufo-2019-09-18"], "id": 1}
image

Using get_blog:

{"jsonrpc": "2.0", "method": "condenser_api.get_blog", "params": ["oflyhigh", 1787, 1], "id": 1}
image

There were no new upvote or downvote changes to net_rshares during my tests, and the reward fund pool did not change significantly.

Most helpful comment

Payouts are calculated on the fly based on the rewards pool, which changes every block. So it's quite possible the same call to the same node gives a slightly different result every few seconds.

Also, if you're using api.steemit.com, the get_blog call would be routed to hivemind, which caches the pending payout at the time of the last vote/edit/comment/payout. get_content on the same endpoint goes to steemd, which provides the most accurate estimate.

However, hivemind always updates posts after they are paid out, so the result for posts older than 7 days should be identical.

All 3 comments

What about price feed median? That affects as well

Payouts are calculated on the fly based on the rewards pool, which changes every block. So it's quite possible the same call to the same node gives a slightly different result every few seconds.

Also, if you're using api.steemit.com, the get_blog call would be routed to hivemind, which caches the pending payout at the time of the last vote/edit/comment/payout. get_content on the same endpoint goes to steemd, which provides the most accurate estimate.

However, hivemind always updates posts after they are paid out, so the result for posts older than 7 days should be identical.

Out steemd nodes in production do not the follow api, so I agree that it is probably a slight discrepancy between steemd and Hivemind. I am going to close this issue. If you run across new evidence that supports there is a problem in condenser_api, please create a new issue with the evidence.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ebonsi picture ebonsi  路  7Comments

lukestokes picture lukestokes  路  5Comments

williambanks picture williambanks  路  4Comments

mvandeberg picture mvandeberg  路  4Comments

porozhnyy picture porozhnyy  路  4Comments