RE: Steem Pressure #7: Go Fork Yourself. Step by step guide to building and setting up a MIRA powered HF21-ready Steem consensus node. by gtg

View this thread on: hive.blog | peakd.com | ecency.com

Viewing a response to: @anthonyadavisii/anthonyadavisii-re-gtg-steem-pressure-7-go-fork-yourself-step-by-step-guide-to-building-and-setting-up-a-mira-powered-hf21-ready-steem-consensus-node-20190816t190137243z

steem-pressure · @gtg · Aug 16 '19

While you can use it to perform some calls, LOW_MEMORY_NODE might not be enough for you. Please note that `rewards_api` is for testing purpose only, and explicitly said that it's not meant for use in production.

properties (22)

`author`	gtg
`permlink`	pwcisp
`category`	steem-pressure
`json_metadata`	{"tags":["steem-pressure"],"app":"steemit/0.1"}
`created`	2019-08-16 20:12:27
`last_update`	2019-08-16 20:12:27
`depth`	2
`children`	2
`last_payout`	2019-08-23 20:12:27
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.000 HBD
`curator_payout_value`	0.000 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	211
`author_reputation`	461,803,244,824,447
`root_title`	"Steem Pressure #7: Go Fork Yourself. Step by step guide to building and setting up a MIRA powered HF21-ready Steem consensus node."
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	89,609,446
`net_rshares`	0

@anthonyadavisii · Aug 16 '19

I may be getting the API needed confused in that case.

Our bot does approximate flag rshares to SBD conversions using methods of the Beem Steem class for it's voting.

Looks like the method uses get_sbd_per_rshares which calls get_reward_fund. That uses the database API if I am understanding correctly.

That should be fine, right?

Posted using [Partiko Android](https://partiko.app/referral/anthonyadavisii)

👍 ismailkah

`author`	anthonyadavisii
`permlink`	anthonyadavisii-re-gtg-pwcisp-20190816t204547531z
`category`	steem-pressure
`json_metadata`	{"app":"partiko","client":"android"}
`created`	2019-08-16 20:45:48
`last_update`	2019-08-16 20:45:48
`depth`	3
`children`	1
`last_payout`	2019-08-23 20:45:48
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.000 HBD
`curator_payout_value`	0.000 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	411
`author_reputation`	212,565,147,344,592
`root_title`	"Steem Pressure #7: Go Fork Yourself. Step by step guide to building and setting up a MIRA powered HF21-ready Steem consensus node."
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	89,610,246
`net_rshares`	5,343,532,197
`author_curate_reward`	""

properties (23)vote details (1)

voter	weight	wgt%	rshares	pct	time
ismailkah	0 B		5,343,532,197	25%

@netuoso · Aug 16 '19

$0.07

The rewards_api is something brand new that was used to attempt to model the changes to rewards after HF21.

What you are referring to is found in `condenser_api` which the the api you will use the majority of the time. Sometimes there is the need for `database_api` but, neither of those are explicitly declared in the config.

👍 gtg, anthonyadavisii

`author`	netuoso
`permlink`	pwcm40
`category`	steem-pressure
`json_metadata`	{"tags":["steem-pressure"],"app":"steemit/0.1"}
`created`	2019-08-16 21:24:00
`last_update`	2019-08-16 21:24:00
`depth`	4
`children`	0
`last_payout`	2019-08-23 21:24:00
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.050 HBD
`curator_payout_value`	0.016 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	327
`author_reputation`	151,901,967,807,285
`root_title`	"Steem Pressure #7: Go Fork Yourself. Step by step guide to building and setting up a MIRA powered HF21-ready Steem consensus node."
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	89,611,108
`net_rshares`	201,944,673,087
`author_curate_reward`	""

properties (23)vote details (2)

voter	weight	wgt%	rshares	pct	time
gtg	0 B		141,466,770,508	1%
anthonyadavisii	0 B		60,477,902,579	35%