RE: How @supercomputing was able to dominate the mining queue and how the bug was fixed. by originate

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

Viewing a response to: @arhag/how-supercomputing-was-able-to-dominate-the-mining-queue-and-how-the-bug-was-fixed

steem · @originate · Aug 15 '16

Great job @arhag on the patch!  Also thank you @alphabeta who I noticed was active in promoting the issue https://steemit.com/steemit/@alphabeta/warning-supercomputing-has-taking-over-witness-queue  

So to confirm:

<em>steem/programs/steemd/witness_node_data_dir/config.ini</em>

no longer needs the active key for any specified miners?  I had actually wondered  why that ever was required since steemd is already in the background.

👍 kodachrome, newbie10

`author`	originate
`permlink`	re-arhag-how-supercomputing-was-able-to-dominate-the-mining-queue-and-how-the-bug-was-fixed-20160815t223842785z
`category`	steem
`json_metadata`	{"tags":["steem"]}
`created`	2016-08-15 22:38:42
`last_update`	2016-08-15 22:38:42
`depth`	1
`children`	2
`last_payout`	2016-09-16 02:57:09
`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`	434
`author_reputation`	175,421,925,272,702
`root_title`	"How @supercomputing was able to dominate the mining queue and how the bug was fixed."
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	825,107
`net_rshares`	11,246,543,898
`author_curate_reward`	""

properties (23)vote details (2)

voter	weight	wgt%	rshares	pct	time
kodachrome	0 B		6,253,300,009	100%
newbie10	0 B		4,993,243,889	100%

@arhag · Aug 15 '16 (edited)

You do still need the active key as usual. It is necessary to sign the final transaction that holds the PoW you submit to the blockchain in order to get into the miner queue. The reason for this signature in even the new mining algorithm is so that someone cannot force an account they do not control into the mining queue without the account owner's permission.

👍 fury

`author`	arhag
`permlink`	re-originate-re-arhag-how-supercomputing-was-able-to-dominate-the-mining-queue-and-how-the-bug-was-fixed-20160815t230605060z
`category`	steem
`json_metadata`	{"tags":["steem"]}
`created`	2016-08-15 23:06:06
`last_update`	2016-08-15 23:07:54
`depth`	2
`children`	0
`last_payout`	2016-09-16 02:57:09
`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`	362
`author_reputation`	52,490,827,205,383
`root_title`	"How @supercomputing was able to dominate the mining queue and how the bug was fixed."
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	825,481
`net_rshares`	17,391,552,604
`author_curate_reward`	""

properties (23)vote details (1)

voter	weight	wgt%	rshares	pct	time
fury	0 B		17,391,552,604	100%

@kodachrome · Aug 15 '16

Good work all. I would also like to know however if we are meant to be making changes to our mining configs, especially those with multiple miners?

properties (22)