MoparMiningLLC (OP)
aka Stryfe
Legendary
Offline
Activity: 2254
Merit: 2419
EIN: 82-3893490
|
|
March 04, 2020, 02:09:42 AM |
|
I am seeing that network diff is 6,404,536.6
and my best share on three of my L3+ are:
1,075,611,604 on 1st 5,916,014,328 on a 2nd 17,863,182,659 on a 3rd
all three are solo mining on ViaBTC but have "found" no blocks
I thought the share just needed to be higher than network diff - so, what am I missing?
|
|
|
|
philipma1957
Legendary
Offline
Activity: 4298
Merit: 8837
'The right to privacy matters'
|
|
March 04, 2020, 04:06:14 AM |
|
I am seeing that network diff is 6,404,536.6
and my best share on three of my L3+ are:
1,075,611,604 on 1st 5,916,014,328 on a 2nd 17,863,182,659 on a 3rd
all three are solo mining on ViaBTC but have "found" no blocks
I thought the share just needed to be higher than network diff - so, what am I missing?
not sure but does the 17,863,182,659 show 1 block made?
|
|
|
|
adaseb
Legendary
Offline
Activity: 3878
Merit: 1733
|
|
March 04, 2020, 04:14:49 AM |
|
It seems pretty risky solo mining LTC on an L3+. From what I recall the hashrate is what? 500 MH/s on those? By quick calculation thats like 625 days to find a single block. And keep in mind that many L3 are offline due to unprofitability and the difficulty now is 6M but it was 16M very recently. Hence if the price of LTC goes up in the near future then the difficulty can triple and 625 days becomes 1875 days. Most likely you will never hit a block...ever.
Looking at your best shares it looks like you should of hit a block on each miner however since it doesn't show up on the pool then most likely the multiple is off. Maybe its off by 10 or 100 factor. Because what are the chances of hitting a block already that should of taken almost 2 years? How long were you running them?
|
|
|
|
MoparMiningLLC (OP)
aka Stryfe
Legendary
Offline
Activity: 2254
Merit: 2419
EIN: 82-3893490
|
|
March 04, 2020, 04:54:19 AM |
|
I am seeing that network diff is 6,404,536.6
and my best share on three of my L3+ are:
1,075,611,604 on 1st 5,916,014,328 on a 2nd 17,863,182,659 on a 3rd
all three are solo mining on ViaBTC but have "found" no blocks
I thought the share just needed to be higher than network diff - so, what am I missing?
not sure but does the 17,863,182,659 show 1 block made? nope i am solo and got zero rewards so yea no block found It seems pretty risky solo mining LTC on an L3+. From what I recall the hashrate is what? 500 MH/s on those? By quick calculation thats like 625 days to find a single block. And keep in mind that many L3 are offline due to unprofitability and the difficulty now is 6M but it was 16M very recently. Hence if the price of LTC goes up in the near future then the difficulty can triple and 625 days becomes 1875 days. Most likely you will never hit a block...ever.
Looking at your best shares it looks like you should of hit a block on each miner however since it doesn't show up on the pool then most likely the multiple is off. Maybe its off by 10 or 100 factor. Because what are the chances of hitting a block already that should of taken almost 2 years? How long were you running them?
yes i know it is rare, but when i saw the shares i was like hmmm that shoulda been a block - yes about 504 mh/s - it had currently been solo mining 3 days or so, its in the screenshot as the miners uptime. check the miner gui - i dont think i am off on the share
|
|
|
|
JayDDee
|
|
March 04, 2020, 05:11:18 AM |
|
You are correct, your shares needs to be >= network difficulty.
But I'm not sure what you mean by found no blocks. Is this from the miner's point of view? Did it submit anything? Was it rejected?
If the miner didn't submit any of those shares it didn't think they were good enough. If it did and they were rejected there's a problem.
What's your TTF? Did you expect to find blocks in that time?
Edit: you posted more info while I was writing. I see lots of rejects, that's your problem.
|
|
|
|
MoparMiningLLC (OP)
aka Stryfe
Legendary
Offline
Activity: 2254
Merit: 2419
EIN: 82-3893490
|
|
March 04, 2020, 05:24:59 AM |
|
You are correct, your shares needs to be >= network difficulty.
But I'm not sure what you mean by found no blocks. Is this from the miner's point of view? Did it submit anything? Was it rejected?
If the miner didn't submit any of those shares it didn't think they were good enough. If it did and they were rejected there's a problem.
What's your TTF? Did you expect to find blocks in that time?
Edit: you posted more info while I was writing. I see lots of rejects, that's your problem.
yes - from the miners pov - look at the image, that is the antminer l3+ status page. it had 70 rejected shares in just over 3 days - you say that is high? I do not think that is very high. but how would i know if the high share was one of the 70? with all 3 hitting that high and no blocks. i am putting them back to pps at least while they are on ViaBTC - may switch to another solo pool and no, I did not expect to hit a block in 3 days but when there are shares that high on multiple miners, i find it hard to believe that all would be rejected. note: these miners have found blocks before, this would not have been their first.
|
|
|
|
JayDDee
|
|
March 04, 2020, 05:57:24 PM |
|
I would guess all your rejects are high diff, they wouldn't have been submitted otherwise. If you have logs you can confirm it.
The point being it's likely all submitted shares were rejected. The question is why? Given the number of submitted shares grossely exceeded your expectation it can be assumed the diff wasn't high enough to be accepted.
This comes back to a previous poster who commented about the "multiple". That multiple is the target factor, sometimes called diff factor or diff multiplier. The target factor works with the stratum difficulty to determine the share target.
The target factor is hard coded for each algo, for scrypt it's 2**16 (65536). If the target factor is set incorrectly the share diff could look higher than it actually is. Set incorrectly one way and the miner throws away good shares, set the other way and you submit a lot of low diff shares as I suspect is your problem.
The diff factor works both ways, the pool and miner have to work with the same factor. It could be a pool configuration issue, I've seen that before when a new algo is first introduced by a pool.
Sometimes there's a miner option that can set the target factor to work around a pool misconfiguration, You could try that if your miner supports it.
|
|
|
|
philipma1957laptop
Jr. Member
Offline
Activity: 38
Merit: 3
|
|
March 04, 2020, 08:21:30 PM Last edit: March 04, 2020, 09:15:21 PM by philipma1957laptop |
|
I have 11gh in ltc I earn .4 ltc a day so in 30 days I earn a block.
I just checked every miner and I have zero blocks.
Now I am pps+ and don't care.
But I find it very odd that I don't have a block showing on any of the 25 miners I have.
I will watch this thread and if I show a block I will show it.
I have some miners showing over 1,000,000,000 which is bigger then the diff. I suspect there is a multiplier involved. btw diff had been under
10,000,000 for a long time.
I have one l3+ doing 87,000,000,000 and no block so these numbers do not reflect what you need there is a multiplier.
I do have enough gear running to hit a block a month so if and when i do I will post the info on it.
|
|
|
|
adaseb
Legendary
Offline
Activity: 3878
Merit: 1733
|
|
March 04, 2020, 09:44:31 PM |
|
I've never had an Antminer L3 so I am not sure however does it report any hardware errors in the miner status page? Because if you overclocked, undervolted or did some tweaking with your L3 for efficiency or speed, then you might encounter some hardware errors and it might find some share which has a high difficulty share but since its invalid it might get rejected.
However I don't think this is the issue here because I think if the share is invalid due to hardware error then the miner doesn't submit it to the pool. So my best guess is that the best share being shown in your miner status is not reporting it properly, probably some multiple factor is taken into account. Especially since you were only mining 3 days.
This reminds me of mining with my Antminer S3 back in 2017 hoping to hit a block and I think my best share after a few months was like 1/1000th of the actual difficulty. I decided it was a waste of energy and just shut it off.
|
|
|
|
philipma1957laptop
Jr. Member
Offline
Activity: 38
Merit: 3
|
|
March 04, 2020, 09:53:12 PM |
|
I've never had an Antminer L3 so I am not sure however does it report any hardware errors in the miner status page? Because if you overclocked, undervolted or did some tweaking with your L3 for efficiency or speed, then you might encounter some hardware errors and it might find some share which has a high difficulty share but since its invalid it might get rejected.
However I don't think this is the issue here because I think if the share is invalid due to hardware error then the miner doesn't submit it to the pool. So my best guess is that the best share being shown in your miner status is not reporting it properly, probably some multiple factor is taken into account. Especially since you were only mining 3 days.
This reminds me of mining with my Antminer S3 back in 2017 hoping to hit a block and I think my best share after a few months was like 1/1000th of the actual difficulty. I decided it was a waste of energy and just shut it off.
it is a multiplier issue. although would think my 11gh would show 1 block hit he could do pps+ and get 1.5 x 0.03974 ltc a day with his units. that is about 0.06 ltc a day or 3.60 usd a day before power cost. he burns about 60kwatts a day for 3 of them so he needs 5 cent power
|
|
|
|
JayDDee
|
|
March 04, 2020, 11:43:31 PM |
|
it is a multiplier issue. although would think my 11gh would show 1 block hit
Agreed it's a multipler issue if the net hash rate is correct it's the miner inflating the share difficulty. You need to recalculate your expectations based on sharediff / 65536. Target factor is only used for shared pool mining using stratum. Some pools offer solo mining using stratum. I'm not familiar with ViaBTC but Zergpool does this. Zerg uses stratum and target factor just like shared pool mining. The shares are accepted but worthless. It's only if the share exceeds the net diff that a block is credited to the finder. It's all transparent to the miner, it thinks it's mining in a shared pool. This method worked fine for me when I tried it. Maybe ViaBTC does if differently in a way that isn't transparent and confuses miner software. Solo mining is probably better done in the wallet, no fees or other pool issues.
|
|
|
|
MoparMiningLLC (OP)
aka Stryfe
Legendary
Offline
Activity: 2254
Merit: 2419
EIN: 82-3893490
|
|
March 05, 2020, 01:22:59 AM |
|
I restarted the miners and put them back to coin foundry - will watch and next time I will look in the logs - I did not pull the logs before I restarted them to change the pools.
|
|
|
|
jstefanop
Legendary
Offline
Activity: 2173
Merit: 1401
|
I am seeing that network diff is 6,404,536.6
and my best share on three of my L3+ are:
1,075,611,604 on 1st 5,916,014,328 on a 2nd 17,863,182,659 on a 3rd
all three are solo mining on ViaBTC but have "found" no blocks
I thought the share just needed to be higher than network diff - so, what am I missing?
Your not mining "diff 1" shares on the pool/machine. Your L3s are most likely mining 16-64k diff shares. So your 18 bill share is really 250k-1M diff 1 IE the share to beat is network diff * share diff
|
|
|
|
MoparMiningLLC (OP)
aka Stryfe
Legendary
Offline
Activity: 2254
Merit: 2419
EIN: 82-3893490
|
|
March 06, 2020, 04:20:01 PM |
|
I am seeing that network diff is 6,404,536.6
and my best share on three of my L3+ are:
1,075,611,604 on 1st 5,916,014,328 on a 2nd 17,863,182,659 on a 3rd
all three are solo mining on ViaBTC but have "found" no blocks
I thought the share just needed to be higher than network diff - so, what am I missing?
Your not mining "diff 1" shares on the pool/machine. Your L3s are most likely mining 16-64k diff shares. So your 18 bill share is really 250k-1M diff 1 IE the share to beat is network diff * share diff ok gotcha - my miner is mining @ 31.5 diff if so, currently I have best share of 1,327,000,315 you are saying i need to have a best share that is greater than 6,084,937 (current ltc network diff) * 31,500 or 191,675,515,500 (give or take) for the share then right? and that makes way more sense - because yea no way in less than a day should I have expected all 3 to hit a block. I just wish I had kept track of what their share was last time they hit a block. I have found 4 blocks between these miners. 1 on tbdice and the other 3 on coinfoundry tbh it was the 17 bill that got my attention and then i started looking at the others and was like yea there is no way lol my BW-L21's never hit a block ever though
|
|
|
|
|
MoparMiningLLC (OP)
aka Stryfe
Legendary
Offline
Activity: 2254
Merit: 2419
EIN: 82-3893490
|
|
March 06, 2020, 06:12:03 PM |
|
not mining with any CPU's
|
|
|
|
JayDDee
|
|
March 06, 2020, 07:00:39 PM |
|
not mining with any CPU's You must have a CPU somewhere, any x86_64, Windows or Linux will do. You won't be doing it for the hashing, just the block info.
|
|
|
|
|