Currently, the post value pop-up in condenser displays unrealistic estimates when the price of STEEM is below the haircut price. To improve accuracy, the displayed value and pending STEEM/SP count should be multiplied by the haircut ratio (i.e. the median witness price of STEEM / the haircut price) when the sbd_print_rate is 0.
Here are the values to be updated.
The sbd_print_rate can be retrieved from condenser_api.get_dynamic_global_properties.
Instead of another network call, the haircut price can also be obtained from global properties, as follows:
current_sbd_supply / ( virtual_supply - current_supply )
The median witness price of STEEM can be retrieved and calculated from condenser_api.get_feed_history.
These values should not be adjusted if the sbd_print_rate is above 0, and they only need to be collected once per hour.
This update needs to be done:
- In feeds
- In top-level posts when the post is open
- Throughout the reply thread when the post is open
- In blog/posts/comments/replies under a profile
- Anywhere else that can be identified
Currently, the post value pop-up in condenser displays unrealistic estimates when the price of STEEM is below the haircut price. To improve accuracy, the displayed value and pending STEEM/SP count should be multiplied by the haircut ratio (i.e. the median witness price of STEEM / the haircut price) when the
sbd_print_rateis 0.Here are the values to be updated.
The
sbd_print_ratecan be retrieved from condenser_api.get_dynamic_global_properties.Instead of another network call, the haircut price can also be obtained from global properties, as follows:
current_sbd_supply / ( virtual_supply - current_supply )The median witness price of STEEM can be retrieved and calculated from condenser_api.get_feed_history.
These values should not be adjusted if the
sbd_print_rateis above 0, and they only need to be collected once per hour.This update needs to be done: