Quote from: abitmore on April 10, 2016, 10:19:35 AM

Quote from: Grandpa Jones on April 10, 2016, 01:53:13 AM

Quote from: thereverseflash on March 25, 2016, 12:40:56 PM

Quote from: SalimNagamato on March 25, 2016, 07:51:08 AM

is it ok to use the same WIF key for few mining accounts?
and to use the same accountname in --witness and --miner ?

1. only use --witness on one machine or you will double produce blocks and lose your account
2. you can use the same key so long as you mine on the same computer in the same process

By "lose" and account, does that mean you lose the ability to mine with it or the balance too?

How can you know which accounts are "lost"?

By "double producing" the nodes are making forks.

I wonder how the account will get "lost" as well..

In order to ban an account, nodes (at least block producers) on the major (longest) chain need to know things happened on a minor chain (at least who was forking), then refuses any transaction signed by that account. If this is the case, the "bad one" will lose everything, STEEMS, VESTS, account name etc. I don't know how to automate this right now, since forking can be caused by accident, IMO it's hard to identify automatically & accurately. On the other hand, it could be easier to be identified manually, although still need some efforts. Then comes another question: how to convince the producers to ban an account. In the mining phrase, if enough hashing power is making forks, it will be troublesome. In the voting phrase, the major VESTS holders (atm it's steemit) decide the block produces, so it's possible for them to do anything. Just thinking out loud..

Code:

/**
* This operation is used to report a miner who signs two blocks
* at the same time. To be valid, the violation must be reported within
* STEEMIT_MAX_WITNESSES blocks of the head block (1 round) and the
* producer must be in the ACTIVE witness set.
*
* Users not in the ACTIVE witness set should not have to worry about their
* key getting compromised and being used to produced multiple blocks so
* the attacker can report it and steel their vesting steem.
*
* The result of the operation is to transfer the full VESTING STEEM balance
* of the block producer to the reporter.
*/
struct report_over_production_operation : public base_operation {
string reporter;
signed_block_header first_block;
signed_block_header second_block;

void validate()const;
};