Page 1 of 2

One Antminer L3+ machine earning more than the other

Posted: Mon Jan 01, 2018 2:57 pm
by letitbegood
Hi, I have 2 Antminer L3+ machines mining with Prohashing. The first one I set up about 2 1/2 months ago and the second one about 8-9 days ago. Over the last week, the first machine has been consistently earning around $4 USD more per day than the second machine. The machines are at two different locations, but they are both running at roughly the same hash rate.

Does the length of time mining with Prohashing have anything to do with how earnings are calculated? Just trying to figure out why one machine is earning a significant amount more than the other?

Thanks in advance for any assistance.

Re: One Antminer L3+ machine earning more than the other

Posted: Mon Jan 01, 2018 2:59 pm
by JiveTonto
whats there daily totals if you dont mind me asking?

Re: One Antminer L3+ machine earning more than the other

Posted: Mon Jan 01, 2018 3:20 pm
by letitbegood
The last several days have been between the high $13's - $16ish, with the second machine earning approx. $4 less per day than these amounts.

Re: One Antminer L3+ machine earning more than the other

Posted: Mon Jan 01, 2018 3:30 pm
by JiveTonto
maby do some fixed password arguments , i can see the latency on shares getting summited making one miss out on potential payouts

Jus tot start ruling things out

Re: One Antminer L3+ machine earning more than the other

Posted: Mon Jan 01, 2018 4:04 pm
by letitbegood
But if I've been using the same password (n=worker_1) on both machines, shouldn't they be earning roughly the same amount assuming they have similar hash rates?

Re: One Antminer L3+ machine earning more than the other

Posted: Mon Jan 01, 2018 5:06 pm
by AppleMiner
The pool does not use the hashrate that the miner reports it is hashing at.
The pool bases the hashrate of the miners on the number of shares found at the difficulty of the coin you were working on.


So if you have 2 miners both hashing at 500, and 1 has 10% effecincy drop due to network lag or hardware errors.
Or one miner is just more lucky on a given day or timeframe than the other(silicon lottery) then it will report a higher hashrate than the miner finding less shares-If both miners have the same settings otherwise.

Re: One Antminer L3+ machine earning more than the other

Posted: Mon Jan 01, 2018 7:22 pm
by Aura89
letitbegood wrote:But if I've been using the same password (n=worker_1) on both machines, shouldn't they be earning roughly the same amount assuming they have similar hash rates?
I don't understand, you have two machines both with n=worker_1? Are they separate accounts? If not, then you shouldn't even be seeing the 2nd miner.

Re: One Antminer L3+ machine earning more than the other

Posted: Mon Jan 01, 2018 9:56 pm
by letitbegood
Hi, yes they are separate accounts. I own one of them with another person.

Re: One Antminer L3+ machine earning more than the other

Posted: Tue Jan 02, 2018 5:28 am
by EyePeaSea
If the better performing L3+ is owned by the other person, I'd swap them ;)

Have you compared the Miner Status screens on both (as per AppleMiner's comment about network latency / hardware errors etc.)

One new years resolution is to read and understand what the 'Miner Status' fields all mean (although I'm really not sure I want to know what a 'nonce' is - or maybe that has a different meaning in the US to the UK?).

Re: One Antminer L3+ machine earning more than the other

Posted: Tue Jan 02, 2018 11:25 am
by AppleMiner
The "nonce" in a bitcoin block is a 32-bit (4-byte) field whose value is set so that the hash of the block will contain a run of leading zeros. The rest of the fields may not be changed, as they have a defined meaning.

Any change to the block data (such as the nonce) will make the block hash completely different. Since it is believed infeasible to predict which combination of bits will result in the right hash, many different nonce values are tried, and the hash is recomputed for each value until a hash containing the required number of zero bits is found. The number of zero bits required is set by the difficulty. The resulting hash has to be a value less than the current difficulty and so will have to have a certain number of leading zero bits to be less than that. As this iterative calculation requires time and resources, the presentation of the block with the correct nonce value constitutes proof of work.