my desktop i7 3.3ghz
sse - yes
aux - no
aux 2 - no
can i make them yes ?
my desktop i7 3.3ghz
sse - yes
aux - no
aux 2 - no
can i make them yes ?
What is the ETA for sending the stuck payments?
Lots of “job not found (21)” with genoil 0.4.1 on zec.suprnova.cc:2142
What’s the solution to this?
I have just noticed the transaction ID 25619995, opid-4ff53915-492a-4b80-a056-8d910eb1e0cf was deleted from my transactions as completed.
Then my account was credited the amount, however this amount has been removed from the account and also there is no transaction for ID 25619995, opid-4ff53915-492a-4b80-a056-8d910eb1e0cf ?
Yes, the wallet failed again… It seems there’s a problem, i’m resyncing from scratch now and have the pool on the backup wallet.
Will let you know when I find out whats the issue with the wallet this time…
Wrong thread, go to Genoil thread to discuss.
When you think will be manually processed transactions? We waiting a long long time. The fee is go, price go down.
Don’t be stupid. The error happens to me only on suprnova, not on other pools. So very likely related to suprnova.
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:
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
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.
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 ?
Only CPU mining with Core i7?
What is AVX 1 & 2 no ?