[ANN][POOL] ZERGPOOL.com - Multialgo, autoexchange, 0.5% fee, 250+ coins

[vethariya]

Hi,
It is important that balance is growing stable as per you hashrate contribution.
Pendings can fluctuate because of exchange prices and luck of found block.

What kind of fluctuation it was? (Neoscrypt)

https://vgy.me/qYaNvm.png

same here

[barbaron]

Hello pinpin,
I have some problem with being credited when mining Neoscrypt. I can see my balance in BTC /I choose option autoconvert in BTC/ since 00:00 AM is even lower, than now /06:39 AM/ At 00:00 AM today it was 0.00501148 BTC, now it shows 0.00493453 BTC/. At the same time I can see my miner sends shares whole night and I cannot understand why this happens? My rig is 8x1070 and I should as minimum make around 0.0006 BTC per 6:45 Hours mining Neoscrypt.
Can You check, please why all shares, which I submit was not credited to my wallet?
My BTC address is 1MVPhmQKNLqD71G6W3hje9oP4zoPH7BS66
Thank You for the help, pinpin!

Regards,
barbaron

[SergADM]

for the last week the pool has become foolish just is not real
I do not advise this pool!


зa пocлeднюю нeдeлю пyл cтaл дypить пpocтo нe peaльнo
нe coвeтyю дaнный пyл!

[SatyrA]

Test neoscrypt (default) with nicehash tool:

Pool host: mine.zergpool.com
Pool port: 4233
Pool user:
Pool pass:
Algorithm: NeoScrypt

Resolving pool host mine.zergpool.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 198.251.81.136:4233... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... Pool difficulty too low (provided=512, minimum=2048)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Received mining.notify work... OK
Error: Difficulty too low.



Test with custom diff:

Pool host: mine.zergpool.com
Pool port: 4233
Pool user:
Pool pass: c=BTC d=2048
Algorithm: NeoScrypt

Resolving pool host mine.zergpool.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 198.251.81.136:4233... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... OK: difficulty=2048
Received mining.notify work... OK

Pool verification process is complete. Tested pool is compatible!
Warning: Selected pool did not request min or higher working diff: 16384 Check FAQ!

[pinpins]

Hello pinpin,
I have some problem with being credited when mining Neoscrypt. I can see my balance in BTC /I choose option autoconvert in BTC/ since 00:00 AM is even lower, than now /06:39 AM/ At 00:00 AM today it was 0.00501148 BTC, now it shows 0.00493453 BTC/. At the same time I can see my miner sends shares whole night and I cannot understand why this happens? My rig is 8x1070 and I should as minimum make around 0.0006 BTC per 6:45 Hours mining Neoscrypt.
Can You check, please why all shares, which I submit was not credited to my wallet?
My BTC address is 1MVPhmQKNLqD71G6W3hje9oP4zoPH7BS66
Thank You for the help, pinpin!

Regards,
barbaron

Hello,

I know it raises wrong perception, when you look at those type of chart. But give it a a closer look all neoscrypt coins are fluctuating in market. BTC was raising last few days, altcoins against BTC became cheaper. We are mining highly volatility coins sometimes.

Take and example of QBIC down in 61% of a price in 24 hours. And RAP 64%.  That goes with a possibility they also raise in price a lot, but in a higher risk it goes vice versa.
That kind of explains on and offs...

However lessons learned could be that we should not trade high volatility coins and make the no autotrade..

[pinpins]

And given all stated above, I think most important is to refer to Actual earnings, the balance you are getting. And real earnings during the period of time

[pinpins]

Hi,
It is important that balance is growing stable as per you hashrate contribution.
Pendings can fluctuate because of exchange prices and luck of found block.

What kind of fluctuation it was? (Neoscrypt)

That was TUNE fork, please refer to previous messages.

[pinpins]

Test neoscrypt (default) with nicehash tool:

Pool host: mine.zergpool.com
Pool port: 4233
Pool user:
Pool pass:
Algorithm: NeoScrypt

Resolving pool host mine.zergpool.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 198.251.81.136:4233... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... Pool difficulty too low (provided=512, minimum=2048)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Received mining.notify work... OK
Error: Difficulty too low.



Test with custom diff:

Pool host: mine.zergpool.com
Pool port: 4233
Pool user:
Pool pass: c=BTC d=2048
Algorithm: NeoScrypt

Resolving pool host mine.zergpool.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 198.251.81.136:4233... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... OK: difficulty=2048
Received mining.notify work... OK

Pool verification process is complete. Tested pool is compatible!
Warning: Selected pool did not request min or higher working diff: 16384 Check FAQ!

Thanks, for giving a test there. Does this warning create troubles in further mining ? I will check config setup

[SatyrA]

Test neoscrypt (default) with nicehash tool:

Pool host: mine.zergpool.com
Pool port: 4233
Pool user:
Pool pass:
Algorithm: NeoScrypt

Resolving pool host mine.zergpool.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 198.251.81.136:4233... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... Pool difficulty too low (provided=512, minimum=2048)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Received mining.notify work... OK
Error: Difficulty too low.



Test with custom diff:

Pool host: mine.zergpool.com
Pool port: 4233
Pool user:
Pool pass: c=BTC d=2048
Algorithm: NeoScrypt

Resolving pool host mine.zergpool.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 198.251.81.136:4233... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... OK: difficulty=2048
Received mining.notify work... OK

Pool verification process is complete. Tested pool is compatible!
Warning: Selected pool did not request min or higher working diff: 16384 Check FAQ!

Thanks, for giving a test there. Does this warning create troubles in further mining ? I will check config setup

With diff=2048  miners often disconnect from pool due to "low difficulty" error . With diff=16384  (recommended minimum for nicehash)  I did not noticed disconnects but it may be too high diff for some coins. I suggest to set up auto adjust. Usually yimp pools set diff equivalent 5-15 shares per minute.

[pinpins]

Test neoscrypt (default) with nicehash tool:

Pool host: mine.zergpool.com
Pool port: 4233
Pool user:
Pool pass:
Algorithm: NeoScrypt

Resolving pool host mine.zergpool.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 198.251.81.136:4233... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... Pool difficulty too low (provided=512, minimum=2048)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Received mining.notify work... OK
Error: Difficulty too low.



Test with custom diff:

Pool host: mine.zergpool.com
Pool port: 4233
Pool user:
Pool pass: c=BTC d=2048
Algorithm: NeoScrypt

Resolving pool host mine.zergpool.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 198.251.81.136:4233... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... OK: difficulty=2048
Received mining.notify work... OK

Pool verification process is complete. Tested pool is compatible!
Warning: Selected pool did not request min or higher working diff: 16384 Check FAQ!

Thanks, for giving a test there. Does this warning create troubles in further mining ? I will check config setup

With diff=2048  miners often disconnect from pool due to "low difficulty" error . With diff=16384  (recommended minimum for nicehash)  I did not noticed disconnects but it may be too high diff for some coins. I suggest to set up auto adjust. Usually yimp pools set diff equivalent 5-15 shares per minute.

Yes, the issue is that we have some low difficulty coins there.  If the difficulty is set higher than one of the a mined coins, it will be forced down to fit the lowest coin's difficulty.

[SergADM]

Again, do not work on this pool
1. buggy constantly
2. missing coins
3. income is constantly falling
4. A hashit is stolen


eщe paз пoвтopюcь нe paбoтaйтe нa этoм пyлe
1. глючит пocтoяннo
2. пpoпaдaют дoбытыe мoнeты
3. дoxoд пocтoяннo пaдaeт
4. xeшpeйт кpaдyт.

[Chosscoin]

Again, do not work on this pool
1. buggy constantly
2. missing coins
3. income is constantly falling
4. A hashit is stolen


eщe paз пoвтopюcь нe paбoтaйтe нa этoм пyлe
1. глючит пocтoяннo
2. пpoпaдaют дoбытыe мoнeты
3. дoxoд пocтoяннo пaдaeт
4. xeшpeйт кpaдyт.

I agree with you

As soon as I reach 0.01 I will go to not return. Yesterday I had an outstanding balance, today in the morning it was different. Mino for hours and there is no benefit.

A user of this same forum told me to turn off Sniffdog. I deactivated it and yesterday I was mining Neoscrypt all day with bad results too.

[SergADM]

Again, do not work on this pool
1. buggy constantly
2. missing coins
3. income is constantly falling
4. A hashit is stolen


eщe paз пoвтopюcь нe paбoтaйтe нa этoм пyлe
1. глючит пocтoяннo
2. пpoпaдaют дoбытыe мoнeты
3. дoxoд пocтoяннo пaдaeт
4. xeшpeйт кpaдyт.

I agree with you

As soon as I reach 0.01 I will go to not return. Yesterday I had an outstanding balance, today in the morning it was different. Mino for hours and there is no benefit.

A user of this same forum told me to turn off Sniffdog. I deactivated it and yesterday I was mining Neoscrypt all day with bad results too.

until the last ddos attack and after it for 2 more days everything was super and then everything collapsed!
дo пocлeднeй ддoc aтaки и пocлe нee eщe 2 дня вce былo cyпepoвo a пoтoм вce cкaтилocь пoд oткoc!

[gogadvice]

hi pinpin...

would be glad if you could help me to understand


- current estimate
- 24 hour estimate
- 24 hour actual
- normalized

thank you  :-)

and thanks again for your work and that pool !

[Babalon]

Hi!
The last time I was mining on zergpool.com there were problems with qubit coins mining profit (Geo, Digibyte).
So, I want to clarify is the profit of mining qubit coins you`ve published is real now?


Thank you.

[pinpins]

Hi!
The last time I was mining on zergpool.com there were problems with qubit coins mining profit (Geo, Digibyte).
So, I want to clarify is the profit of mining qubit coins you`ve published is real now?


Thank you.

Hello,

We had problem with GEO twice when YOBIT provided wrong price in API, so we had to adjust price accordingly to the market. Lately price was correct, not like 1 BTC per GEO

I think must be stable now, but please ping me if you notice something wrong. I am happy to help

[pinpins]

UPDATE

I have set no autotrade for some higly violative neoscrypt coins. It is better we mine more stable now, to avoid fluctuations.

[Babalon]

Hi!
The last time I was mining on zergpool.com there were problems with qubit coins mining profit (Geo, Digibyte).
So, I want to clarify is the profit of mining qubit coins you`ve published is real now?


Thank you.

Hello,

We had problem with GEO twice when YOBIT provided wrong price in API, so we had to adjust price accordingly to the market. Lately price was correct, not like 1 BTC per GEO

I think must be stable now, but please ping me if you notice something wrong. I am happy to help

Thanks, hope there wouldn`t nessesary.
Any way I wish you good luck in your work of making your pool better.

[Jameson007]

UPDATE

I have set no autotrade for some higly violative neoscrypt coins. It is better we mine more stable now, to avoid fluctuations.

Ok, thx.

Next question - what about loosing shares when worker hashing is finished or worker is phisically disconnected? It looks wrong because it must be a valid shares (other pools is ok, share is fixed until block is founded).

few sec after stop hashing (you can see some fixed shares):
https://vgy.me/rIkm1y

about minute or two later (inn has been confirmed before resetting shares):
https://vgy.me/PtcuV7

as you see all valid shares was removed.

[SatyrA]

UPDATE

I have set no autotrade for some higly violative neoscrypt coins. It is better we mine more stable now, to avoid fluctuations.

Ok, thx.

Next question - what about loosing shares when worker hashing is finished or worker is phisically disconnected? It looks wrong because it must be a valid shares (other pools is ok, share is fixed until block is founded).

few sec after stop hashing (you can see some fixed shares):
https://vgy.me/rIkm1y

about minute or two later (inn has been confirmed before resetting shares):
https://vgy.me/PtcuV7

as you see all valid shares was removed.

I have noticed same thing. Looks like pool uses PPLNS reward system with very small N. Older shares dropped.