Pages:
Author

Topic: [ANN][POOL] ZERGPOOL.com - Multialgo, autoexchange, 0.5% fee, 250+ coins - page 60. (Read 57740 times)

newbie
Activity: 85
Merit: 0
2018-03-21 08:29:05] Stratum connection failed: Failed to connect to mine.zergpool.com port 8533: Timed out
[2018-03-21 08:29:05] ...retry after 30 seconds
[2018-03-21 08:29:56] Stratum connection failed: Failed to connect to mine.zergpool.com port 8533: Timed out
[2018-03-21 08:29:56] ...retry after 30 seconds
[2018-03-21 08:30:47] Stratum connection failed: Failed to connect to mine.zergpool.com port 8533: Timed out
[2018-03-21 08:30:47] ...retry after 30 seconds

 Same here Sad
newbie
Activity: 37
Merit: 0
2018-03-21 08:29:05] Stratum connection failed: Failed to connect to mine.zergpool.com port 8533: Timed out
[2018-03-21 08:29:05] ...retry after 30 seconds
[2018-03-21 08:29:56] Stratum connection failed: Failed to connect to mine.zergpool.com port 8533: Timed out
[2018-03-21 08:29:56] ...retry after 30 seconds
[2018-03-21 08:30:47] Stratum connection failed: Failed to connect to mine.zergpool.com port 8533: Timed out
[2018-03-21 08:30:47] ...retry after 30 seconds
copper member
Activity: 96
Merit: 1
Sorry Zerg,
I was hopeful when I saw Awesome Miner support Zergpool, however I'm dismayed by the payouts (lack of).  Even when there are sufficient earnings (IMO) the threshold for LTC prevents payout until .26LTC is reached.  From Zergpool: "Balance payment threshold is ~0.26 based on 0.005 BTC equivalent; and ~0.05 on Sunday".  Currently, if you want to mine at Zergpool you won't get paid until you've mined more than $40.
I like the pool but can't agree with any payout limits.
member
Activity: 514
Merit: 11
UPDATE

1. To clarify regarding new stratum endpoints. Those are already operational, so you can switch over to them. Old ones are operational as well. EU and US concept will be discontinued as there will be internal routing and load balancing based on user region. So for end user it will simply be just .mine.zergpool.com:

Thank you!
Change is to be integrated in the next version of NPLusMiner coming end of week.
Ready in dev version.
newbie
Activity: 140
Merit: 0
UPDATE

1. To clarify regarding new stratum endpoints. Those are already operational, so you can switch over to them. Old ones are operational as well. EU and US concept will be discontinued as there will be internal routing and load balancing based on user region. So for end user it will simply be just .mine.zergpool.com:

Finally next week ZergPool will be one of top 3 pools and will be able to pay miners around 10 million dollars a month and have 24/24 human management to avoid orphaned blocks.

Looking forward to test it again next week and I will move a few hundred rigs to zergpool if it will be the most profitable.

Congratulations !

member
Activity: 1027
Merit: 19
UPDATE

1. To clarify regarding new stratum endpoints. Those are already operational, so you can switch over to them. Old ones are operational as well. EU and US concept will be discontinued as there will be internal routing and load balancing based on user region. So for end user it will simply be just .mine.zergpool.com:
hero member
Activity: 714
Merit: 512
1) "connection refused" - that I noticed a lot for many RIGS ( DDOS protection is too restrictive or server is overloaded ) ;  
2) many orphaned blocks caused by too late coin being disabled or bad configuration when there is a chain split
I believe the root of evil is the same for both: the hardware is too weak to handle more than a certain number of miners connections -> when this limit is reached, the stratum server falls off and miners start getting "connection refused" -> when stratum server goes up and miners resume working on the block, that block comes too late and the network refuses it (i.e. it becomes "orphan").
However, it's just my theory, I don't know what actually goes there.

2. I also do hope mining software developers will switch over to new stratum server name format. (We will change to .mine.zergpool.com: server name format, so you can start updating your configuration to support this slowly). This will make it possible to have different network routes for different stratum servers.

I manually updated my NEMOSMINER to accept it -- it's very simple.

In the pool .ps1 you change this:

$Locations | ForEach {
    $Location = $_

   $zergpool_Request | Get-Member -MemberType NoteProperty | Select-Object -ExpandProperty Name | foreach {
       $zergpool_Host = If ($Location -eq "Europe"){$Location + ".mine.zergpool.com"}else{"$_.mine.zergpool.com"}


-----

Add the part in BOLD/RED text -- and that is it! =)

I assume for Europe you also add the same to the previous instance of ".mine.zergpool.com" in the previous brackets.
member
Activity: 514
Merit: 11
UPDATE

1. x11 algo stratum will be working on x11.mine.zergpool.com. Will also change to [ALGO].mine.zergpool.com:[PORT] server name format, so you can start adapting slowly. No rush as old URLs will work also for quite some time

Hi pinpins.

What will it be for regional servers?
Should we assume [ALGO].Europe.zergpool.com?

Also, could you communicate on an effective date when all new URLs will be accessible?

I need to update NPlusMiner according to the change and let users know.

Best regards,
MrPlus
newbie
Activity: 140
Merit: 0
1) "connection refused" - that I noticed a lot for many RIGS ( DDOS protection is too restrictive or server is overloaded ) ;  
2) many orphaned blocks caused by too late coin being disabled or bad configuration when there is a chain split
I believe the root of evil is the same for both: the hardware is too weak to handle more than a certain number of miners connections -> when this limit is reached, the stratum server falls off and miners start getting "connection refused" -> when stratum server goes up and miners resume working on the block, that block comes too late and the network refuses it (i.e. it becomes "orphan").
However, it's just my theory, I don't know what actually goes there.

Hello,

1.  I do plan massive HW upgrade on weekend, now preparation goes full speed. Want to make it as smooth as possible for users.
Meanwhile yes, we are close to limits in current config.

2. I also do hope mining software developers will switch over to new stratum server name format. (We will change to .mine.zergpool.com: server name format, so you can start updating your configuration to support this slowly). This will make it possible to have different network routes for different stratum servers.

pinpin

You will have to use several very powerful servers (web&db + Stratum svr + coinsvr) ?  This way the overall profitability will be increased and you will soon have the number of users zpool has targeting 30000 because next week you will be over aHashPool, they only have 6000 miners.

Think that with 6000 miners ahashpool makes daily payments of 7BTC and this means they pay every month 2,000,000 dollars and this means an income of $20,000 per month at 1% total fee that is with just 6000 miners and with 30k miners you will have an income of at least $100,000 per month.  If you take into consideration also huge profits from forgotten wallets or too old wallets that remain on your wallet, you do realize it worth having very powerful servers.  

You do realize zpool makes monthly payments of $10,000,000 ? You can soon be there if you will have the most profitable pool, and it is very easy to achieve that.

Do you agree, pinpin ?
member
Activity: 1027
Merit: 19
1) "connection refused" - that I noticed a lot for many RIGS ( DDOS protection is too restrictive or server is overloaded ) ;  
2) many orphaned blocks caused by too late coin being disabled or bad configuration when there is a chain split
I believe the root of evil is the same for both: the hardware is too weak to handle more than a certain number of miners connections -> when this limit is reached, the stratum server falls off and miners start getting "connection refused" -> when stratum server goes up and miners resume working on the block, that block comes too late and the network refuses it (i.e. it becomes "orphan").
However, it's just my theory, I don't know what actually goes there.

Hello,

1.  I do plan massive HW upgrade on weekend, now preparation goes full speed. Want to make it as smooth as possible for users.
Meanwhile yes, we are close to limits in current config.

2. I also do hope mining software developers will switch over to new stratum server name format. (We will change to .mine.zergpool.com: server name format, so you can start updating your configuration to support this slowly). This will make it possible to have different network routes for different stratum servers.

pinpin
member
Activity: 1027
Merit: 19
Quote
So how about my problem?
"...I mine on your pool a couple days on Bitcore BTX adress:  1HEna34LcLkbZv47HTHhrZCcYp2pp8szis
I didn't received any payment and yesterday I had more than 4BTX."
And now I have more than 6.5BTX on your pool and still not paid!
Also because of you I missed an 7% airdrop on Monday and it's like you simply still it from me!
I demand payment!!!!!!


Checked, we are short of BTX.

"BTC payouts are made automatically every 12 hours for all balances above 0.008, or 0.004 on Sunday.
Payouts for all other currencies are made automatically every 12 hours for all balances above 0.005 in BTC equivalent, or 0.001 on Sunday.
BTC and LTC are guaranteed payout coins, for others please check block amount we mine in pool."

If you mouse over BTX coin, you will see how much we are short of. It also is red color advising to switch to another one.

Hopefully we will get some mined soon!
hero member
Activity: 714
Merit: 512
If the server is in-house & not leased from a provider... you can grab some pretty mean servers used on e-bay.

I am mining with a bunch of Dell R815 with 4x Opteron 6380 CPUs (16 cores each) that I picked up very reasonably:

https://www.ebay.com/itm/PowerEdge-R815-4x-Opteron-6380-64C-2-5GHz-64GB-H700-2x-Tray-Monero-Crypto-Mining/173105716450?hash=item284de79ce2:g:44YAAOSwKwVaX8Ah
newbie
Activity: 140
Merit: 0
1) "connection refused" - that I noticed a lot for many RIGS ( DDOS protection is too restrictive or server is overloaded ) ;  
2) many orphaned blocks caused by too late coin being disabled or bad configuration when there is a chain split
I believe the root of evil is the same for both: the hardware is too weak to handle more than a certain number of miners connections -> when this limit is reached, the stratum server falls off and miners start getting "connection refused" -> when stratum server goes up and miners resume working on the block, that block comes too late and the network refuses it (i.e. it becomes "orphan").
However, it's just my theory, I don't know what actually goes there.

I hope pinpins will select a good server with this CPU:  Intel  2x Xeon E5-2680v4 - 28c/56t - 2.4GHz /3.3GHz RAM:  512GB DDR4 ECC 2133 MHz with 2 x 450GB NVME SSD ( https://www.ovh.ie/dedicated_servers/enterprise/1801mg04.xml )
otherwise he will not be able to compete with zpool server that has more than 40000 miners simultaneously.

also :

Recommended installation of yiimp for large pools

Server setup break-down:
Server 1: Web Server
Server 2: DB Server
Server 3: Stratum Server
Server 4: Coin Daemon Server

I would install on the same powerful server both DB and Web Server to avoid network latency delay for each DB request.

Additional Servers can be setup to improve the network performance;
Server 5-7: Can be set as either backup web server, high diff stratum server, secondary coin server




But the most important part is to have dual Xeon 2x Xeon E5-2680v4 - 28c/56t , because miners are like a swarm of bees, all moving simultanously from one algo to another, and using many smaller servers for  different algos does not help, because most fo the time many servers will not be used, but if you have a powerful server it can handle large traffic amounts, specially for stratum to avoid "connection denied" and for web server with NGINX to handle the huge number of api requests form all miners that are downloading statistics via API.

What do you think, pinpins ?
newbie
Activity: 57
Merit: 0
1) "connection refused" - that I noticed a lot for many RIGS ( DDOS protection is too restrictive or server is overloaded ) ;  
2) many orphaned blocks caused by too late coin being disabled or bad configuration when there is a chain split
I believe the root of evil is the same for both: the hardware is too weak to handle more than a certain number of miners connections -> when this limit is reached, the stratum server falls off and miners start getting "connection refused" -> when stratum server goes up and miners resume working on the block, that block comes too late and the network refuses it (i.e. it becomes "orphan").
However, it's just my theory, I don't know what actually goes there.
newbie
Activity: 140
Merit: 0
WHY is this greedy pool not paid for three weeks my 0.002BTC Huh I will say that they are scammers Angry Angry Angry My wallet 194UADtniM913eexVqqSsyyo3P6nkScyqX
I wanted to stay on this pool but they're dishonorable! beware of them

because: BTC payouts are made automatically every 12 hours for all balances above 0.008, or 0.004 on Sunday. http://zerg.zergpool.com/
Read first.
newbie
Activity: 140
Merit: 0
Hi, I noticed there are  3 hours of orphaned blocks and pending balance suddenly dropped probably because of that.

Can you do anything to avoid  having so many orphaned blocks ?

I noticed that this pool's real revenue paid in BTC for 24 hours is  dragged down a lot by the following 2 issues:

1) "connection refused" - that I noticed a lot for many RIGS ( DDOS protection is too restrictive or server is overloaded ) ;  
2) many orphaned blocks caused by too late coin being disabled or bad configuration when there is a chain split

PinPin , if you use several public IPs and start more instances for the same algo, each instance with a different public IP, will this help avoiding this kind of issue ? How does ZPOOL solve this issue because they have 38000 miners and many times there are more than 8000 simultaneous miners for the same algo, a lot more than zergpool (see that only 3 non consecutive blocks are orphan for tribus on zpool : https://www.zpool.ca/site/mining ) ? Thanks.
newbie
Activity: 38
Merit: 0
Hello.
I mine on your pool a couple days on Bitcore BTX adress:  1HEna34LcLkbZv47HTHhrZCcYp2pp8szis
I didn't received any payment and yesterday I had more than 4BTX. Today an airdrop day and I may not receive my coins because of that!
What's wrong???
Similar problem with LTC. The message was saying that the threshold is ~0.05. During the last payout before the change of the day I had 0.051 LTC and I got no payment. What does the ~0.05 LTC mean? 0.05 or 0.05999? Can't a stable number be used?

There is market price used. On Sunday there was deep on BTC, so LTC went almost up to 0.02BTC. So it is pure math in system.
This is a payment we did for LTC on Sunday.

https://chainz.cryptoid.info/ltc/tx.dws?b8aa0b5c0eafcc951c932e5e8e1b700fded6b65dde331e27a93e6a40f3b69755.htm
So how about my problem?
"...I mine on your pool a couple days on Bitcore BTX adress:  1HEna34LcLkbZv47HTHhrZCcYp2pp8szis
I didn't received any payment and yesterday I had more than 4BTX."
And now I have more than 6.5BTX on your pool and still not paid!
Also because of you I missed an 7% airdrop on Monday and it's like you simply still it from me!
I demand payment!!!!!!
member
Activity: 1027
Merit: 19
Hello.
I mine on your pool a couple days on Bitcore BTX adress:  1HEna34LcLkbZv47HTHhrZCcYp2pp8szis
I didn't received any payment and yesterday I had more than 4BTX. Today an airdrop day and I may not receive my coins because of that!
What's wrong???
Similar problem with LTC. The message was saying that the threshold is ~0.05. During the last payout before the change of the day I had 0.051 LTC and I got no payment. What does the ~0.05 LTC mean? 0.05 or 0.05999? Can't a stable number be used?

There is market price used. On Sunday there was deep on BTC, so LTC went almost up to 0.02BTC. So it is pure math in system.
This is a payment we did for LTC on Sunday.

https://chainz.cryptoid.info/ltc/tx.dws?b8aa0b5c0eafcc951c932e5e8e1b700fded6b65dde331e27a93e6a40f3b69755.htm
newbie
Activity: 57
Merit: 0
Looks like something up with Tribus consistently for the past half hour to hour:

*** ccminer 2.2.4 for nVidia GPUs by tpruvot@github ***
    Built with VC++ 2013 and nVidia CUDA SDK 9.0 64-bits

  Originally based on Christian Buchner and Christian H. project
  Include some kernels from alexis78, djm34, djEzo, tsiv and krnlx.

BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)

[2018-03-18 20:37:38] Starting on stratum+tcp://mine.zergpool.com:8533
[2018-03-18 20:37:38] NVML GPU monitoring enabled.
[2018-03-18 20:37:38] NVAPI GPU monitoring enabled.
[2018-03-18 20:37:38] 2 miner threads started, using 'tribus' algorithm.
[2018-03-18 20:37:39] API open to the network in read-only mode on port 4028
[2018-03-18 20:37:41] ...retry after 30 seconds
[2018-03-18 20:38:15] ...retry after 30 seconds
[2018-03-18 20:38:48] ...retry after 30 seconds
[2018-03-18 20:39:21] ...retry after 30 seconds

Seeing this on multiple systems. Anyone else having this issue?

Yes. Same issue.

There are still connection issues when the number of simultaneous miners for a single algo is above 1000. 

When can you install a much powerful server with many CPU cores ?

Installing many small servers is not helping because the number of miners can go very fast from 100 to 2000 while total number of miners remains almost the same and miners are never distributed to all algos, miners are like "a swarm of bees" that go from one algo to another all driven by Awesome Miner.

When will you have a very powerful server installed ?
He says about the coming weekend https://bitcointalksearch.org/topic/m.32505901
newbie
Activity: 140
Merit: 0
Looks like something up with Tribus consistently for the past half hour to hour:

*** ccminer 2.2.4 for nVidia GPUs by tpruvot@github ***
    Built with VC++ 2013 and nVidia CUDA SDK 9.0 64-bits

  Originally based on Christian Buchner and Christian H. project
  Include some kernels from alexis78, djm34, djEzo, tsiv and krnlx.

BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)

[2018-03-18 20:37:38] Starting on stratum+tcp://mine.zergpool.com:8533
[2018-03-18 20:37:38] NVML GPU monitoring enabled.
[2018-03-18 20:37:38] NVAPI GPU monitoring enabled.
[2018-03-18 20:37:38] 2 miner threads started, using 'tribus' algorithm.
[2018-03-18 20:37:39] API open to the network in read-only mode on port 4028
[2018-03-18 20:37:41] ...retry after 30 seconds
[2018-03-18 20:38:15] ...retry after 30 seconds
[2018-03-18 20:38:48] ...retry after 30 seconds
[2018-03-18 20:39:21] ...retry after 30 seconds

Seeing this on multiple systems. Anyone else having this issue?

Yes. Same issue.

There are still connection issues when the number of simultaneous miners for a single algo is above 1000. 

When can you install a much powerful server with many CPU cores ?

Installing many small servers is not helping because the number of miners can go very fast from 100 to 2000 while total number of miners remains almost the same and miners are never distributed to all algos, miners are like "a swarm of bees" that go from one algo to another all driven by Awesome Miner.

When will you have a very powerful server installed ?
Pages:
Jump to: