[ANN][XMR] monero.crypto-pool.fr | Large Monero Mining Pool

[onetwentyfive]

Update :

Please mine on

xmr.crypto-pool.fr because it will redirect you on the fastest IP available ( xmr1.crypto-pool.fr or xmr2.crypto-pool.fr or xmr3.crypto-pool.fr...)

like this :

stratum+tcp://xmr.crypto-pool.fr:6666

like this :

C:\path_to_minerd\minerd.exe -a cryptonight -o stratum+tcp://xmr.crypto-pool.fr:6666 -u your_monero_address

C:\path_to_miner\ccminer.exe -l 8x64 -o stratum+tcp://xmr1.crypto-pool.fr:6666 -u your_monero_address -p x

so we all should be using port 6666? i've been using 3333

[superresistant]

Update :
Please mine on
xmr.crypto-pool.fr because it will redirect you on the fastest IP available ( xmr1.crypto-pool.fr or xmr2.crypto-pool.fr or xmr3.crypto-pool.fr...)
like this :
stratum+tcp://xmr.crypto-pool.fr:6666
like this :
C:\path_to_minerd\minerd.exe -a cryptonight -o stratum+tcp://xmr.crypto-pool.fr:6666 -u your_monero_address
C:\path_to_miner\ccminer.exe -l 8x64 -o stratum+tcp://xmr1.crypto-pool.fr:6666 -u your_monero_address -p x

so we all should be using port 6666? i've been using 3333

We're gonna update the ports with new rules and system but it is not done yet so you can stay on any port. 3333 is fine.

[ltcnim]

how can I get a payout of my remaining balance? my address:

4A6dz63kfnEPDzefMU51Y1AcbwmsdyxH1aAyKLVF5KigTMzfK824zM7SZ276pWzR7MNQwd8Suwv34a6 Ju9gQGztCT5TNgXk

[superresistant]

how can I get a payout of my remaining balance? my address:
4A6dz63kfnEPDzefMU51Y1AcbwmsdyxH1aAyKLVF5KigTMzfK824zM7SZ276pWzR7MNQwd8Suwv34a6 Ju9gQGztCT5TNgXk

Ok no problem.

[gilad215]

Can't connect to the pool.
guys?

[superresistant]

Can't connect to the pool.
guys?

Try port 7777

[bublik750]

Job timeout, disconnect, retry in 20 sec...

[superresistant]

Job timeout, disconnect, retry in 20 sec...

Here are the ports you can try in the meantime:
80,443,8080,6666,3333,7777

We are looking for what cause disconnect.

EDIT : the problem should be solved, please report if new disconnections.

[PVmining]

like this :
C:\path_to_miner\ccminer.exe -l 8x64 -o stratum+tcp://xmr1.crypto-pool.fr:6666 -u your_monero_address -p x

naaaa!  

btw. your pool performs quite well.
The last days I distributed my rigs to different pools and I was quite satisfied with the result of your pool.
hope it stays that good.

[bublik750]

Job timeout, disconnect, retry in 20 sec...

Here are the ports you can try in the meantime:
80,443,8080,6666,3333,7777

We are looking for what cause disconnect.

EDIT : the problem should be solved, please report if new disconnections.

all right, thank you

[superresistant]

like this :
C:\path_to_miner\ccminer.exe -l 8x64 -o stratum+tcp://xmr1.crypto-pool.fr:6666 -u your_monero_address -p x

naaaa!  

Thx for spotting the typo.

btw. your pool performs quite well.
The last days I distributed my rigs to different pools and I was quite satisfied with the result of your pool.
hope it stays that good.

Yes, we finally got positive results from optimizing the code.
The % pool efficiency tend to go lower when the total hashrate increase too fast but it should remain up as pool hash stabilize.
We've been over 110% for more than 2 days after the vardiff update and still over 100% despite the big jump in hashrate.
We're still optimizing. We found a new technique to update the pool without restarting and causing disconnection. You'll be much less disconnected by our experiments.

all right, thank you

You're welcome. Thx for bug reporting.

[Anobix]

Still getting random disconnects/job timeouts as an FYI, switching between 6666 and 3333 and 80

[superresistant]

Still getting random disconnects/job timeouts as an FYI, switching between 6666 and 3333 and 80

This come from 2 things :

 - botnets spamming the pool with very very low hashrate but millions of connections
 - Claymore GPU miner that split your hash as fees and increase the pool load

We had a discussion with Claymore and found a fix but it will take some time before seeing the effect.

If you still get disconnect, you can set multiple failover addresses with different ports to switch on.

[Anobix]

Still getting random disconnects/job timeouts as an FYI, switching between 6666 and 3333 and 80

This come from 2 things :

 - botnets spamming the pool with very very low hashrate but millions of connections
 - Claymore GPU miner that split your hash as fees and increase the pool load

We had a discussion with Claymore and found a fix but it will take some time before seeing the effect.

If you still get disconnect, you can set multiple failover addresses with different ports to switch on.

Thanks for the quick reply, looks like it is back up and working, I had failover to the multiple ports but it had to cycle through all of them a few times before sticking to one.

[sparks2013]

I'm still getting massive amounts of timeouts.

[superresistant]

Thanks for the quick reply, looks like it is back up and working, I had failover to the multiple ports but it had to cycle through all of them a few times before sticking to one.

I'm still getting massive amounts of timeouts.

Could you guys run a test for me ?
Go on this site : http://www.pingtest.net/
Chose Britain or Germany as a test server.
And report your connection results here or via PM.
I also need to know the miner you use & your average hashrate.

Thanks in advance. If you can't do it, it's fine no problem.

[sparks2013]

Thanks for the quick reply, looks like it is back up and working, I had failover to the multiple ports but it had to cycle through all of them a few times before sticking to one.

I'm still getting massive amounts of timeouts.

Could you guys run a test for me ?
Go on this site : http://www.pingtest.net/
Chose Britain or Germany as a test server.
And report your connection results here or via PM.
I also need to know the miner you use & your average hashrate.

Thanks in advance. If you can't do it, it's fine no problem.

I have quite a few headless miners, but it all seems to be working fine now / no more timeouts.  I also switched some of my miners off of ports 6666 to 3333.

[superresistant]

Right, sorry for the disconnections earlier. My friend had to disconnect some of you to update everyone with the fix.

The fix work !

Server charge has dropped from 66% to 6%. We can handle all miners and even botnet.

[Anobix]

Just a feature suggestion, no idea if it would be possible:

multiple worker tracking. Akin to how you have your vardiff +# at the end of the address, maybe a -1,-2,-3 to keep track of mulitple workers to make sure that each one is mining properly? Of course that would require doing multiple synching/lookups on the same page, I don't know if your servers can handle that kind of load or what kind of load that would require for the active refresh to continue to work in that fashion.

[superresistant]

Just a feature suggestion, no idea if it would be possible:
multiple worker tracking. Akin to how you have your vardiff +# at the end of the address, maybe a -1,-2,-3 to keep track of mulitple workers to make sure that each one is mining properly? Of course that would require doing multiple synching/lookups on the same page, I don't know if your servers can handle that kind of load or what kind of load that would require for the active refresh to continue to work in that fashion.

That's definitely a good feature to add but as you said, we must keep the server charge as low as possible because it could make us miss blocks somehow.
Let me talk with my pool dev.

-----

For 6 hours we had really low chance, most of our blocks were rejected (without appearing as orphan) but we found what was causing this.
It is a bug in bitmonerod that we reported to the monero devs. This bug can affect anyone, if you want more details, PM me.
I think we found the good fix as the chance is back to really high for the last 45 minutes.