Woohoo! Making progress in Neoscrypt now.
For those of you using Neoscrypt, I'd advise switching to Excavator 1.4.1a release for a Windows-based miner. It outperforms all Neoscrypt miners I've dealt with for most cards, assuming you're on 9.1 CUDA support and latest drivers. Don't trust the hashrate numbers coming out of HSRMiner; Palgin is a great guy, but the miner misrepresents what is actually doing at a pool level and has problems with hashrate dropoff over time.
What are you getting with latest excavator? 1080Ti (105% pwr, +100 core, +250 mem) = avg just over 1.69 MH/s 1070 (no OC) = avg just over 1.00 MH/s On my 4x1080Ti + 1x1070 rig, I was getting about 7.3 MH/s with KlausT. Excavator 1.4.1a gets me 7.76 MH/s. Palgin HSRMiner reports over 8 MH/s (after a 15 minute warmup period), but that doesn't match the pool reported hash rate and it starts to drop off after 30 minutes or so (and comes with a devfee). https://github.com/nicehash/excavator/releases/download/v1.4.1a/excavator_v1.4.1a_NVIDIA_Win64_CUDA_9.1.zipSniffDog has this as a dormant miner....EULA copyright law that SniffDog can't distribute.....which means it needs to be manually opened by the user.... Yes works great on neo  How did you guys format your .bat file for excavator? I'm trying it now with my bat file and it's just getting stuck on "core initialized". My bat file: excavator -a neoscrypt -o stratum+tcp://pool.unimining.net:4234 -u DDnfG1Zb2NjhC4kB7gep7R9ThkcbaSWU4y -p d=256,c=DSR,stats It's based on the command json file... You may have to read a little at the nicehash gethub for more info.... |
|
|
|
Woohoo! Making progress in Neoscrypt now.
For those of you using Neoscrypt, I'd advise switching to Excavator 1.4.1a release for a Windows-based miner. It outperforms all Neoscrypt miners I've dealt with for most cards, assuming you're on 9.1 CUDA support and latest drivers. Don't trust the hashrate numbers coming out of HSRMiner; Palgin is a great guy, but the miner misrepresents what is actually doing at a pool level and has problems with hashrate dropoff over time.
What are you getting with latest excavator? 1080Ti (105% pwr, +100 core, +250 mem) = avg just over 1.69 MH/s 1070 (no OC) = avg just over 1.00 MH/s On my 4x1080Ti + 1x1070 rig, I was getting about 7.3 MH/s with KlausT. Excavator 1.4.1a gets me 7.76 MH/s. Palgin HSRMiner reports over 8 MH/s (after a 15 minute warmup period), but that doesn't match the pool reported hash rate and it starts to drop off after 30 minutes or so (and comes with a devfee). https://github.com/nicehash/excavator/releases/download/v1.4.1a/excavator_v1.4.1a_NVIDIA_Win64_CUDA_9.1.zipSniffDog has this as a dormant miner....EULA copyright law that SniffDog can't distribute.....which means it needs to be manually opened by the user.... Yes works great on neo |
|
|
|
We are all trying to help you From another pool site..... Unfortunately, Crowdcoin CRC (neoscrypt) appears to have a chain split, and the pool ended up being in the shorter side of the split even though the pool is connected to 46 peers. Upon re-syncing to the longer chain, the pool had approximately 750 CRC orphaned during the 4 hours of mining on this split chain. This will affect miner's immature unconfirmed pending balance because orphans cannot get confirmed or cleared. It's sad that some coin's network just isn't well built. If you guys, as miners, see any "too good to be true" profit estimates, or long continuous streams of single coin blocks, it is probably too good to be true, and please contact us immediately to stop the coin. Fromage Belive or not, but looks like we are good on CRC. At least from first look. And anyway would not be affected, as didin't find any coin there. But let's keep an eye Ok, time to get some sleep. See you folks, hope blockchains are not that nasty tonight Sounds good! Just will wait now for btc payment and everything should be tiggidy-boo for now |
|
|
|
We are all trying to help you From another pool site..... Unfortunately, Crowdcoin CRC (neoscrypt) appears to have a chain split, and the pool ended up being in the shorter side of the split even though the pool is connected to 46 peers. Upon re-syncing to the longer chain, the pool had approximately 750 CRC orphaned during the 4 hours of mining on this split chain. This will affect miner's immature unconfirmed pending balance because orphans cannot get confirmed or cleared. It's sad that some coin's network just isn't well built. If you guys, as miners, see any "too good to be true" profit estimates, or long continuous streams of single coin blocks, it is probably too good to be true, and please contact us immediately to stop the coin. |
|
|
|
oppps bitcoin balance no tx id..
but I'm sure it will be returned and resent right?
No worries, it just too many things to sort out the same time , hint me once again on your wallet address. And this AMS wallet drives me nuts, it is again behind....!!!  Just check your logs... you will see that probably nobody got a bitcoin tx id...I have multiple accounts on here not just my default one IMHO... I would turn off AMS for now... looks like you will always have problems when bitsend drives almost 700mhs to xevan causing ams to be an instant mine... could be hard on the wallet and chain if that is how it all works Yes, you perhaps right regarding AMS. Checked BTC, so yes. Our balance on exhange is 0.02886674BTC, with withdrawal limit 0.03 BTC. I would really appreciate if you can wait until it arrives, otherwise I will send my personal BTC to pool BTC to cover your earnings. Let me know, thank you Yeah no need to start doing that out of your own pocket...we know you are just starting out.... some won't have patience as much.... just trying to help you out and maybe to others as to why they didn't get paid... Your honesty is your best policy |
|
|
|
oppps bitcoin balance no tx id..
but I'm sure it will be returned and resent right?
No worries, it just too many things to sort out the same time , hint me once again on your wallet address. And this AMS wallet drives me nuts, it is again behind....!!! Just check your logs... you will see that probably nobody got a bitcoin tx id...I have multiple accounts on here not just my default one IMHO... I would turn off AMS for now... looks like you will always have problems when bitsend drives almost 700mhs to xevan causing ams to be an instant mine... could be hard on the wallet and chain if that is how it all works |
|
|
|
|
oppps bitcoin balance no tx id..
but I'm sure it will be returned and resent right?
|
|
|
|
Kept 1/3 of my mining power on skunk. All would be to risky
Would the Admin please check ? Regardless of SONO upgrade, which is to happen from 192.500, we just went on wrong chain in ALTCOM. That could happen in blockchain, and sometimes it could really depend on nodes we are talking to at the point of time. I have disabled ALTCOM now, and performing upgrade to SONO. Thank you...this is not the only pool who had Altcom and not Sono... oh btw can you fix my equihash issue? http://zergpool.com/?address=1AMQg6m9GPDN9HGuC3wJGpSuiZr1XQXjxi |
|
|
|
This with skunk looks to good to be true . What to do ?
Honestly choice is yours... If I'm wrong you make good money... if I'm right then you hashed for nothing |
|
|
|
Me too. I noticed Skunk BTC/Day is off the charts - very suspicious. Could be wasted hashing power. Yeah I was trying to be polite... I'm not sure how he is going to compensate for not being on the right wallet update EDIT: I'ts been changed to Sono (Skunk algo) |
|
|
|
|
@Crackfoo.....
Polytimos algo? SniffDog is not picking up the API
Thanks for fixing it
|
|
|
|
Getting sporadic drops in stratum availability for most of the coins I'm trying to mine (C11/Xevan). Works for 5-10 minutes, then dies and doesn't come back for a while.
What command do you run, password argument? I had used "workername,c=FLAX" for the c11 mining password (using option 3 with a preestablished BTC address as userid). I am wondering now if the workername part is causing some confusion for your coin detection logic. I'll try again without the workername and see if that helps. c11 picked up and was running for me with the ID=$workername in my SniffDog script and was mining the proper coin since interzone is non auto trade I think that was good but if not where does the interzone coins go? Just was curious about LTC payouts... if users use a lightcoin address instead of btc address and a LTC symbol in the password... will the user get paid in litecoin? Btw... thanks for neoscrypt being lowered... I'm finally hitting some shares 1. Regarding c11. So you saying you specified BTC wallet and ITZ for picked for you in Option 1? Can you please post wallet address, I will check details. Normally it should prevent you to mine ITZ in Option 1. 2. Yes, it will be exchanged and you will be payed. I am just on my way to get LTC thresholds setup higher than BTC. no I had bitcoin wallet to c=BTC.... nvm stupid question  Thank you for replying to litecoin question... I just released SniffDog 4.0 with Zergpool... Welcome! |
|
|
|
Getting sporadic drops in stratum availability for most of the coins I'm trying to mine (C11/Xevan). Works for 5-10 minutes, then dies and doesn't come back for a while.
What command do you run, password argument? I had used "workername,c=FLAX" for the c11 mining password (using option 3 with a preestablished BTC address as userid). I am wondering now if the workername part is causing some confusion for your coin detection logic. I'll try again without the workername and see if that helps. c11 picked up and was running for me with the ID=$workername in my SniffDog script and was mining the proper coin since interzone is non auto trade I think that was good but if not where does the interzone coins go? Just was curious about LTC payouts... if users use a lightcoin address instead of btc address and a LTC symbol in the password... will the user get paid in litecoin? Btw... thanks for neoscrypt being lowered... I'm finally hitting some shares |
|
|
|
Still monitoring....
Can my script include a c=BTC at the end of a btc address... just makes my life easier when it's time to add you
Also, retired Alexis in newest update and now running with Tpruvot HSR Alexis on most algos... better come check your Sniffdog...I'm letting all the pools with Sniffdog know...
links are below
Very good, I will look into this. Currently my pool is customized a bit differently, giving more flexibility when it comes to mining. (e.g. you can have it both auto-exchange and direct mining). I will have to update stratum a bit to support c=BTC. At the moment it will first regiter your address as BTC, and afterwards will try to mine exactly BTC I know how to do it, I just need a time. I think I will leave c=BTC as on other pools to identify payout wallet, and will introduce mc=SYMBOL(mc will stand for mining coin) to target some particular coin. Now I need some sleep, see you folks! Sounds good keep up the good work! and Peace!.... Sniffdog out I have added support of c=BTC for Option 1. So it will work out of box with your Sniffdog release. And the of course if anyone wants to target particular coin, they can do it separately. And will rollout changes in 4 hours I think Thank you! EDIT: just noticing at homepage it shows c=BTC; is that correct or do we use c=BTC? Also, my cpuminer is not registering properly ... just not showing hash or % in the box at the bottom nor showing up at the pool statsnow my phi algo was getting a lot of invalid job id's....pool being either slow or having some other stratum or server issue?now yescrypt is getting invalid job id...pool being either slow or having some other stratum or server issue?
Stratum_recv_line failedRunning a bench- phi,xevan,c11,skein,equihash,groestl,bitcore,Nist5,Lyra2RE2,neoscrypt,skunk,blake2s,x17,yescrypt,m7m(tribus,quark,scrypt) can you lower neoscrypt stratum diff to 512 or 1024 please for smaller users? 16384 is a little high... 512 would be ideal having issues with equihash miner is dropping off...it is porting at your address Blake2s API is down Stratum diff for scrypt seems high at 524288( I usually don't have this algo open in SniffDog) That was misstype. just c=BTC. I lowered stratum diff for neo. Scrypt I will keep as this is requirement for Nicehash renting. Equihash is back online too. I actually don't have any blake2s yet. Does it prevent you from adding my pool? no your fine with Blake2s... SniffDog will pickup the competition blake2s algo API and leave yours out till you get yours up and running... If a user puts in a LTC address and places c=LTC in password(or any other Wallet address and password) will Zergpool autotrade coins to that LTC address? |
|
|
|
Still monitoring....
Can my script include a c=BTC at the end of a btc address... just makes my life easier when it's time to add you
Also, retired Alexis in newest update and now running with Tpruvot HSR Alexis on most algos... better come check your Sniffdog...I'm letting all the pools with Sniffdog know...
links are below
Very good, I will look into this. Currently my pool is customized a bit differently, giving more flexibility when it comes to mining. (e.g. you can have it both auto-exchange and direct mining). I will have to update stratum a bit to support c=BTC. At the moment it will first regiter your address as BTC, and afterwards will try to mine exactly BTC I know how to do it, I just need a time. I think I will leave c=BTC as on other pools to identify payout wallet, and will introduce mc=SYMBOL(mc will stand for mining coin) to target some particular coin. Now I need some sleep, see you folks! Sounds good keep up the good work! and Peace!.... Sniffdog out I have added support of c=BTC for Option 1. So it will work out of box with your Sniffdog release. And the of course if anyone wants to target particular coin, they can do it separately. And will rollout changes in 4 hours I think Thank you! EDIT: just noticing at homepage it shows c=BTC; is that correct or do we use c=BTC? Also, my cpuminer is not registering properly ... just not showing hash or % in the box at the bottom nor showing up at the pool statsnow my phi algo was getting a lot of invalid job id's....pool being either slow or having some other stratum or server issue?now yescrypt is getting invalid job id...pool being either slow or having some other stratum or server issue?
Stratum_recv_line failedRunning a bench- phi,xevan,c11,skein,equihash,groestl,bitcore,Nist5,Lyra2RE2,neoscrypt,skunk,blake2s,x17,yescrypt,m7m(tribus,quark,scrypt) can you lower neoscrypt stratum diff to 512 or 1024 please for smaller users? 16384 is a little high... 512 would be an ideal start having issues with equihash miner is dropping off...it is porting at your address Blake2s API is down... not an issue to SniffDog (just won't pick it up) Stratum diff for scrypt seems high at 524288( I usually don't have this algo open in SniffDog) ALL DONE! Just a few things to report... neoscrypt stratum diff and blake2s API down and equihash miner dropping out.... other than that I'm testing I like the way Zergpool reports the hashing on each coin.... Just one last question.... If a user puts in a LTC address and places c=LTC in password(or any other Wallet address and password) will Zergpool autotrade coins to that LTC address? |
|
|
|
|
Show Posts
