Wow SONO is a mess...
block explorer now is getting re-booted
I wonder which chain of SONO Yobit was on
block explorer now is getting re-booted
I wonder which chain of SONO Yobit was on
SONO is disabled now
Topic: [ANN][POOL] ZERGPOOL.com - Multialgo, autoexchange, 0.5% fee, 250+ coins - page 105. (Read 57362 times)
January 28, 2018, 02:39:43 AM
SONO is disabled now
January 28, 2018, 01:55:40 AM
Wow SONO is a mess...
block explorer now is getting re-booted
I wonder which chain of SONO Yobit was on
block explorer now is getting re-booted
I wonder which chain of SONO Yobit was on
January 28, 2018, 12:01:48 AM
Same here... I only made .005 btc in the matter of hours yesterday... but then the rest was orphaned
rigs are off it for now...
there is only 38ghs on the real chain so I'm assuming this pool is not the only one with issues
http://sonoexplorer.com/
rigs are off it for now...
there is only 38ghs on the real chain so I'm assuming this pool is not the only one with issues
http://sonoexplorer.com/
January 27, 2018, 11:54:48 PM
Lol i used this pool yesterday and today, its not funny how i waste my time and hash
January 27, 2018, 11:38:44 PM
I would say the same as yesterday..... not sure why that chain is so messed up
Admin please fix
Admin please fix
January 27, 2018, 11:29:03 PM
Its SONO in a true chain? or its like ALTCOM of yesterday?
January 27, 2018, 08:32:16 PM
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:
Code:
excavator -a neoscrypt -o stratum+tcp://pool.unimining.net:4234 -u DDnfG1Zb2NjhC4kB7gep7R9ThkcbaSWU4y -p d=256,c=DSR,stats
It's easiest to use a JSON command file, so you can just run "excavator -c command_file.json".
Here's an example of one I use for Neoscrypt for ORB on Zergpool with my 5-card rig:
Code:
[
{
"time": 0,
"commands": [
{
"id": 1,
"method": "algorithm.add",
"params": [
"neoscrypt",
"83.99.183.36:4233",
"1NG4nxGzn9sNhzYacha5XSazyZEt54X7vk:c=BTC,mc=ORB"
]
}
]
},
{
"time": 3,
"commands": [
{"id": 1,"method": "worker.add", "params": ["0", "0"]},
{"id": 2,"method": "worker.add", "params": ["0", "1"]},
{"id": 3,"method": "worker.add", "params": ["0", "2"]},
{"id": 4,"method": "worker.add", "params": ["0", "3"]},
{"id": 5,"method": "worker.add", "params": ["0", "4"]}
]
},
{
"time": 10,
"loop": 30,
"commands": [
{"id": 1,"method": "worker.print.speed", "params":["0"]},
{"id": 2,"method": "worker.print.speed", "params":["1"]},
{"id": 3,"method": "worker.print.speed", "params":["2"]},
{"id": 4,"method": "worker.print.speed", "params":["3"]},
{"id": 5,"method": "worker.print.speed", "params":["4"]},
{"id": 6,"method": "algorithm.print.speeds", "params": ["0"]}
]
}
]
{
"time": 0,
"commands": [
{
"id": 1,
"method": "algorithm.add",
"params": [
"neoscrypt",
"83.99.183.36:4233",
"1NG4nxGzn9sNhzYacha5XSazyZEt54X7vk:c=BTC,mc=ORB"
]
}
]
},
{
"time": 3,
"commands": [
{"id": 1,"method": "worker.add", "params": ["0", "0"]},
{"id": 2,"method": "worker.add", "params": ["0", "1"]},
{"id": 3,"method": "worker.add", "params": ["0", "2"]},
{"id": 4,"method": "worker.add", "params": ["0", "3"]},
{"id": 5,"method": "worker.add", "params": ["0", "4"]}
]
},
{
"time": 10,
"loop": 30,
"commands": [
{"id": 1,"method": "worker.print.speed", "params":["0"]},
{"id": 2,"method": "worker.print.speed", "params":["1"]},
{"id": 3,"method": "worker.print.speed", "params":["2"]},
{"id": 4,"method": "worker.print.speed", "params":["3"]},
{"id": 5,"method": "worker.print.speed", "params":["4"]},
{"id": 6,"method": "algorithm.print.speeds", "params": ["0"]}
]
}
]
You'll obviously need to adjust this for your BTC address, coin to mine etc. and adjust the number of "worker.add" and "worker.print.speed" lines to match the number of cards in your rig. Also, you need to know the IP of the pool stratum endpoint as DNS name resolution doesn't always work with Excavator. I've supplied the one for "zergpool.com" in that sample file. This file basically creates one Neoscrypt worker thread for each of my GPUs and prints the per-GPU and summary stats every 30 seconds.
January 27, 2018, 08:27:21 PM
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.
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.zip
SniffDog 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:
Code:
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....
January 27, 2018, 07:47:32 PM
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.
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.zip
SniffDog 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:
Code:
excavator -a neoscrypt -o stratum+tcp://pool.unimining.net:4234 -u DDnfG1Zb2NjhC4kB7gep7R9ThkcbaSWU4y -p d=256,c=DSR,stats
January 27, 2018, 07:35:13 PM
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.
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.zip
SniffDog 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
January 27, 2018, 07:27:23 PM
Hmm...something isn't right with my BTC balance.
@pinpins: Can you check out BTC wallet 1NG4nxGzn9sNhzYacha5XSazyZEt54X7vk?
My balance dropped over 0.001 BTC about 3 hours ago, but I haven't been involved in the Crowdcoin or Skunk chain splits. I've been working solely on c11/FLAX and Neoscrypt with PXC/ORB. Not sure what happened here.
@pinpins: Can you check out BTC wallet 1NG4nxGzn9sNhzYacha5XSazyZEt54X7vk?
My balance dropped over 0.001 BTC about 3 hours ago, but I haven't been involved in the Crowdcoin or Skunk chain splits. I've been working solely on c11/FLAX and Neoscrypt with PXC/ORB. Not sure what happened here.
January 27, 2018, 07:20:08 PM
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.
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.zip
Nice find It does perform better then klaust. thank you!
January 27, 2018, 07:14:25 PM
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.
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.zip
January 27, 2018, 07:04:29 PM
Hey could you add Vaperscoin https://bitcointalksearch.org/topic/annvprc-vaperscoin-scrypt-1489456 for scrypt it is sometimes very profitable even with small hashrate.
Hi
I can added, but after quick check it appears website and block explorer are all malware, how do we know that coin daemon is not?
Perhaps, I am paranoidal a bit , but makes me worry. Do you think many would mine it?
January 27, 2018, 06:28:23 PM
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.
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
January 27, 2018, 06:15:36 PM
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.
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
January 27, 2018, 06:12:29 PM
While skunk is ok and doesn't have that right?
Yes, skunk is ok. SONO should give us 1 coin, and it does so
January 27, 2018, 06:10:38 PM
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.
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?
January 27, 2018, 06:07:20 PM
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.
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.
January 27, 2018, 05:38:29 PM
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.
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.
Jump to: