Topic: [ANN][POOL] ZERGPOOL.com - Multialgo, autoexchange, 0.5% fee, 250+ coins - page 105. (Read 57735 times)
January 28, 2018, 06:11:11 AM
Hello. I joined the pool 48 hours ago. There are a few questions about the payments and rewards for the found blocks. For the found block, I do not get a 50% reward? Only that part of my hash? And when is the payment made once a week? If I have a wallet for Dash, will I be paid? Is there no solo mining? Sincerely, thanks
January 28, 2018, 06:05:38 AM
where is my payment ?
Wallet: 19VkR5s5tC6fjNj7Czvu4fpqMtBWCgH7WU
Total Unpaid 0.00137489 BTC
And where is the all other block I found ?
Wallet: 19VkR5s5tC6fjNj7Czvu4fpqMtBWCgH7WU
Total Unpaid 0.00137489 BTC
And where is the all other block I found ?
January 28, 2018, 05:36:06 AM
Bitcoin (total pending) - 0.00131143 BTC
Balance - 0.00189426 BTC
Total Unpaid - 0.00320569 BTC
Total Paid - 0.00000000 BTC
Total Earned - 0.00320569 BTC
Waiting to see if a payout will happen today...
Balance - 0.00189426 BTC
Total Unpaid - 0.00320569 BTC
Total Paid - 0.00000000 BTC
Total Earned - 0.00320569 BTC
Waiting to see if a payout will happen today...
I have BTC now into pool wallet. And payments were happening hour ago as per schedule, however for BTC I hit issue, where network ttf field exceded DB field max value. Eventually failing in processing
and taking value 'network_ttf' => -9223106500578770944
Minus because it exceeds Code:
'CDbCommand failed to execute the SQL statement: SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column \'network_ttf\' at row 1
NEthertheless funds are with us! I will try to fix that field max length issue now, and trigger payments
Thanks mate.
Not that I don't appreciate your devotion and time spent - I really do.
However, that current miner has not been generating any income for the last couple of days and that raises questions from certain people which I have to answer.
As soon as regular processing is restored, I'd be happy to switch back to zp
January 28, 2018, 05:09:00 AM
Bitcoin (total pending) - 0.00131143 BTC
Balance - 0.00189426 BTC
Total Unpaid - 0.00320569 BTC
Total Paid - 0.00000000 BTC
Total Earned - 0.00320569 BTC
Waiting to see if a payout will happen today...
Balance - 0.00189426 BTC
Total Unpaid - 0.00320569 BTC
Total Paid - 0.00000000 BTC
Total Earned - 0.00320569 BTC
Waiting to see if a payout will happen today...
I have BTC now into pool wallet. And payments were happening hour ago as per schedule, however for BTC I hit issue, where network ttf field exceded DB field max value. Eventually failing in processing
and taking value 'network_ttf' => -9223106500578770944
Minus because it exceeds Code:
'CDbCommand failed to execute the SQL statement: SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column \'network_ttf\' at row 1
NEthertheless funds are with us! I will try to fix that field max length issue now, and trigger payments
January 28, 2018, 04:12:16 AM
Bitcoin (total pending) - 0.00131143 BTC
Balance - 0.00189426 BTC
Total Unpaid - 0.00320569 BTC
Total Paid - 0.00000000 BTC
Total Earned - 0.00320569 BTC
Waiting to see if a payout will happen today...
Balance - 0.00189426 BTC
Total Unpaid - 0.00320569 BTC
Total Paid - 0.00000000 BTC
Total Earned - 0.00320569 BTC
Waiting to see if a payout will happen today...
January 28, 2018, 02:32:29 AM
Heading to bed.... You do have the history of the bitcoin balances we had from the last transactions(missing tx id) that never took place?
reason why I'm asking is that my Bitcoin balance was never restored
reason why I'm asking is that my Bitcoin balance was never restored
January 28, 2018, 02:14:56 AM
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.
@papacheal, I found and eliminated problem. The way system was designed, it cleaned up earnings after history table update - used just for the graphs.
Good I found it and commented, I have also restored your balance.
Going forward we will have all the history for all balances, so it must be easier to update it in case of hiccups like wrong blockchains etc...
January 28, 2018, 01:39:43 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
SONO is disabled now
January 28, 2018, 12: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 27, 2018, 11:01:48 PM
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, 10:54:48 PM
Lol i used this pool yesterday and today, its not funny how i waste my time and hash
January 27, 2018, 10: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, 10:29:03 PM
Its SONO in a true chain? or its like ALTCOM of yesterday?
January 27, 2018, 07: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, 07: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, 06: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, 06: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, 06: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, 06: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, 06: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
Jump to: