Search content
Sort by
Showing 20 of 170 results by optiminer
Re: [ANN] Ħ [HODL] Version 5.0.0 was borked - urgent upgrade to version 6.0.0
The optiminer hodlcoin pool has been upgraded to the latest version 6.0.0 and is working again.
Happy mining and holding!
http://hodl.optiminer.pl
Happy mining and holding!
http://hodl.optiminer.pl
Code:
hodlminer.exe -o stratum+tcp://hodl.optiminer.pl:5555 -u HODLADDR -p x
./hodlminer -o stratum+tcp://hodl.optiminer.pl:5555 -u HODLADDR -p x
./hodlminer -o stratum+tcp://hodl.optiminer.pl:5555 -u HODLADDR -p x
Re: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.33 (Mar 23)
Under what license is this miner distributed?
Is the source available? It seems to use GPLed code, so I would expect it to be.
Is the source available? It seems to use GPLed code, so I would expect it to be.
Hi there,
Can you be more specific which code under GPL you think I am using? The only external libraries I use and link at the moment are the boost library and the g++/mingw64 runtimes. Well and OpenCL of cause. I hope I am not wrong here, so if you found somethink I use that I am not allowed to I will remove it immidiately. I wrote most of this from scratch - don't even have the external equihashverify code from node code in here. Beeing a bit more specific could help clarifying this.
Ah okay, so you claim it to be GPL code-free. That's fine. I do not have the code available so I cannot say much about that. But for parts of the opencl kernel it's obvious that you started from GPLed code and modified it from there (probably a lot). Just try this: https://www.google.com/search?q=%22occupy+the+high+32+bits+of+the+second+ulong+word%22
If that's still covered by the GPL or not I don't know.
Re: [ANN] Ħ [HODL] 5% Interest. No Staking Req. Term Deposits 10%. Solo Mining.
It's looking good!
Does anyone know which pools nicehash uses to aggreate their hasing power on ? I don't know, and want to buy a contract for hashing power on suprnova.cc, but they don't participate.
Is there a current list of HODL mining pools up to date that don't 404?
hodl.optiminer.pl works with nicehash
Re: [ANN] Ħ [HODL] 5% Interest. No Staking Req. Term Deposits 10%. Solo Mining.
Looking for HOdl pool instructions
I used to mine on suprnova.cc (can't remember what coin or if I stayed mining there very long) and I can still log in, but I can't reset my pin. My attempts for support never get reply's from the pool operators. Mining solo isn't working.
I suppose I will need to boot a Linux box and get programming. I have setup masternodes for other coins in the past. I expect it will take some messing about but I should be able to get a HOdl pool working. I am looking for any instructions on how to start a HOdl pool. If anyone has this information please reply or message me.
I used to mine on suprnova.cc (can't remember what coin or if I stayed mining there very long) and I can still log in, but I can't reset my pin. My attempts for support never get reply's from the pool operators. Mining solo isn't working.
I suppose I will need to boot a Linux box and get programming. I have setup masternodes for other coins in the past. I expect it will take some messing about but I should be able to get a HOdl pool working. I am looking for any instructions on how to start a HOdl pool. If anyone has this information please reply or message me.
Try http://hodl.optiminer.pl No registration required. Just start mining.
Re: [ANN][ROI] ROI Coin | CPU Only Solo Mining Hybrid | 15% POS | 593% Term Deposit
Nice! I can't see no payment yet?!? But I also noticed that my address suddenly disappeared from the list and came back after I restarted the miner. Started from 0 again. Maybe something got lost? Well, let's wait for the next block. 
Payouts happen normally with the next mined block. The list on the main page only shows currently active miner. Note that there is a search box on top of the page where you can enter your address and it will show you all the balance details.
Re: [ANN][ROI] ROI Coin | CPU Only Solo Mining Hybrid | 15% POS | 593% Term Deposit
Yes, the average is over the last N shares -- which is a long time as currently the hash rate is low. Changing the shown hash rate to a fixed interval has been on the TODO list for a long time. But for now, just let the miners run a few hours and you will see that the shown hash rate is correct.
Hope we will find the first block soon
Hope we will find the first block soon
Congrats! We just mined the first block
Re: [ANN][ROI] ROI Coin | CPU Only Solo Mining Hybrid | 15% POS | 593% Term Deposit
Yes, could be due to the averaging over time. The averaging time is constantly increasing.
Yes, I am trying to decipher that too. I started mining using just one computer and it shows 400h/s on computer but only 35 h/s on optiminer. Unless his table shows 10 times less than what h/s really is, I am missing something here.
if Paddy321 is running 650h/s for 1 hour, optiminer should show close to it. Average s hould be around that speed after 3 minutes, not just after 1 hour.
Reduce the shares that are kept for PPLNS. I used the same settings for the ROI pool as for my HODl pool which gets 10-20k H/s. That was probably not ideal for the start
Now the averaging interval is about 1 hour.Re: [ANN][ROI] ROI Coin | CPU Only Solo Mining Hybrid | 15% POS | 593% Term Deposit
Yes, the average is over the last N shares -- which is a long time as currently the hash rate is low. Changing the shown hash rate to a fixed interval has been on the TODO list for a long time. But for now, just let the miners run a few hours and you will see that the shown hash rate is correct.
Hope we will find the first block soon
Hope we will find the first block soon
Re: [ANN][ROI] ROI Coin | CPU Only Solo Mining Hybrid | 15% POS | 593% Term Deposit
Optiminer Mining Pool for ROIcoin is now available!
http://roi.optiminer.pl:8081/
Point your hodlminer to stratum+tcp://roi.optiminer.pl:5000:
./hodlminer -o stratum+tcp://roi.optiminer.pl:5000 -u ROIADDR -p x
http://roi.optiminer.pl:8081/
Point your hodlminer to stratum+tcp://roi.optiminer.pl:5000:
./hodlminer -o stratum+tcp://roi.optiminer.pl:5000 -u ROIADDR -p x
Re: [ANN] Ħ [HODL] 5% Interest. No Staking Req. Term Deposits 10%. Solo Mining.
http://hodl.optiminer.pl is now up again for testing!
Improvements:
- Minimum payout 1.0 hodl
- Balances are now usually payout out with the next mined block if they are above minimum.
- Reduced memory usage of pool.
- Added new balance calculation on miner page
Thanks for all the testers! This allowed me to fix various bugs and improve the UI.
I have removed the experimental warning on the pool page. This means the pool is open for all again, all major bugs seem to be fixed. I'll still keep an eye on it during the next days :-)
Happy mining!
Re: [ANN] Ħ [HODL] 5% Interest. No Staking Req. Term Deposits 10%. Solo Mining.
hodl.optiminer.pl down
The DB size grew to >4GB which it was not prepared for.
Originally, I set up this mining pool when there was no pool available as due to the forced locking of coins for 1 year. This is no longer true and there are alternative pools again. As I do not have the time that would be required to run and monitor the pool at a professional service level, I do not intend to bring the pool back up.
I will work on restoring the DB and paying out the outstanding balances in the next weeks.
Thanks for all the mining and don't forget to hodl your coins!
The DB size grew to >4GB which it was not prepared for.
Originally, I set up this mining pool when there was no pool available as due to the forced locking of coins for 1 year. This is no longer true and there are alternative pools again. As I do not have the time that would be required to run and monitor the pool at a professional service level, I do not intend to bring the pool back up.
I will work on restoring the DB and paying out the outstanding balances in the next weeks.
Thanks for all the mining and don't forget to hodl your coins!
All outstanding balances have been payed now!
As I noticed that there seems to be only one hodl mining pool alive, I might bring up my pool again. But it first requires some changes to the mining and database.
Thanks for sending payouts for everyone, and thanks for serving us this long!
I would love to see it back when you have time to work on it =)
If you need anything make sure to message us
http://hodl.optiminer.pl is now up again for testing!
Improvements:
- Minimum payout 1.0 hodl
- Balances are now usually payout out with the next mined block if they are above minimum.
- Reduced memory usage of pool.
- Added new balance calculation on miner page
Re: [ANN] Ħ [HODL] 5% Interest. No Staking Req. Term Deposits 10%. Solo Mining.
hodl.optiminer.pl down
The DB size grew to >4GB which it was not prepared for.
Originally, I set up this mining pool when there was no pool available as due to the forced locking of coins for 1 year. This is no longer true and there are alternative pools again. As I do not have the time that would be required to run and monitor the pool at a professional service level, I do not intend to bring the pool back up.
I will work on restoring the DB and paying out the outstanding balances in the next weeks.
Thanks for all the mining and don't forget to hodl your coins!
The DB size grew to >4GB which it was not prepared for.
Originally, I set up this mining pool when there was no pool available as due to the forced locking of coins for 1 year. This is no longer true and there are alternative pools again. As I do not have the time that would be required to run and monitor the pool at a professional service level, I do not intend to bring the pool back up.
I will work on restoring the DB and paying out the outstanding balances in the next weeks.
Thanks for all the mining and don't forget to hodl your coins!
All outstanding balances have been payed now!
As I noticed that there seems to be only one hodl mining pool alive, I might bring up my pool again. But it first requires some changes to the mining and database.
Quote
Here is an example from log files
We thought a block was found but it was rejected by the daemon, share data: {"job":"d3a2","ip":"::ffff:x.x.x.x","port":2053,"worker":"t1xxxxxxxxxeL","height":236147,"difficulty":0.2,"shareDiff":"4596.03419805","blockDiff":1351.176112912,"blockDiffActual":1351.176112912,"blockHash":"0000007212f19755fb017650d29e3823cf44a2b5aca1cf90baa36f3152951c0f","error":{"unknown":"check coin daemon logs"}}
ERROR: CheckEquihashSolution(): invalid solution
ERROR: CheckBlockHeader(): Equihash solution invalid
We thought a block was found but it was rejected by the daemon, share data: {"job":"d3a2","ip":"::ffff:x.x.x.x","port":2053,"worker":"t1xxxxxxxxxeL","height":236147,"difficulty":0.2,"shareDiff":"4596.03419805","blockDiff":1351.176112912,"blockDiffActual":1351.176112912,"blockHash":"0000007212f19755fb017650d29e3823cf44a2b5aca1cf90baa36f3152951c0f","error":{"unknown":"check coin daemon logs"}}
ERROR: CheckEquihashSolution(): invalid solution
ERROR: CheckBlockHeader(): Equihash solution invalid
Have you considered that the user might just have used the wrong hash algorithm param when connecting to the pool?
If the protocol is different it goes right away as an error on the first submit.
I have tested all the pools listed on the first page. They all report shares mined with a wrong algorithm as correct back to the miner:
Quote
$ ./optiminer-equihash -a equihash200_9 -s zer-eu.forgetop.com:2053 -u <...> -p x
[2018-01-17 01:42:59.055] [default] [info] Optiminer/Equihash 2.1.2 (C) Optiminer 2017
[2018-01-17 01:42:59.055] [default] [info] Connecting to zer-eu.forgetop.com:2053.
[2018-01-17 01:42:59.149] [default] [info] Using 2 verifier threads.
[2018-01-17 01:42:59.149] [default] [info] Using highly optimized kernel code for Fiji devices.
[2018-01-17 01:42:59.149] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Fiji.bin
[2018-01-17 01:42:59.150] [default] [info] Autodetected '--intensity 5' for device 0.
[2018-01-17 01:42:59.192] [default] [info] Extranonce is '60000043'.
[2018-01-17 01:42:59.233] [default] [info] Mining target is 0050000000000000000000000000000000000000000000000000000000000000
[2018-01-17 01:42:59.234] [default] [info] Got new work.
[2018-01-17 01:42:59.260] [default] [info] [GPU0] Device info: {"id": "0/0" "name": "Fiji" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:42:59.314] [default] [info] Connected to zer-eu.forgetop.com:2053.
[2018-01-17 01:42:59.464] [default] [info] Using highly optimized kernel code for Ellesmere devices.
[2018-01-17 01:42:59.464] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Ellesmere.bin
[2018-01-17 01:42:59.465] [default] [info] Autodetected '--intensity 5' for device 1.
[2018-01-17 01:42:59.570] [default] [info] [GPU1] Device info: {"id": "0/1" "name": "Ellesmere" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:42:59.773] [default] [info] Using highly optimized kernel code for Ellesmere devices.
[2018-01-17 01:42:59.773] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Ellesmere.bin
[2018-01-17 01:42:59.773] [default] [info] Autodetected '--intensity 5' for device 2.
[2018-01-17 01:42:59.879] [default] [info] [GPU2] Device info: {"id": "0/2" "name": "Ellesmere" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:43:01.015] [default] [info] [GPU2] Share accepted! (1 / 1)
[2018-01-17 01:43:02.549] [default] [info] [GPU0] Share accepted! (2 / 2)
[2018-01-17 01:43:03.061] [default] [info] [GPU2] Share accepted! (3 / 3)
[2018-01-17 01:42:59.055] [default] [info] Optiminer/Equihash 2.1.2 (C) Optiminer 2017
[2018-01-17 01:42:59.055] [default] [info] Connecting to zer-eu.forgetop.com:2053.
[2018-01-17 01:42:59.149] [default] [info] Using 2 verifier threads.
[2018-01-17 01:42:59.149] [default] [info] Using highly optimized kernel code for Fiji devices.
[2018-01-17 01:42:59.149] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Fiji.bin
[2018-01-17 01:42:59.150] [default] [info] Autodetected '--intensity 5' for device 0.
[2018-01-17 01:42:59.192] [default] [info] Extranonce is '60000043'.
[2018-01-17 01:42:59.233] [default] [info] Mining target is 0050000000000000000000000000000000000000000000000000000000000000
[2018-01-17 01:42:59.234] [default] [info] Got new work.
[2018-01-17 01:42:59.260] [default] [info] [GPU0] Device info: {"id": "0/0" "name": "Fiji" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:42:59.314] [default] [info] Connected to zer-eu.forgetop.com:2053.
[2018-01-17 01:42:59.464] [default] [info] Using highly optimized kernel code for Ellesmere devices.
[2018-01-17 01:42:59.464] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Ellesmere.bin
[2018-01-17 01:42:59.465] [default] [info] Autodetected '--intensity 5' for device 1.
[2018-01-17 01:42:59.570] [default] [info] [GPU1] Device info: {"id": "0/1" "name": "Ellesmere" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:42:59.773] [default] [info] Using highly optimized kernel code for Ellesmere devices.
[2018-01-17 01:42:59.773] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Ellesmere.bin
[2018-01-17 01:42:59.773] [default] [info] Autodetected '--intensity 5' for device 2.
[2018-01-17 01:42:59.879] [default] [info] [GPU2] Device info: {"id": "0/2" "name": "Ellesmere" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:43:01.015] [default] [info] [GPU2] Share accepted! (1 / 1)
[2018-01-17 01:43:02.549] [default] [info] [GPU0] Share accepted! (2 / 2)
[2018-01-17 01:43:03.061] [default] [info] [GPU2] Share accepted! (3 / 3)
It seems the pools internally filter those incorrect shares which is good. But they should be reported back to the miner as invalid.
The pool always get warnings when zcash solution is submited:
Share rejected: {"job":"ccd0","ip":"::ffff:x.x.x.x","worker":"xxxxx.xxx","difficulty":0.01,"error":"incorrect size of solution"}
And also there is no hashrate.
Unfortunately this is not the case with the problem. Not a single warning is presented in the log files.
Those ppl have good steady hasrate, everything is OK, just when it comes to finding block it got rejected from zcashd.
Just checked, the solution verification has stayed the same in optiminer since version 2.0. You are chasing a red herring here.
The problem also does not seem to be new: https://github.com/zerocurrency/zero/issues/6
My best guess would be that there is NOMP and zerod validate the block difficulty.
Don't work optiminer recognise hd graphics card of motherboard and stops...
Use the --list-devices option to show all devices and their -c / -d params. Then choose the correct platform (-c) and list all the devices of that platform that you want to mine on (-d), e.g.,
Quote
$ ./optiminer-equihash --list-devices
[2018-01-17 01:48:14.597] [default] [info] Optiminer/Equihash 2.1.2 (C) Optiminer 2017
Platform (-c) 0, Device (-d) 0:
Platform Vendor: AMD
Device Name: Fiji
Driver Version: 2482.3
Address bits: 64
Available memory: 4284411904
GCN Support: Gen 3
Has device specific faster kernel (for equihash200_9): Yes
Platform (-c) 0, Device (-d) 1:
Platform Vendor: AMD
Device Name: Ellesmere
Driver Version: 2482.3
Address bits: 64
Available memory: 4287418368
GCN Support: Gen 4
Has device specific faster kernel (for equihash200_9): Yes
$ ./optiminer-equihash -c 0 -d 0 -d 1 ...
[2018-01-17 01:48:14.597] [default] [info] Optiminer/Equihash 2.1.2 (C) Optiminer 2017
Platform (-c) 0, Device (-d) 0:
Platform Vendor: AMD
Device Name: Fiji
Driver Version: 2482.3
Address bits: 64
Available memory: 4284411904
GCN Support: Gen 3
Has device specific faster kernel (for equihash200_9): Yes
Platform (-c) 0, Device (-d) 1:
Platform Vendor: AMD
Device Name: Ellesmere
Driver Version: 2482.3
Address bits: 64
Available memory: 4287418368
GCN Support: Gen 4
Has device specific faster kernel (for equihash200_9): Yes
$ ./optiminer-equihash -c 0 -d 0 -d 1 ...
Quote
Here is an example from log files
We thought a block was found but it was rejected by the daemon, share data: {"job":"d3a2","ip":"::ffff:x.x.x.x","port":2053,"worker":"t1xxxxxxxxxeL","height":236147,"difficulty":0.2,"shareDiff":"4596.03419805","blockDiff":1351.176112912,"blockDiffActual":1351.176112912,"blockHash":"0000007212f19755fb017650d29e3823cf44a2b5aca1cf90baa36f3152951c0f","error":{"unknown":"check coin daemon logs"}}
ERROR: CheckEquihashSolution(): invalid solution
ERROR: CheckBlockHeader(): Equihash solution invalid
We thought a block was found but it was rejected by the daemon, share data: {"job":"d3a2","ip":"::ffff:x.x.x.x","port":2053,"worker":"t1xxxxxxxxxeL","height":236147,"difficulty":0.2,"shareDiff":"4596.03419805","blockDiff":1351.176112912,"blockDiffActual":1351.176112912,"blockHash":"0000007212f19755fb017650d29e3823cf44a2b5aca1cf90baa36f3152951c0f","error":{"unknown":"check coin daemon logs"}}
ERROR: CheckEquihashSolution(): invalid solution
ERROR: CheckBlockHeader(): Equihash solution invalid
Have you considered that the user might just have used the wrong hash algorithm param when connecting to the pool?
If the protocol is different it goes right away as an error on the first submit.
I have tested all the pools listed on the first page. They all report shares mined with a wrong algorithm as correct back to the miner:
Quote
$ ./optiminer-equihash -a equihash200_9 -s zer-eu.forgetop.com:2053 -u <...> -p x
[2018-01-17 01:42:59.055] [default] [info] Optiminer/Equihash 2.1.2 (C) Optiminer 2017
[2018-01-17 01:42:59.055] [default] [info] Connecting to zer-eu.forgetop.com:2053.
[2018-01-17 01:42:59.149] [default] [info] Using 2 verifier threads.
[2018-01-17 01:42:59.149] [default] [info] Using highly optimized kernel code for Fiji devices.
[2018-01-17 01:42:59.149] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Fiji.bin
[2018-01-17 01:42:59.150] [default] [info] Autodetected '--intensity 5' for device 0.
[2018-01-17 01:42:59.192] [default] [info] Extranonce is '60000043'.
[2018-01-17 01:42:59.233] [default] [info] Mining target is 0050000000000000000000000000000000000000000000000000000000000000
[2018-01-17 01:42:59.234] [default] [info] Got new work.
[2018-01-17 01:42:59.260] [default] [info] [GPU0] Device info: {"id": "0/0" "name": "Fiji" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:42:59.314] [default] [info] Connected to zer-eu.forgetop.com:2053.
[2018-01-17 01:42:59.464] [default] [info] Using highly optimized kernel code for Ellesmere devices.
[2018-01-17 01:42:59.464] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Ellesmere.bin
[2018-01-17 01:42:59.465] [default] [info] Autodetected '--intensity 5' for device 1.
[2018-01-17 01:42:59.570] [default] [info] [GPU1] Device info: {"id": "0/1" "name": "Ellesmere" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:42:59.773] [default] [info] Using highly optimized kernel code for Ellesmere devices.
[2018-01-17 01:42:59.773] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Ellesmere.bin
[2018-01-17 01:42:59.773] [default] [info] Autodetected '--intensity 5' for device 2.
[2018-01-17 01:42:59.879] [default] [info] [GPU2] Device info: {"id": "0/2" "name": "Ellesmere" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:43:01.015] [default] [info] [GPU2] Share accepted! (1 / 1)
[2018-01-17 01:43:02.549] [default] [info] [GPU0] Share accepted! (2 / 2)
[2018-01-17 01:43:03.061] [default] [info] [GPU2] Share accepted! (3 / 3)
[2018-01-17 01:42:59.055] [default] [info] Optiminer/Equihash 2.1.2 (C) Optiminer 2017
[2018-01-17 01:42:59.055] [default] [info] Connecting to zer-eu.forgetop.com:2053.
[2018-01-17 01:42:59.149] [default] [info] Using 2 verifier threads.
[2018-01-17 01:42:59.149] [default] [info] Using highly optimized kernel code for Fiji devices.
[2018-01-17 01:42:59.149] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Fiji.bin
[2018-01-17 01:42:59.150] [default] [info] Autodetected '--intensity 5' for device 0.
[2018-01-17 01:42:59.192] [default] [info] Extranonce is '60000043'.
[2018-01-17 01:42:59.233] [default] [info] Mining target is 0050000000000000000000000000000000000000000000000000000000000000
[2018-01-17 01:42:59.234] [default] [info] Got new work.
[2018-01-17 01:42:59.260] [default] [info] [GPU0] Device info: {"id": "0/0" "name": "Fiji" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:42:59.314] [default] [info] Connected to zer-eu.forgetop.com:2053.
[2018-01-17 01:42:59.464] [default] [info] Using highly optimized kernel code for Ellesmere devices.
[2018-01-17 01:42:59.464] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Ellesmere.bin
[2018-01-17 01:42:59.465] [default] [info] Autodetected '--intensity 5' for device 1.
[2018-01-17 01:42:59.570] [default] [info] [GPU1] Device info: {"id": "0/1" "name": "Ellesmere" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:42:59.773] [default] [info] Using highly optimized kernel code for Ellesmere devices.
[2018-01-17 01:42:59.773] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Ellesmere.bin
[2018-01-17 01:42:59.773] [default] [info] Autodetected '--intensity 5' for device 2.
[2018-01-17 01:42:59.879] [default] [info] [GPU2] Device info: {"id": "0/2" "name": "Ellesmere" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:43:01.015] [default] [info] [GPU2] Share accepted! (1 / 1)
[2018-01-17 01:43:02.549] [default] [info] [GPU0] Share accepted! (2 / 2)
[2018-01-17 01:43:03.061] [default] [info] [GPU2] Share accepted! (3 / 3)
It seems the pools internally filter those incorrect shares which is good. But they should be reported back to the miner as invalid.
Your newer versions are under investigation after final versions appeared to produce wrong solutions. There are suspicions that those solutions could be back engineered to working state with proper actions applied from 3rd parties.
We currently direct everyone to use previous best working software as mysteriously old versions have disappeared from your github. At the same time when we have discovered this suspicious activity.
We currently direct everyone to use previous best working software as mysteriously old versions have disappeared from your github. At the same time when we have discovered this suspicious activity.
So, this is an accusation that my miner would try to cheat the users? This is a rather large claim. You better have some proof for that. It's the opposite, I actually reduced the fee from 2.5% (OptiminerZero) to 1% only in OptiminerEquihash.
The older versions of optiminer are all on the new download site.
http://download.optiminer.pl/optiminer-equihash-2.0.0.tar.gz
http://download.optiminer.pl/optiminer-equihash-2.1.0.tar.gz
http://download.optiminer.pl/optiminer-equihash-2.1.1.tar.gz
http://download.optiminer.pl/optiminer-equihash-2.1.2.tar.gz
github does not support well the hosting of large files. That's why the files have moved.
Quote
As you know very well we do pay fees for it so we can use it as much as we like.
If it is a problem for you we can all stop using it reverting back to a modded ccminer until we can have a community miner software.
Needs create solutions and whenever there is a big need a big solution is always found. If we find ourselves without a good working miner we can always create our own.
There was no need until now.... Let me know if there is one?
If it is a problem for you we can all stop using it reverting back to a modded ccminer until we can have a community miner software.
Needs create solutions and whenever there is a big need a big solution is always found. If we find ourselves without a good working miner we can always create our own.
There was no need until now.... Let me know if there is one?
Sorry, you are very wrong here. The existence of a fee does not mean you can use it like you want. You need to accept and adhere to the license to use it. What you say is like saying with a rental car you can do anything you want because you pay a rent.
If you feel like writing your own miner, go ahead.
Quote
Here is an example from log files
We thought a block was found but it was rejected by the daemon, share data: {"job":"d3a2","ip":"::ffff:x.x.x.x","port":2053,"worker":"t1xxxxxxxxxeL","height":236147,"difficulty":0.2,"shareDiff":"4596.03419805","blockDiff":1351.176112912,"blockDiffActual":1351.176112912,"blockHash":"0000007212f19755fb017650d29e3823cf44a2b5aca1cf90baa36f3152951c0f","error":{"unknown":"check coin daemon logs"}}
ERROR: CheckEquihashSolution(): invalid solution
ERROR: CheckBlockHeader(): Equihash solution invalid
We thought a block was found but it was rejected by the daemon, share data: {"job":"d3a2","ip":"::ffff:x.x.x.x","port":2053,"worker":"t1xxxxxxxxxeL","height":236147,"difficulty":0.2,"shareDiff":"4596.03419805","blockDiff":1351.176112912,"blockDiffActual":1351.176112912,"blockHash":"0000007212f19755fb017650d29e3823cf44a2b5aca1cf90baa36f3152951c0f","error":{"unknown":"check coin daemon logs"}}
ERROR: CheckEquihashSolution(): invalid solution
ERROR: CheckBlockHeader(): Equihash solution invalid
Have you considered that the user might just have used the wrong hash algorithm param when connecting to the pool?
Why not a windows version for 6gb cards??
I currently focus development on Linux.