sgminer binaries with optimized Lyra2RE algorithm (by djm34 from Dec. 18th) and support for multi-algo are available: https://www.nicehash.com/index.jsp?p=software#sgminer (thanks badman74 for windows build). Do not forget to include ";f9=1.5" to the password parameter of your NiceHash multi-algo configuration if you want to enable Lyra2RE for multi-algo. As far as drivers are concerned - probably the best results are achieved with 14.6/14.7 drivers.
|
|
|
Fresh sgminer binaries with optimized Lyra2RE algorithm (by djm34) and support for multi-algo are available: https://www.nicehash.com/index.jsp?p=software#sgminer (thanks badman74 for windows build). Do not forget to include ";f9=1.5" to the password parameter of your NiceHash multi-algo configuration if you want to enable Lyra2RE for multi-algo.
|
|
|
What exactly is the issue with these stats? Graph is not refreshed if miner is not active! Displayed data is from the last active period. Please check dates with mouse over the graph.
|
|
|
Hi, NiceHash and WestHash are under DDoS. Mitigation is already active, but you might experience some network interruptions. Sorry for this, but the bad guys just never seems to get tired of this DDoSing bs...
|
|
|
Feature proposal: client report hashing speed
It would be very useful for stratum protocol to include a client message to report hashing speed. Today's miners (SHA256, Scrypt and others) vary a lot in terms of speed. For efficient initial vardiff handling, initial miners distribution in dependence of speed, etc. it wold be very useful for a pool to be informed by the client at what speed it is hashing. It would be nice if this would be implemented in the stratum protocol.
|
|
|
Why are these workers not authorized on the WestHash pool? (It's frustrating because I have 3.2TH/s worth of miners that WestHash is refusing)
Looks like the appendWorkerNames : true parameter (of Pfool's stratum proxy) doesn’t work with WestHash. Only one worker gets through, all the others are ignored with an authorisation error. It would be a huge advantage if Nice/WestHash could allow this work to be submitted, because then we could see our individual workers behind the proxy. We do support worker naming (see details in this FAQ: https://www.westhash.com/index.jsp?p=faq#faqs1) but unfortunately this feature does not work through Pfool's stratum proxy ... maybe you could raise this issue in Pfool's thread https://bitcointalk.org/index.php?topic=611338.0 ... hopefully he could fix this little bug.
|
|
|
Just a reminder: the gold rush is still ongoing, check out NiceHash.com / WestHash.com.
|
|
|
according to coinwarz its much better to mine than rent!! 3btc in 24hrs its saying?!! can only hope...
Coinwarz was going mad, 16th now is saying 1.2 btc daily. PayCoin mining is a bit of a gamble since PayCoin network hashrate and block findings fluctuates a lot (it is a game for those who want to risk a bit) ... your safest bet would be to use our multipool and get a stable income with pure PPS system. https://www.nicehash.com/index.jsp?p=stats (SHA256 tab) https://www.nicehash.com/index.jsp?p=gstarted#sellerNiceHash.com
|
|
|
I'm new to WestHash, please excuse me if these questions have been answered already: 1) Does KnCMiner Neptune work ok on NiceHash?
heh i'd like to put the patch in for the jupiter but have no idea if We haven't tested KnCMiner Neptune, but if you're referring to the extranonce.subscribe patch it is important to note that extranonce.subscribe is not absolutely required to mine on NiceHash/WestHash, you can just point your SHA256 miners to our stratum servers the same as any other Bitcoin pool. However, if you have a fast miner (anything > 1TH), then mining with extranonce.subscribe patched cgminer gives you a bit better payouts since your hashrate is completely stable - it doesn't fluctuate when orders changes on nicehash/westhash - no disconnects from the stratum. It's only a matter of a few percents in terms of profitability, but sometimes every percent counts. That said - just give it a try and report if you have any success (nevertheless it might be good for you to upgrade it to the latest firmware https://www.kncminer.com/pages/neptune-setup-info). The only show-stopper issue would it be if you would be getting 99-100% rejects - this happens with some particular versions of cgminer due to extranonce2-bug ... hopefully Neptune has a recent version of cgminer without this bug.
|
|
|
But if you want to test the SP20 with the new extronance bug fix by all means go ahead, you would be doing us all a favour by testing it. Just post the results so we can have a look and be very careful. Backup the old flash build and the cgminer twice. Once on the machine and once locally. If you're unsure of what you're doing stop...I've seen alot of stuff break over the years from bad flashing and other screwups without the tech guy making a backup to re-flash. It's an $800 mistake if it goes wrong.
By only replacing cgminer binary you can not brick or damage your miner. It is now a firmware update, only the cgminer binary (one executable file) with a newer one. Nevertheless it is true that one should be careful when doing manual modifications on miners. This binary was provided by ckolivas (thanks again, Con) and is working flawlessly: https://www.nicehash.com/index.jsp?p=miners&a=1&addr=1JFUoyUSnLcrMjfq3hEBFsNLhLk5QY3vQR+1 i've been waiting to see if Zvi would implement the extranonce.sub but I can't consider it for my SP-Tech miners from a nicehash branch that hasn't been fully tested.
We've already asked Zvi to include our very small patch into their firmware, hopefully they'll include it soon. no just point your miners at nicehash and enjoy the 3x to 7x rental rate while it lasts. I got .67 btc in 25 hours. my miners (7th) should earn about .1btc in that time frame.
True, extranonce.subscribe is not absolutely required to mine on NiceHash/WestHash, you can just point your miners to our stratum servers. However, if you have a fast miner (anything > 1TH) mining with extranonce.subscribe patched cgminer gives you a bit better payouts since your hashrate is completely stable - it doesn't fluctuate when orders changes on nicehash/westhash - no disconnects from the stratum. It's only a matter of a few percents in terms of profitability, but sometimes every percent counts.
|
|
|
We need more hashing power! What are you waiting for, point your SHA256 miners to NiceHash.com / WestHash.com!
|
|
|
If anybody is interested in mining VertCoin with the new Lyra2RE and doesn't have a miner: you can rent Lyra2RE hashing power at NiceHash.com.
|
|
|
For NiceHash/WestHash users: we have added Lyra2RE algorithm.SETTINGS:Here are some recommended settings: "pools" : [ { "name" : "NiceHash_Lyra2RE", "url" : "stratum+tcp://stratum.nicehash.com:3342", "user" : "your-BTC-address", "pass" : "d=1", "algorithm" : "Lyra2RE", "nfactor" : "10", "xintensity" : "64", "thread-concurrency" : "8192", "gpu-engine" : "1050", "gpu-memclock" : "1500", "worksize" : "64", "gpu-threads" : "2" }, Download miner from here: https://github.com/metalicjames/sgminer-Lyra2RE/releaseshttps://github.com/metalicjames/ccminer-Lyra2RE/releasesThese miners should also work well on other algorithms, but we haven't checked if all algorithms optimizations are included. Hopefully Lyra2RE will be soon included in sgminer-dev as well ( https://github.com/sgminer-dev/sgminer/pull/403) MULTIALGO:Lyra2RE is disabled on multilago by default (because currently you have to use a special sgminer fork and the transition will take a while, I guess). But nevertheless if you want to use multialgo you can still use it by manually adding Lyra2RE factor to your pool's password setting, for example: "pass" : "d=1;f0=0;f2=0;f3=8.5;f4=4.5;f5=500;f6=3.5;f7=14;f8=0.35; f9=1.25", (as always, remember to add this to all your NiceHash/WestHash pools entries, not only for the new Lyra2RE entry).
|
|
|
|