[suggestion] real total payout or beneficiary payout field in a post

[economicstudio]

In the Steem blockchain, currently, payout related fields are

• total_payout_value : author payout (really terrible name, which leads to a bug like https://github.com/steemit/condenser/issues/3450. Everybody may think this is author + curator payout, but this is author only, too late to change though.)
• curator_payout_value : curator payout

This is normally fine, but there is no easy way to know the real total payout amount when there are beneficiaries. For instance, when beneficiary is set to 100%, `total_payout_value` (author payout again!) is set to zero! This itself is fine, but then to know the **"real total"** payout, one may need to query benefactor reward which will be very inefficient.

There are several use cases of high percentage of beneficiaries e.g., fund SPS instead of declining the reward: https://github.com/steemit/condenser/issues/3447 Many dapps are using beneficiaries and there are many possibility with beneficiaries.

In such case, it'd be great if UI can shows the real total payout value first and the details are shown with mouseover or click.

Mockups / Examples

There should be additional fields in a post

• either real_total_payout_value: author+curator+beneficiaries payout
• or beneficiaries_payout_value: beneficiaries payout (total would be enough, since there is beneficiaries field anyway, so breakdown can be calculated from these two infomation.)

Before

 > Currently, payout info is very inconsistent. While it shows the real total pending (author+curator+beneficiaries), but after payout, it only shows (author+curator). That means, if % of beneficiaries is high, there is a sudden drop after payout on the UI.

After

If the above information is provided by the Steem blockchain, UI can easily show the real total payout for paid out posts too. This is much better in terms of consistency and UX.

Benefits

• Efficient real total payout information query
• Consistent payout info
• Better UX for high beneficiary settings
• More possibility for dapps to use beneficiary