Yea, happening to me aswell. It is normal.
Maybe Suprnova is the only pool who actually checks if the share is valid (and thus should be credited) or not 
Unfortunately the wallet resyncing seems to take hours:
- Cache size: 100
- Top (height 2613): …
- New (height 1687): …
2016-11-01 10:15:43 Inconsistent witness cache state found for JSOutPoint(…, 0, 0) - Cache size: 100
- Top (height 2613): …
- New (height 1687): …
2016-11-01 10:16:17 Still rescanning. At block 1691. Progress=1.000000
2016-11-01 10:16:17 AddToWallet …
2016-11-01 10:16:17 Inconsistent witness cache state found for JSOutPoint(…, 0, 0) - Cache size: 100
- Top (height 2613): …
- New (height 1691): …
2016-11-01 10:16:34 AddToWallet …
2016-11-01 10:16:34 Inconsistent witness cache state found for JSOutPoint(…, 0, 1)
As you see it reprocesses 2-3 blocks per minute and it still has over 1000 blocks to go… So unfortunately this will take some time 
1 Like
my desktop is I7 3.3ghz
When i run miner:
sse2 - yes
avx - no
avx 2 - no
can i make avx and av2 yes ?
Pending (2 of 24) ZEC 0.00500892
Cool that something went through, yet the correct amount would be 0.00591215… Like there is a 18% fee 
Inavlid shares are labeled (20) in genoil. They happen on other pools (not on suprnova).
Suprnova instead produces “job not found (21)” right after “submitting solution”. Which looks like the work has expired or whatever. Maybe too high vardiff?
It occurs regularly every 10min maybe and then goes away alone after a few minutes. So it produces considerable wastage. Maybe too high vardiff and then job expires?
Any chance to get a port with fixed diff? I know from previous coins those work better.
You didn’t seem to see my previous post about this:
2016-10-31 19:33:42 (Thread 124) Suspicious Share rejected (Attack?): {“job”:“13”,“ip”:“x”,“worker”:“xxx”,“difficulty”:15.60970206,“error”:“job not found”}
2016-10-31 19:33:51 (Thread 14) Suspicious Share rejected (Attack?): {“job”:“13”,“ip”:“x”,“worker”:“xxx”,“difficulty”:15.60970206,“error”:“job not found”}
2016-10-31 19:34:03 (Thread 95) Suspicious Share rejected (Attack?): {“job”:“13”,“ip”:“x”,“worker”:“xxx”,“difficulty”:15.60970206,“error”:“job not found”}
See the “difficulty” there… That is the share difficulty. This means this user submitted three, for him individual, shares which I rejected and even marked them “suspicious” because the second and third share’s difficulty matches exactly the first shares diff.
This is practically impossible - you cannot have two or three subsequent shares with exactly the same difficulty, it’s a “fake” share - it’s the same share submitted twice or even three times here.
Thats why it’s rejected (and flagged :))
Other pools might not check that and therefore accept it … You hopefully know and understand what this means.
3 Likes
it seems that we don’t have found any of the last 20 blocks … very odd…
Are you running with VirtualBox?
We found some, but because of the mass of transactions which are processing, the cronjob is busy … They’ll be updating soon.
No just on desktop
Computer spec:
Intel Core i7 980
6 cores
12 threads
Should have AVX 1 & 2 no ?
1 Like
Only CPU mining with Core i7?
What is AVX 1 & 2 no ?
yep CPU mining on this one ?
mabey this model doesnt have AVX 1 & 2
Take it that this is a hardware change requiured… im getting slow speeds with the 
Intel Core i7 980
6 cores
12 threads
Both my laptops which are less cores and threads and less speed are doubling my desktop CPU speed as they are running AVX 1 & 2 instructions
On my desktop
AVX - no
AVX2 No
Are you running with 64 bit OS? windows 7 or 8?
tyler try with -e 2
this will let miner work with your avx2 instruction
charry
no you have not avx
charry
dam . so i need new processor . why sse2 so slow ?