Search content
Sort by
Showing 20 of 179 results by dloganbill
Re: [ANN] NiceHash.com - innovative professional cryptocurrency cloud mining service
Are there any problems with Nicehash stability today? Hashrate is very volatile today...
I've been seeing issues as well. I don't have a p=x setting in place and nothing is hitting my failover.
https://nicehash.com/?p=miners&a=0&d=2&addr=192wH2yhWVyjiUkzf2qppnATSvmQkuMsxA
Re: [ANN] NiceHash.com - innovative professional cryptocurrency cloud mining service
Where can I see current order list??? I just registered in "Orders" tab I can see only my orders(has 0 so far) and create new - I don't know what price circa I should use.
It's on the homepage.
https://nicehash.com/index.jsp
Re: [ANN] NiceHash.com - innovative professional cryptocurrency cloud mining service
It sounds like they are ranking the orders based on the initial price when the order was placed. If someone adjusts the price, they should refresh what the new order ranking should be.
Example:
Order #12 @ price 0.9 1 Gh/s limit running (100 miners)
Order #11 @ price 0.8 no limit running (all remaining miners)
Order #15 @ price 0.7 no limit in queue
Order #10 @ price 0.5 no limit in queue
---Order #10 adjusts price to 0.7/no limit
Order #12 @ price 0.9 1 Gh/s limit running (100 miners)
Order #11 @ price 0.8 no limit running (all remaining miners)
Order #15 @ price 0.7 no limit in queue
Order #10 @ price 0.7 no limit in queue
---New order #16 is placed at 0.7/no limit
Order #12 @ price 0.9 1 Gh/s limit running (100 miners)
Order #11 @ price 0.8 no limit running (all remaining miners)
Order #15 @ price 0.7 no limit in queue
Order #10 @ price 0.7 no limit in queue
Order #16 @ price 0.7 no limit in queue
It sounds like Odie and others are seeing order #16 jumping ahead of #10 which is not fair since they placed the order after an existing order increased their price.
Example:
Order #12 @ price 0.9 1 Gh/s limit running (100 miners)
Order #11 @ price 0.8 no limit running (all remaining miners)
Order #15 @ price 0.7 no limit in queue
Order #10 @ price 0.5 no limit in queue
---Order #10 adjusts price to 0.7/no limit
Order #12 @ price 0.9 1 Gh/s limit running (100 miners)
Order #11 @ price 0.8 no limit running (all remaining miners)
Order #15 @ price 0.7 no limit in queue
Order #10 @ price 0.7 no limit in queue
---New order #16 is placed at 0.7/no limit
Order #12 @ price 0.9 1 Gh/s limit running (100 miners)
Order #11 @ price 0.8 no limit running (all remaining miners)
Order #15 @ price 0.7 no limit in queue
Order #10 @ price 0.7 no limit in queue
Order #16 @ price 0.7 no limit in queue
It sounds like Odie and others are seeing order #16 jumping ahead of #10 which is not fair since they placed the order after an existing order increased their price.
Linux noob here. I found the php files, but I don't know how to open or view them.
If you have a SFTP client just point it to your ip with minera/minera as user/pass you should be able to navigate the filesystem and get the files (then just open them with a text-edit)
Files are in /var/log/minera or /var/www/minera/application/logs (it's a directory link)
Here is what the logs look like
Code:
ERROR - 2014-05-28 23:55:02 --> Miner is up
ERROR - 2014-05-28 23:55:02 --> Storing stats...
ERROR - 2014-05-28 23:55:03 --> Delta Stats stored as: {"timestamp":1401321303,"pool_hashrate":2974929,"hashrate":3757777,"avg_freq":0,"accepted":0,"errors":0,"rejected":0,"shares":0}
ERROR - 2014-05-28 23:55:03 --> Total Stats stored as: {"timestamp":1401321303,"pool_hashrate":2974929,"hashrate":3757777,"avg_freq":895,"accepted":7629,"errors":40,"rejected":35,"shares":3639005}
ERROR - 2014-05-28 23:55:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:56:02 --> Miner is up
ERROR - 2014-05-28 23:56:02 --> Storing stats...
ERROR - 2014-05-28 23:56:03 --> Delta Stats stored as: {"timestamp":1401321363,"pool_hashrate":4971027,"hashrate":3757840,"avg_freq":0,"accepted":8,"errors":0,"rejected":0,"shares":4096}
ERROR - 2014-05-28 23:56:03 --> Total Stats stored as: {"timestamp":1401321363,"pool_hashrate":4971027,"hashrate":3757840,"avg_freq":895,"accepted":7637,"errors":40,"rejected":35,"shares":3643101}
ERROR - 2014-05-28 23:56:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:57:02 --> Miner is up
ERROR - 2014-05-28 23:57:02 --> Storing stats...
ERROR - 2014-05-28 23:57:03 --> Delta Stats stored as: {"timestamp":1401321423,"pool_hashrate":2354697,"hashrate":3758129,"avg_freq":0,"accepted":0,"errors":0,"rejected":0,"shares":0}
ERROR - 2014-05-28 23:57:03 --> Total Stats stored as: {"timestamp":1401321423,"pool_hashrate":2354697,"hashrate":3758129,"avg_freq":895,"accepted":7637,"errors":40,"rejected":35,"shares":3643101}
ERROR - 2014-05-28 23:57:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:58:02 --> Miner is up
ERROR - 2014-05-28 23:58:02 --> Storing stats...
ERROR - 2014-05-28 23:58:03 --> Delta Stats stored as: {"timestamp":1401321483,"pool_hashrate":4431717,"hashrate":3758139,"avg_freq":0,"accepted":7,"errors":0,"rejected":0,"shares":3584}
ERROR - 2014-05-28 23:58:03 --> Total Stats stored as: {"timestamp":1401321483,"pool_hashrate":4431717,"hashrate":3758139,"avg_freq":895,"accepted":7644,"errors":40,"rejected":35,"shares":3646685}
ERROR - 2014-05-28 23:58:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:59:02 --> Miner is up
ERROR - 2014-05-28 23:59:02 --> Storing stats...
ERROR - 2014-05-28 23:59:03 --> Delta Stats stored as: {"timestamp":1401321543,"pool_hashrate":2672477,"hashrate":3758158,"avg_freq":0,"accepted":2,"errors":0,"rejected":0,"shares":1024}
ERROR - 2014-05-28 23:59:03 --> Total Stats stored as: {"timestamp":1401321543,"pool_hashrate":2672477,"hashrate":3758158,"avg_freq":895,"accepted":7646,"errors":40,"rejected":35,"shares":3647709}
ERROR - 2014-05-28 23:55:02 --> Storing stats...
ERROR - 2014-05-28 23:55:03 --> Delta Stats stored as: {"timestamp":1401321303,"pool_hashrate":2974929,"hashrate":3757777,"avg_freq":0,"accepted":0,"errors":0,"rejected":0,"shares":0}
ERROR - 2014-05-28 23:55:03 --> Total Stats stored as: {"timestamp":1401321303,"pool_hashrate":2974929,"hashrate":3757777,"avg_freq":895,"accepted":7629,"errors":40,"rejected":35,"shares":3639005}
ERROR - 2014-05-28 23:55:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:56:02 --> Miner is up
ERROR - 2014-05-28 23:56:02 --> Storing stats...
ERROR - 2014-05-28 23:56:03 --> Delta Stats stored as: {"timestamp":1401321363,"pool_hashrate":4971027,"hashrate":3757840,"avg_freq":0,"accepted":8,"errors":0,"rejected":0,"shares":4096}
ERROR - 2014-05-28 23:56:03 --> Total Stats stored as: {"timestamp":1401321363,"pool_hashrate":4971027,"hashrate":3757840,"avg_freq":895,"accepted":7637,"errors":40,"rejected":35,"shares":3643101}
ERROR - 2014-05-28 23:56:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:57:02 --> Miner is up
ERROR - 2014-05-28 23:57:02 --> Storing stats...
ERROR - 2014-05-28 23:57:03 --> Delta Stats stored as: {"timestamp":1401321423,"pool_hashrate":2354697,"hashrate":3758129,"avg_freq":0,"accepted":0,"errors":0,"rejected":0,"shares":0}
ERROR - 2014-05-28 23:57:03 --> Total Stats stored as: {"timestamp":1401321423,"pool_hashrate":2354697,"hashrate":3758129,"avg_freq":895,"accepted":7637,"errors":40,"rejected":35,"shares":3643101}
ERROR - 2014-05-28 23:57:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:58:02 --> Miner is up
ERROR - 2014-05-28 23:58:02 --> Storing stats...
ERROR - 2014-05-28 23:58:03 --> Delta Stats stored as: {"timestamp":1401321483,"pool_hashrate":4431717,"hashrate":3758139,"avg_freq":0,"accepted":7,"errors":0,"rejected":0,"shares":3584}
ERROR - 2014-05-28 23:58:03 --> Total Stats stored as: {"timestamp":1401321483,"pool_hashrate":4431717,"hashrate":3758139,"avg_freq":895,"accepted":7644,"errors":40,"rejected":35,"shares":3646685}
ERROR - 2014-05-28 23:58:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:59:02 --> Miner is up
ERROR - 2014-05-28 23:59:02 --> Storing stats...
ERROR - 2014-05-28 23:59:03 --> Delta Stats stored as: {"timestamp":1401321543,"pool_hashrate":2672477,"hashrate":3758158,"avg_freq":0,"accepted":2,"errors":0,"rejected":0,"shares":1024}
ERROR - 2014-05-28 23:59:03 --> Total Stats stored as: {"timestamp":1401321543,"pool_hashrate":2672477,"hashrate":3758158,"avg_freq":895,"accepted":7646,"errors":40,"rejected":35,"shares":3647709}
It seems you haven't MM enabled, could you try to force it with this command?
Code:
redis-cli set mobileminer_enabled 1
This didn't work either. Should I try a fresh image?
Linux noob here. I found the php files, but I don't know how to open or view them.
If you have a SFTP client just point it to your ip with minera/minera as user/pass you should be able to navigate the filesystem and get the files (then just open them with a text-edit)
Files are in /var/log/minera or /var/www/minera/application/logs (it's a directory link)
Here is what the logs look like
Code:
ERROR - 2014-05-28 23:55:02 --> Miner is up
ERROR - 2014-05-28 23:55:02 --> Storing stats...
ERROR - 2014-05-28 23:55:03 --> Delta Stats stored as: {"timestamp":1401321303,"pool_hashrate":2974929,"hashrate":3757777,"avg_freq":0,"accepted":0,"errors":0,"rejected":0,"shares":0}
ERROR - 2014-05-28 23:55:03 --> Total Stats stored as: {"timestamp":1401321303,"pool_hashrate":2974929,"hashrate":3757777,"avg_freq":895,"accepted":7629,"errors":40,"rejected":35,"shares":3639005}
ERROR - 2014-05-28 23:55:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:56:02 --> Miner is up
ERROR - 2014-05-28 23:56:02 --> Storing stats...
ERROR - 2014-05-28 23:56:03 --> Delta Stats stored as: {"timestamp":1401321363,"pool_hashrate":4971027,"hashrate":3757840,"avg_freq":0,"accepted":8,"errors":0,"rejected":0,"shares":4096}
ERROR - 2014-05-28 23:56:03 --> Total Stats stored as: {"timestamp":1401321363,"pool_hashrate":4971027,"hashrate":3757840,"avg_freq":895,"accepted":7637,"errors":40,"rejected":35,"shares":3643101}
ERROR - 2014-05-28 23:56:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:57:02 --> Miner is up
ERROR - 2014-05-28 23:57:02 --> Storing stats...
ERROR - 2014-05-28 23:57:03 --> Delta Stats stored as: {"timestamp":1401321423,"pool_hashrate":2354697,"hashrate":3758129,"avg_freq":0,"accepted":0,"errors":0,"rejected":0,"shares":0}
ERROR - 2014-05-28 23:57:03 --> Total Stats stored as: {"timestamp":1401321423,"pool_hashrate":2354697,"hashrate":3758129,"avg_freq":895,"accepted":7637,"errors":40,"rejected":35,"shares":3643101}
ERROR - 2014-05-28 23:57:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:58:02 --> Miner is up
ERROR - 2014-05-28 23:58:02 --> Storing stats...
ERROR - 2014-05-28 23:58:03 --> Delta Stats stored as: {"timestamp":1401321483,"pool_hashrate":4431717,"hashrate":3758139,"avg_freq":0,"accepted":7,"errors":0,"rejected":0,"shares":3584}
ERROR - 2014-05-28 23:58:03 --> Total Stats stored as: {"timestamp":1401321483,"pool_hashrate":4431717,"hashrate":3758139,"avg_freq":895,"accepted":7644,"errors":40,"rejected":35,"shares":3646685}
ERROR - 2014-05-28 23:58:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:59:02 --> Miner is up
ERROR - 2014-05-28 23:59:02 --> Storing stats...
ERROR - 2014-05-28 23:59:03 --> Delta Stats stored as: {"timestamp":1401321543,"pool_hashrate":2672477,"hashrate":3758158,"avg_freq":0,"accepted":2,"errors":0,"rejected":0,"shares":1024}
ERROR - 2014-05-28 23:59:03 --> Total Stats stored as: {"timestamp":1401321543,"pool_hashrate":2672477,"hashrate":3758158,"avg_freq":895,"accepted":7646,"errors":40,"rejected":35,"shares":3647709}
ERROR - 2014-05-28 23:55:02 --> Storing stats...
ERROR - 2014-05-28 23:55:03 --> Delta Stats stored as: {"timestamp":1401321303,"pool_hashrate":2974929,"hashrate":3757777,"avg_freq":0,"accepted":0,"errors":0,"rejected":0,"shares":0}
ERROR - 2014-05-28 23:55:03 --> Total Stats stored as: {"timestamp":1401321303,"pool_hashrate":2974929,"hashrate":3757777,"avg_freq":895,"accepted":7629,"errors":40,"rejected":35,"shares":3639005}
ERROR - 2014-05-28 23:55:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:56:02 --> Miner is up
ERROR - 2014-05-28 23:56:02 --> Storing stats...
ERROR - 2014-05-28 23:56:03 --> Delta Stats stored as: {"timestamp":1401321363,"pool_hashrate":4971027,"hashrate":3757840,"avg_freq":0,"accepted":8,"errors":0,"rejected":0,"shares":4096}
ERROR - 2014-05-28 23:56:03 --> Total Stats stored as: {"timestamp":1401321363,"pool_hashrate":4971027,"hashrate":3757840,"avg_freq":895,"accepted":7637,"errors":40,"rejected":35,"shares":3643101}
ERROR - 2014-05-28 23:56:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:57:02 --> Miner is up
ERROR - 2014-05-28 23:57:02 --> Storing stats...
ERROR - 2014-05-28 23:57:03 --> Delta Stats stored as: {"timestamp":1401321423,"pool_hashrate":2354697,"hashrate":3758129,"avg_freq":0,"accepted":0,"errors":0,"rejected":0,"shares":0}
ERROR - 2014-05-28 23:57:03 --> Total Stats stored as: {"timestamp":1401321423,"pool_hashrate":2354697,"hashrate":3758129,"avg_freq":895,"accepted":7637,"errors":40,"rejected":35,"shares":3643101}
ERROR - 2014-05-28 23:57:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:58:02 --> Miner is up
ERROR - 2014-05-28 23:58:02 --> Storing stats...
ERROR - 2014-05-28 23:58:03 --> Delta Stats stored as: {"timestamp":1401321483,"pool_hashrate":4431717,"hashrate":3758139,"avg_freq":0,"accepted":7,"errors":0,"rejected":0,"shares":3584}
ERROR - 2014-05-28 23:58:03 --> Total Stats stored as: {"timestamp":1401321483,"pool_hashrate":4431717,"hashrate":3758139,"avg_freq":895,"accepted":7644,"errors":40,"rejected":35,"shares":3646685}
ERROR - 2014-05-28 23:58:04 --> Sending data to Mobileminer
ERROR - 2014-05-28 23:59:02 --> Miner is up
ERROR - 2014-05-28 23:59:02 --> Storing stats...
ERROR - 2014-05-28 23:59:03 --> Delta Stats stored as: {"timestamp":1401321543,"pool_hashrate":2672477,"hashrate":3758158,"avg_freq":0,"accepted":2,"errors":0,"rejected":0,"shares":1024}
ERROR - 2014-05-28 23:59:03 --> Total Stats stored as: {"timestamp":1401321543,"pool_hashrate":2672477,"hashrate":3758158,"avg_freq":895,"accepted":7646,"errors":40,"rejected":35,"shares":3647709}
This may not be the best place to post, but I'm having trouble with MobileMiner. I have two RPIs each with ten 5-chip gridseeds. I set up a MM account and set it up on one RPI. I logged into the app and it showed up right away. I set up the 2nd RPI the same way, except gave it a different name. However, it won't show up in the app. I power cycled the whole system (RPI, hub, PSU, etc) and still nothing. I thought maybe it would take a while for it to register, but it has been over 14 hours since the power cycle and still nothing.
You have a possible problem with php5-curl installation.
Please do exactly what I posted before your post, in particular the upgrade_minera.sh script
I tried what you said (twice actually) and it still hasn't shown up yet. Any other ideas?
Let me understand, is it working everything on that RPi but Mobileminer app? Could you check the application/logs/*.php? You should see some lines telling you it's trying to contact MM every minute. Look at it if there are some errors.
Linux noob here. I found the php files, but I don't know how to open or view them.
This may not be the best place to post, but I'm having trouble with MobileMiner. I have two RPIs each with ten 5-chip gridseeds. I set up a MM account and set it up on one RPI. I logged into the app and it showed up right away. I set up the 2nd RPI the same way, except gave it a different name. However, it won't show up in the app. I power cycled the whole system (RPI, hub, PSU, etc) and still nothing. I thought maybe it would take a while for it to register, but it has been over 14 hours since the power cycle and still nothing.
You have a possible problem with php5-curl installation.
Please do exactly what I posted before your post, in particular the upgrade_minera.sh script
I tried what you said (twice actually) and it still hasn't shown up yet. Any other ideas?
This may not be the best place to post, but I'm having trouble with MobileMiner. I have two RPIs each with ten 5-chip gridseeds. I set up a MM account and set it up on one RPI. I logged into the app and it showed up right away. I set up the 2nd RPI the same way, except gave it a different name. However, it won't show up in the app. I power cycled the whole system (RPI, hub, PSU, etc) and still nothing. I thought maybe it would take a while for it to register, but it has been over 14 hours since the power cycle and still nothing.
Seems to be no support here anymore.
well, there is no need, everything works just fine
With a gridseed and Nicehash combo, Minera is the champ IMO.
So that begs the question, Michelem, does your update today contain the latest commit from Sandor?
No, I'm just compiling it, some tests and I will push it asap.
PS
usually when I update the binary version I add a comment note in the commit so you can know it, just look here: https://github.com/michelem09/minera/commits/master
Is there a mirror for the img? Mega seems to be acting up...
I'm having the same problem. Dropbox option?
Re: LIGHTNINGASIC LA75M,75MHS SCRYPT Miner, USD8800; LA1THS, USD2350.shipped out!!!
rodeo, if you truly want to 100% get the truth in the open, follow this link and post your conversation. Everyone is tired of the rants, so let's put this to bed. You've posted the TX, now let's see your convo. Put up or shut up.
https://support.skype.com/en/faq/FA392/where-can-i-find-my-conversation-history-in-skype-for-windows-desktop-and-what-can-i-do-with-it
https://support.skype.com/en/faq/FA392/where-can-i-find-my-conversation-history-in-skype-for-windows-desktop-and-what-can-i-do-with-it
omg, no reason to be a dick- i still have my skype convo-
[deleted nonsense for everyone's sanity]
Once again you open your mouth and puke more nonsense instead of trying to help yourself. I have not bought anything from LA so I have no reason to "be scared." If you've read this thread at all you'd know that. I was genuinely trying to help clear up this mess. The skype convo log would prove WHO you talked to. While getting your BTC back is the ultimate goal, part of the solution is figuring out WHO you talked to. If you were dealing with a scammer alias, then we want to know that. If it wasn't a known scammer alias, we want to know that too. If it was a genuine LA alias, you've got him dead to rights.
This thread is full of very smart and skilled people (myself not included) that would like nothing more than to prove that either you or Jack were wrong. You have not welcomed ANY advice or questions from anyone. IF fact you are being incredibly rude to the community as a whole. Help us help you. No more "ready, fire, aim."
Re: LIGHTNINGASIC LA75M,75MHS SCRYPT Miner, USD8800; LA1THS, USD2350.shipped out!!!
rodeo, if you truly want to 100% get the truth in the open, follow this link and post your conversation. Everyone is tired of the rants, so let's put this to bed. You've posted the TX, now let's see your convo. Put up or shut up.
https://support.skype.com/en/faq/FA392/where-can-i-find-my-conversation-history-in-skype-for-windows-desktop-and-what-can-i-do-with-it
https://support.skype.com/en/faq/FA392/where-can-i-find-my-conversation-history-in-skype-for-windows-desktop-and-what-can-i-do-with-it
Here are the results from my head-to-head comparison against Hashra. I have two identical RPI setups with qty ten 5-chip miners each. Since there is no way to distinguish between rigs on Nicehash's website, I used my BTC address for Hashra Controla and Michelem's donation BTC address for the Minera controller.
Hashra's Dashboard and Nicehash stats
Minera's Dashboard, Settings, and Nicehash stats
Looking through the log, it looks like it took about 6 hours for the autotune process to finish. Minera had FAR fewer rejects and HW. It's hard to tell from a short run like this which is the ultimate winner, but I think that Minera has a solid edge over Hashra.
Hashra's Dashboard and Nicehash stats
Minera's Dashboard, Settings, and Nicehash stats
Looking through the log, it looks like it took about 6 hours for the autotune process to finish. Minera had FAR fewer rejects and HW. It's hard to tell from a short run like this which is the ultimate winner, but I think that Minera has a solid edge over Hashra.
Re: [ANN] NiceHash.com - innovative professional cryptocurrency cloud mining service
Here are the results from my head-to-head comparison against Hashra. I have two identical RPI setups with qty ten 5-chip miners each. Since there is no way to distinguish between rigs on Nicehash's website, I used my BTC address for Hashra Controla and Michelem's donation BTC address for the Minera controller.
Hashra's Dashboard and Nicehash stats
Minera's Dashboard, Settings, and Nicehash stats
Looking through the log, it looks like it took about 6 hours for the autotune process to finish. Minera had FAR fewer rejects and HW. It's hard to tell from a short run like this which is the ultimate winner, but I think that Minera has a solid edge over Hashra.
Hashra's Dashboard and Nicehash stats
Minera's Dashboard, Settings, and Nicehash stats
Looking through the log, it looks like it took about 6 hours for the autotune process to finish. Minera had FAR fewer rejects and HW. It's hard to tell from a short run like this which is the ultimate winner, but I think that Minera has a solid edge over Hashra.
Re: [Minera] New web management system for Gridseed devices
Here are the results from my head-to-head comparison against Hashra. I have two identical RPI setups with qty ten 5-chip miners each. Since there is no way to distinguish between rigs on Nicehash's website, I used my BTC address for Hashra Controla and Michelem's donation BTC address for the Minera controller.
Hashra's Dashboard and Nicehash stats
Minera's Dashboard, Settings, and Nicehash stats
Looking through the log, it looks like it took about 6 hours for the autotune process to finish. Minera had FAR fewer rejects and HW. It's hard to tell from a short run like this which is the ultimate winner, but I think that Minera has a solid edge over Hashra.
Hashra's Dashboard and Nicehash stats
Minera's Dashboard, Settings, and Nicehash stats
Looking through the log, it looks like it took about 6 hours for the autotune process to finish. Minera had FAR fewer rejects and HW. It's hard to tell from a short run like this which is the ultimate winner, but I think that Minera has a solid edge over Hashra.
Re: [ANN] NiceHash.com - innovative professional cryptocurrency cloud mining service
So what are people using to mine here with their Gridseed GC3355-Q64 55nm ASICs 
Last night I started running a side-by-side comparison of Hashra Mini Controlla vs Minera
Results so far:
Hashra--RPI with qty ten 5-chip Gridseeds, no d= or p= settings
https://nicehash.com/?p=miners&a=0&addr=192wH2yhWVyjiUkzf2qppnATSvmQkuMsxA
Minera--RPI with qty ten 5-chip Gridseeds, no d= or p= settings
https://nicehash.com/?p=miners&a=0&addr=1AmREReHNLec9EaW7gLRdW31LNSDA9SGR1
I have been using Hashra for quite a while with good success.
Re: [Minera] New web management system for Gridseed devices
For the speed to gain max hashrate, you can save the frequencies table (when you found the good ones) and restart your miner directly with the tuned devices.
Why don't you add a "automatically save and reuse autotuned frequencies" option in the settings page? Maybe also include a autotune reset button if someone wanted to restart the autotune after miner restart.
Re: [Minera] New web management system for Gridseed devices
Is the latest version compatible with Nicehash yet? I'm holding off until it is.
BumpThat has been answered in this thread already. As well as cpuminer thread.
Yes
Thank you. I must have missed that.
Michelem, I'm running another head to head comparison at Nicehash now. I am using your BTC address with 10 Gridseed miners vs Hashra+10 miners on my BTC address . I'll report back with results tomorrow.
Re: [Minera] New web management system for Gridseed devices
Is the latest version compatible with Nicehash yet? I'm holding off until it is.
Bump