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

[Arux]

very strange. 

time to reply and now



is there a little bug ?

the block n°123954 is also counted 20x 

and what's mean "NB submit"?

[superresistant]

http://www.hostingpics.net/viewer.php?id=116397monero.jpg][IMG]http://img4.hostingpics.net/pics/116397monero.jpg
very strange. 
time to reply and now
http://www.hostingpics.net/viewer.php?id=610891monero2.jpg][IMG]http://img4.hostingpics.net/pics/610891monero2.jpg
is there a little bug ?
the block n°123954 is also counted 20x 
and what's mean "NB submit"?

Some blocks where counted xx times yes. It was a display bug.
We remove them manually.

NB submit is the number of bitmonerod process submitting blocks. The bug that we found was on bitmonerod so we switched everyone on one bitmonerod that was working, restarted the others and resynced the blockchain.

[perl]

To day and last night .
Pool as touch by big bug in bitmonerod .

When pool get blocktemplate 2/4 bitmonerod add transactions already spend in blocktemplate .
When you find block all bitmonerod 4/4 rejec block because transaction already spend  .

For fix at after speek core team .
I have delete all blockchain and poolstate of 3/4 bitmonerod
And start full resynch for 3/4 bitmonerod .

And restart the last bitmonerod with blockchain valide and fiability

The bug of display is create by one of 4 bitmonerod as accept block ( not full resync ans not ).
When  bitmonerod is resync . bitmonerod accept all block


 It is not possible to lose block submitted if bitmonerod not work ( I submit to 4 bitmonerod and repush block for 5 secondes if not accepts for all ).

I have lost blocksubmitted to night only block submitted contain transaction already spend .
You can look now . All is OK .


Submit is the number of bitmonerod as accepted block
( 1/4 only one as accepted block )
( 2/4 halh as accepted and other half reject )
( 3/4 only one asreject block )
( 4/4 all bitmonerod as accepted block )

Without configuration 4 bitmonerod for same incident/bug to night
The pool found nothing block for more than 12H ( I have found 3/5 block )

[onetwentyfive]

I noticed that I'm getting WAY more shares accepted, though they are all of a much lower target diff than I usually get. Right now they're 7500, earlier they were 10000. Usually my 7970 rig submits shares in the 50000-100000 range. Is this something to do with the new diff adjustments you were talking about?

Also the overall pool mh/s is down to just over 1mh/s, error in hashrate reporting?

Once in a while I'm getting this error:

Error in server response
: {"id":1,"jsonrpc";"2.0","error":{"code":-1,"message":"Unauthenticated"}}

then it reconnects and resumes as usual, just wanted to let you know 

Still a great pool!

[superresistant]

I noticed that I'm getting WAY more shares accepted, though they are all of a much lower target diff than I usually get. Right now they're 7500, earlier they were 10000. Usually my 7970 rig submits shares in the 50000-100000 range. Is this something to do with the new diff adjustments you were talking about?
Also the overall pool mh/s is down to just over 1mh/s, error in hashrate reporting?
Once in a while I'm getting this error:
Error in server response
: {"id":1,"jsonrpc";"2.0","error":{"code":-1,"message":"Unauthenticated"}}
then it reconnects and resumes as usual, just wanted to let you know  
Still a great pool!

Yes we changed the difficulty settings.
Apparently some miners got disconnected during the change.
We wait for all of them to reconnect.
We'll wait for a day and see if we get an improvement.

We deleted the history of blocks to start calculation from zero.


------

What diff would you like ?

[perl]

You can defined diff with address 

Add per ex +1428 for get fidd to 50.000
1428*35 = 50.000

[2014-07-12 21:06:21] > {"method": "login", "params": {"login": "48THv.......................................................................... ...5F4xk+1428", "pass": "x", "agent": "cpuminer-multi/0.1"}, "id": 1}
[2014-07-12 21:06:21] < {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"855269159097224","job":{"blob":"0100f98d869e059a2c67575a9d6422435546373a9fffbe1d6c615366d957fbea15ff89d7ec18510 00000008be987036033f73991803cc7b4c5424e8b8b47fb4655f6a89a8532f757a2505706","job_id":"552922042296268","target":"ad4f0100"},"status":"OK"}}
[2014-07-12 21:06:21] Pool set diff to 49980.4

[onetwentyfive]

I noticed that I'm getting WAY more shares accepted, though they are all of a much lower target diff than I usually get. Right now they're 7500, earlier they were 10000. Usually my 7970 rig submits shares in the 50000-100000 range. Is this something to do with the new diff adjustments you were talking about?
Also the overall pool mh/s is down to just over 1mh/s, error in hashrate reporting?
Once in a while I'm getting this error:
Error in server response
: {"id":1,"jsonrpc";"2.0","error":{"code":-1,"message":"Unauthenticated"}}
then it reconnects and resumes as usual, just wanted to let you know  
Still a great pool!

Yes we changed the difficulty settings.
Apparently some miners got disconnected during the change.
We wait for all of them to reconnect.
We'll wait for a day and see if we get an improvement.

We deleted the history of blocks to start calculation from zero.


------

What diff would you like ?

I'm not quite sure honestly.. It really depends on the power correct?

my spare pc gets 1025h/s with 2x7970 my main pc gets 688h/s with 2x270x and 268h/s with my i7 4820k

What would you recommend?

[onetwentyfive]

You can defined diff with address 

Add per ex +1428 for get fidd to 50.000
1428*35 = 50.000

[2014-07-12 21:06:21] > {"method": "login", "params": {"login": "48THv.......................................................................... ...5F4xk+1428", "pass": "x", "agent": "cpuminer-multi/0.1"}, "id": 1}
[2014-07-12 21:06:21] < {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"855269159097224","job":{"blob":"0100f98d869e059a2c67575a9d6422435546373a9fffbe1d6c615366d957fbea15ff89d7ec18510 00000008be987036033f73991803cc7b4c5424e8b8b47fb4655f6a89a8532f757a2505706","job_id":"552922042296268","target":"ad4f0100"},"status":"OK"}}
[2014-07-12 21:06:21] Pool set diff to 49980.4

that's greek to me boss lol i'm all up for fiddling with setting but i dont even know where to begin with all that! 

[onetwentyfive]

Also i think the payments are stuck.. i havent received anything since 8:41am EST (almost 10 hours ago)

[perl]

The wallet is broken. ( all coin is safe )
Juste deleted .bin and rebuild wallet-pool.bin
I finish rebuild in 5 minutes

The Last payout of pool is 18H  ( 4 hour to go )

[onetwentyfive]

Received thank you

[superresistant]

So it has been over 24h since our last update and we are doing very well according to the block we find.
http://monero.crypto-pool.fr/#pool_blocks vs http://moneropool.com/#pool_blocks
What is strange is that the efficiency is not over 100%
That mean one thing : the total hashrate estimation is wrong.
http://monerochain.info/charts/hashrate
It say 12M but I think that it is at least 10% less.

Anyway we're doing well. Thanks for mining.

[perl]

For efficient with only 50 Blocks
http://monero.crypto-pool.fr/index2.html

Just one big periode without chance .

Pool Efficiency: 97% now
Pool Efficiency: 90% 12 Hours a go
Pool Efficiency: 95% 1 Hours a go

[onetwentyfive]

So it has been over 24h since our last update and we are doing very well according to the block we find.
http://monero.crypto-pool.fr/#pool_blocks vs http://moneropool.com/#pool_blocks
What is strange is that the efficiency is not over 100%
That mean one thing : the total hashrate estimation is wrong.
http://monerochain.info/charts/hashrate
It say 12M but I think that it is at least 10% less.

Anyway we're doing well. Thanks for mining.

I was just about to say, the pool seems to be doing very well. On average I usually make 2.5-3 XMR a day and I made 1.6 in the last 8 hours! With another .5 already in the last 2 hours, whatever you did, it's working. Thanks!

[xa4]

Small question : how do you calculate the 'network hash rate' ?
I thought it was 'Diff/60', but that's not what I see on the pool's mainpage (neither on other pools' mainpage) What formula are you using ?
Thx. 
 

[superresistant]

Small question : how do you calculate the 'network hash rate' ?
I thought it was 'Diff/60', but that's not what I see on the pool's mainpage (neither on other pools' mainpage) What formula are you using ?
Thx. 

It is the same as here : http://monerochain.info/charts
Shows the estimated hash rate on each day. The approximate mining hash rate (in H/sec) at a given point of time can be obtained by taking the difficulty and dividing it by 60.

The thing is that there is some time between each difficulty adjustment so the network hashrate can never be accurate.

[superresistant]

 
ducknote.crypto-pool.fr just opened.

Same features as monero.crypto-pool.fr :
High Efficiency - Ultra Stability - Advanced Payment System ( transaction ID for every payment + adaptive minimal payout ) - Firewall pass through - both HTTP & stratum available

EDIT :
LOL pool efficiency 390% (ducknote.crypto-pool)
So bad ass    

EDIT : Promotion for the ducknote pool

[superresistant]

 
Tonight we are doing a small update (with no restart, no downtime, no worry).
You will not be able to see the history of payment for few hours but you'll still get paid as usual.

[Shrikez]

Hi,

I've been mining happily at your pool for a long time now so props for that.

However recently I started getting only 10k targets on all rigs. Is that supposed to work like that? In earlier times target was increasing to much higher numbers.

What am I missing?

Thanks!

[superresistant]

I've been mining happily at your pool for a long time now so props for that.
However recently I started getting only 10k targets on all rigs. Is that supposed to work like that? In earlier times target was increasing to much higher numbers.
What am I missing?
Thanks!

That's normal. After many tests, we found out that this target is the best.

If you would like to change it.
Add +hashrate to your address like this :
stratum+tcp://xmr.crypto-pool.fr:6666+1000
for 1 KH/S
stratum+tcp://xmr.crypto-pool.fr:6666+500
for 500 H/S