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

[superresistant]

I keep getting
Stratum - connecting to 'xmr.crypto-pool.fr' <212.83.168.41> port 6666
Stratum - Connected
Error in server response
: {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"yourIPisbanned"}}
Job timeout, disconnect, retry in 20 sec...
Any idea

Are you using a special miner ?
Are you overclocking ?

The ban is only temporary. Check your settings.

-------

BTW guys, did you know that the Monero online wallet is released ?
https://mymonero.com/

[Taxidermista]

BTW guys, did you know that the Monero online wallet is released ?
https://mymonero.com/

Yes, and I would be delighted to use it if you could explain this cryptic banner of yours:

Advanced Payment System
The higher you hashrate is, the more often you get pay : 1.6XMR=1H, 0.8XMR=2H, 0.4XMR=4H, 0.2XMR=8H, 0.1XMR=16H.

so stupid persons like me can understand how the hell your payment system works and why my last 0.322 XMR are still stuck in your pool. There must be really really hard to write a f*cking line in your Getting Started page explaining the "system".

[superresistant]

BTW guys, did you know that the Monero online wallet is released ?
https://mymonero.com/

Yes, and I would be delighted to use it if you could explain this cryptic banner of yours:

Advanced Payment System
The higher you hashrate is, the more often you get pay : 1.6XMR=1H, 0.8XMR=2H, 0.4XMR=4H, 0.2XMR=8H, 0.1XMR=16H.

so stupid persons like me can understand how the hell your payment system works and why my last 0.322 XMR are still stuck in your pool. There must be really really hard to write a f*cking line in your Getting Started page explaining the "system".

You are paid every 3-4 hours no matter the amount unless a payment failed.
You can check if the last payment failed here : http://monero.crypto-pool.fr/monit.html look for "failed" on the top right.

Right now the 2 last payments failed, we're on it.

[5w00p]

BTW guys, did you know that the Monero online wallet is released ?
https://mymonero.com/

Yes, and I would be delighted to use it if you could explain this cryptic banner of yours:

Advanced Payment System
The higher you hashrate is, the more often you get pay : 1.6XMR=1H, 0.8XMR=2H, 0.4XMR=4H, 0.2XMR=8H, 0.1XMR=16H.

so stupid persons like me can understand how the hell your payment system works and why my last 0.322 XMR are still stuck in your pool. There must be really really hard to write a f*cking line in your Getting Started page explaining the "system".

Pull the corncob out of your ass. That shit must be in there sideways, you whiny bitch.

[superresistant]

 
Hi guys,

I just released the first version of my One Click Monero Miner, see details here :

https://bitcointalk.org/index.php?topic=613072.msg9758820#msg9758820

[superresistant]

 
Hi folks,

We'll upgrade to a more stable server config soon.
I'll tell you exactly the time later.

See you,

SR

[OrientA]

Hi folks,

We'll upgrade to a more stable server config soon.
I'll tell you exactly the time later.

See you,

SR

Has it been done?

[superresistant]

Hi folks,
We'll upgrade to a more stable server config soon.
I'll tell you exactly the time later.
See you,
SR

Has it been done?

We did it but it was unstable so we rolled back.
We are now fixing the code and testing. It should be finish in 10-12 days.

[dox-ua]

I keep getting
Stratum - connecting to 'xmr.crypto-pool.fr' <212.83.168.41> port 6666
Stratum - Connected
Error in server response
: {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"yourIPisbanned"}}
Job timeout, disconnect, retry in 20 sec...
Any idea

the same thing . kminer or Claimore got the same NEGATIVE result 

[perl]

You can send all communication data add option -P ?
You can connect now ? Or connexion is allways timeout ?

For information , I have attack statum ( all pool is touched ) .
I search best solution for resolve attack

[perl]

[superresistant]

Explanations about the new Monitoring page

State of all bitmonerod
Total Daemons: 12
It is the number of bitmonerod daemon. A daemon is a background process. We use so many for 3 reasons :
1.) Each of those daemon are 12 times less stressed than using only one. It allow the pool to update much faster (getblocktemplate).
2.) If one of them is stuck, it doesn't affect the pool and miners. A bitmonerod process can be stuck for many reasons : busy, fork, too slow, restarting...
3.) Allow the pool to be connected to more nodes on the network.

Total OK: 12
It is the number of daemon online and up-to-date.

Last Monitoring: 15/1/2015 18:01:39.803
The last time all process were checked.

This board under display all details :

Node   Height   Difficulty   Time Check   Previous Block   Error
node9   393244   859128448   15/1/2015 18:01:39.812   1bd5e8d19f746f54   OK
node8   393244   859128448   15/1/2015 18:01:39.812   1bd5e8d19f746f54   OK
node7   393244   859128448   15/1/2015 18:01:39.813   1bd5e8d19f746f54   OK
node6   393244   859128448   15/1/2015 18:01:39.813   1bd5e8d19f746f54   OK
node5   393244   859128448   15/1/2015 18:01:39.816   1bd5e8d19f746f54   OK
node4   393244   859128448   15/1/2015 18:01:39.816   1bd5e8d19f746f54   OK
node3   393244   859128448   15/1/2015 18:01:39.811   1bd5e8d19f746f54   OK
node2   393244   859128448   15/1/2015 18:01:39.811   1bd5e8d19f746f54   OK
node11   393244   859128448   15/1/2015 18:01:39.812   1bd5e8d19f746f54   OK
node10   393244   859128448   15/1/2015 18:01:39.812   1bd5e8d19f746f54   OK
node1   393244   859128448   15/1/2015 18:01:39.814   1bd5e8d19f746f54   OK
node0   393244   859128448   15/1/2015 18:01:39.813   1bd5e8d19f746f54   OK

Node: The daemon nickname.

Height: The blockcount on the blockchain. This data can tell if we are stuck or on a fork.

Difficulty : The actual difficulty.

Time Check: The time of verification.
You can guess the daemon latency by comparing the Last monitoring with the Time check. For example, the node9 daemon has 9 ms ( 18:01:39.812 - 18:01:39.803 ).

Previous Block: The hash corresponding to the last block in the blockchain. It is used as a reference for the current block.

Blocktemplate used for each thread using of mining


You are now aware of most of the data a pool admin is monitoring and you can appreciate the transparency. We believe this make the difference between a good and a bad pool.

With an average time of 60 seconds between each block, finding, processing and sending update to all miners in the shortest possible time is critical. For example, 3 seconds looks small but it represent 5% time lost so 5% less mining gain !

Because of Monero complexity, 2 seconds is already great but we now average 600 ms. Most pools are over 3 secs.

Total Threads: 58 Number of process used to manage all miners.

Average NewJobs: This is the most important for you. It is the average time for miners to get the new job after the discovery of a new block on the network.

Short Average Send NewJobs: It is the shortest average time some miners got the work from the pool.

Long Average Send NewJobs: The longest average...

Thread   Height   Difficulty   Start SendJobs   Duration SendJobs   Previous Block
0988cfe7   393247   863994976   15/1/2015 18:03:29.942   68ms/571ms   4e763aa3.....859e0e79
0cf89fc3   393247   863994976   15/1/2015 18:03:29.533   3ms/97ms   4e763aa3.....859e0e79
....................
fc35f69b   393247   863994976   15/1/2015 18:03:29.778   60ms/399ms   4e763aa3.....859e0e79
ff956901   393247   863994976   15/1/2015 18:03:29.443   27ms/31ms   4e763aa3.....859e0e79

Thread: Unique thread identifier.
Height: Actual block height.
Difficulty: Difficulty.
Start SendJobs: Timestamp for the last block discovery.
Duration SendJobs : The first number is the time for the daemon to send new jobs. The second is the time for the daemon to send new job and discover new block.
Previous Block : The previous block.


The data are not in real time but it's pretty decent.
You'll sometimes see "state of all bitmonerod" give 5 minutes outdated informations.
If you spot bad or old data, try to refresh the page.

[superresistant]

 
Hi,

Be sure you are using xmr.crypto-pool.fr as mining address.

Thanks,

[superresistant]

 
The server update is now complete and everything is fine

[grouper fish]

Hi,

I have some dust stuck at your pool. (0.215076354401 XMR)

Possible to get a manual payout? 

[perl]

Not worry , if you stop mining for 5 day . You are payout all amount if you have more 0.01XMR.

Just need Walt and Not submit share.

[grouper fish]

Not worry , if you stop mining for 5 day . You are payout all amount if you have more 0.01XMR.

Just need Walt and Not submit share.

Last Share Submitted was 15 days ago. 

[perl]

Send my , your address in mp

[grouper fish]

Send my , your address in mp

PM sent, thx

[perl]

Send my , your address in mp

PM sent, thx

Probleme solved for you and many other .
Thank You for find the bug .