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

[superresistant]

It seems you have made a manual transfer for the difference as I don't see the txid in my recent payments. Thank you very much for resolving the issue!

Yes I did a manual payment for you because it would take me too much time to do it from the pool with adding amount in the database.

----

If anyone still missing XMR, please PM me your address + missing XMR.

Right now I'm going to sleep so I'll pay you tomorrow when I wake up so don't panic please !

Thanks.

[5w00p]

Pm'd the pool dev and my issue was taken care of.

Thanks, superresistant!

[tema-proc]

Best POOL Ever. Thank you guys.

[superresistant]

Problem with payments at  address

Hi tema-proc,

I just did a manual payment for you.

Please remove or edit your message in the pool thread so the issue is resolved.

Regards,

SR

[hellojdk]

thx pool master.i found it.

[nuxxer]

love this coin, but how this coin in future? #next 1-2 year

[superresistant]

love this coin, but how this coin in future? #next 1-2 year

With Monero, it feels like mining Bitcoin at the beginning but everything goes very fast.
I started mining Monero on my laptop the first days. The gain was ridiculous at the time but now it is worth more than the computer I was using.

You have to be strong to believe in it, mine it and hold it long enough.

[Techone]

Hi guys,

I am new to the forum and pool, so first: HI to everyone!

I started mining a few days ago on crypto-pool.fr and I works like a charm.
However, I got a slight problem with my hashrate.

My miners show ~ 21kh/s combined with TSIVs Nvidia ccminer for monero. I use the Nvidia GTX 750 Ti cards, 6 per board, 1650 H/s total per miner.
But the pool only shows ~ 15 kh/s, daily payment is also adding up to 15 kh worth of hashrate.

Does anyone else got this problem with tsiv´s ccminer? I tried several precompiled windows binaries, directly from Tsiv´s Github account. There is around 20% difference between the hashrate shown by the miner and the one shown by the pool.

There are no rejected shares shown at the miner, all accepted. Can anyone help?

[superresistant]

Hi guys,
I am new to the forum and pool, so first: HI to everyone!
I started mining a few days ago on crypto-pool.fr and I works like a charm.
However, I got a slight problem with my hashrate.
My miners show ~ 21kh/s combined with TSIVs Nvidia ccminer for monero. I use the Nvidia GTX 750 Ti cards, 6 per board, 1650 H/s total per miner.
But the pool only shows ~ 15 kh/s, daily payment is also adding up to 15 kh worth of hashrate.
Does anyone else got this problem with tsiv´s ccminer? I tried several precompiled windows binaries, directly from Tsiv´s Github account. There is around 20% difference between the hashrate shown by the miner and the one shown by the pool.
There are no rejected shares shown at the miner, all accepted. Can anyone help?

There are 3 mains reasons :

 - The hashrate displayed on the pool is only an estimate and vary.
 - The hashrate displayed on the miner software is also an estimate and is calculated differently on every miner software.
 - The pool only take count of the accepted-shares to calculate the hashrate BUT the miner count the bad-shares / stale-shares.

The pool only see what you successfully send and dismiss the bad-shares. The miner, don't know if a share is going to reach the pool or not, neither it knows if the share will turn into a bad-share / stale-share.

You should not worry about the hashrate. Ask other miners what are the best miner software and the best settings.
Compare how much XMR you get per 24h depending on software and settings.

Be careful about overclocking ! It greatly increase the bad-shares ratio and reduce your gain.

[Techone]

As far as I can tell the ccminer does validate (checking if the result can be considered good) the share before submitting.

CCminer shows "yayy!" or "boo!". If I enter wrong settings or overclock hard the miner shows "result does not validate on CPU" or something like that, so I assume I submit only valid shares. Most of them should also reach the pool, because I got several AMD based cards running on your pool too and the hasrate and payout fits just perfect. (at the same location and connection)

On ccminer however there is always a 20% cut in hashrate displayed and payment received.

I watched some posts from tsiv here. Tsiv, if you read this, maybe you have further help or ideas where to look.
Or anyone else using tsivs miner, since it is the only one for monero and Nvidia cards right now.

[equipoise]

^You could try the result of -l MxN option with different M and N. Here are some hints in a previous post of mine:

Strange result.
[2014-06-26 15:30:13] Using JSON-RPC 2.0
[2014-06-26 15:30:13] 1 miner threads started, using 'cryptonight' algorithm.
[2014-06-26 15:30:13] Starting Stratum on stratum+tcp://mro.extremehash.com:7777
[2014-06-26 15:30:13] GPU #0: GeForce GTX 285, using 40 blocks of 8 threads
[2014-06-26 15:30:13] GPU #0: GeForce GTX 285, 12200.23 H/s
[2014-06-26 15:30:14] Pool set diff to 5000
[2014-06-26 15:30:14] Stratum detected new block
[2014-06-26 15:30:14] GPU #0: GeForce GTX 285, 2845422.95 H/s
[2014-06-26 15:30:37] Stratum detected new block
[2014-06-26 15:30:37] GPU #0: GeForce GTX 285, 3259881.74 H/s
[2014-06-26 15:31:22] Stratum detected new block
[2014-06-26 15:31:22] GPU #0: GeForce GTX 285, 3474958.52 H/s

Compute 1.3 definitely won't work...

It's making windows to think the driver crashed because it's taking long enough without returning a result (windows default is 2 seconds for the GPU) and that's why windows restarts the driver and ccminer won't work and show you impossible hash rate. I made the timeout 40 seconds on my machine (tried with 10 first - it worked for some time, but then it crashed again). This made my laptop second nvidea card to start happily mining with about 22 H/s. Don't do this if you don't have a second video card, because your PC will become completely unusable while mining (if you are cpu mining on the same machine run the cpu miner before running the gpu miner, because otherwise it'll become difficult for you to even start the cpu miner). Here is a link to a .reg file, which will set the timeout to 40 seconds - just double click it and it'll add the setting to the registry (it'll ask you if you are sure). Then you should restart your windows and ccminer should work after the restart. If you find it useful don't forget to tip me https://www.dropbox.com/s/ci8b3h7oxtvd6dq/TdrDelaySetTo40.reg

Thank you for this. Going with the same OC on my 780 Ti I applied this and now I'm getting 350-360 using 6x120. I can play with the numbers a bit without crashing now. The best I've been able to do is 6x120 with higher hashrates. There is definitely a sweet spot you have to find. Hey it's better than what my i5 was doing for sure now.

There is something more to be done about the -l MxN.
About the first number M:
"First of all, your thread block size should always be a multiple of 32, because kernels issue instructions in warps (32 threads). For example, if you have a block size of 50 threads, the GPU will still issue commands to 64 threads and you'd just be wasting them."
About the second number N:
You could find it by gradually increasing it until your card stop working (showing impossible hash rate 3474958.52 H/s) and then restart is needed for maximum performance (but not for testing), because without restart my hash rate is felling 2x compared to the same options before the crash.

The "magical numbers" for 650M seems to be -l 128x5

XMR tip: 4AyRmUcxzefB5quumzK3HNE4zmCiGc8vhG6fE1oJpGVyVZF7fvDgSpt3MzgLfQ6Q1719xQhmfkM9Z2u NXgDMqYhjJVmc6KX
Thank you!

[perl]

Techone,

Send me your address for look on log off pool .
If you are sure all share is valid is not possible you have 20% less .

You can 20% less and 5 minute after 20% more not 20% all time.

[BLanKa]

Hi. Pending balance it's stuck. ¿will we ever see the coins we are mining today? ¿should we stop mining asap? (at least until monero devs fix their code)

[superresistant]

Hi. Pending balance it's stuck. ¿will we ever see the coins we are mining today? ¿should we stop mining asap? (at least until monero devs fix their code)

We are all in the same boat.
We wait for the devs to tell us what to do.

Here is the first update from devs :

2014/08/04 Attack: Update 1
Here's what we've ascertained thus far: the "bad block" occurred at 202612. Immediately thereafter there was 202613, which also has oddities, and then at 202614 the network forked. The "A" part of the network has "c29e3dc37d8da3e72e506e31a213a58771b24450144305bcba9e70fa4d6ea6fb" as the block hash on 202614, the "B" part of the network has "ed4eea6109a1b662cf4a3bb372ed4bdee588160b0ac371c2ad78c5e603b8f2ac" as the block hash on 202614. Ultimately the "A" part won, and is the current fork. The "B" part is dead and has not proceeded beyond block 202647.

Thus the good news is that the consensus code works, and only one fork has survived. The bad news is that those on the bad fork are not reorganising back to the fork, and that is something we will need to look at fixing in future - the consensus code is so aggressive that it refuses to believe that the peers on the "good" fork are correct.

To determine if you are on the good or the bad (dead) fork, you can check "diff" in your daemon window. If you are stuck on 202647 or thereabouts, you will need to delete your blockchain and sync from scratch. I strongly suggest using the blockchain bootstrap downloads from the OP, as those are on the correct fork. Please note that the Windows blockchain bootstrap download has not been checked and updated as yet, I will be doing so in the next few hours, so we have rolled back to a Windows blockchain from a few weeks back. The Linux and OS X blockchain bootstraps are fine.

The next step is to determine how, exactly, 202612 & 202613 managed to cause this, which is what we've been doing concurrently and will continue to do. You can use Monero with caution if you are on the main chain, we will continue to update as we proceed.

NB: no funds have been lost, and there will be no blockchain rollback. If you transacted on the dead fork it was only live for about 35 minutes, so chances are little happened of relevance. Once you are on the good fork you can re-sync your wallets and any funds you sent on the dead fork will reappear.

According to block datas, monero.crypto-pool.fr is not stuck on the fork (block 202976)

The monero block explorer is stuck on the fork : http://monerochain.info/ (block 202648)


EDIT : Don't pay attention to the orphaned block from the block page. The block page take informations from the monero block explorer but this explorer is on the wrong fork. Our blocks are not orphaned.
You can safely keep mining. The payments will resume soon.

[BLanKa]

According to block datas, monero.crypto-pool.fr is not stuck on the fork (block 202976)

The monero block explorer is stuck on the fork : http://monerochain.info/ (block 202648)


EDIT : Don't pay attention to the orphaned block from the block page (http://monero.crypto-pool.fr/#pool_blocks). The block page take informations from the monero block explorer but this explorer is on the wrong fork. Our blocks are not orphaned.
You can safely keep mining. The payments will resume soon.

OK, understood.

I guess the pending balance it's not updating because the pool is holding payments as a precaution, just in case there is another fork or some other problem, right? (i'm not complaining, just curious)

[superresistant]

According to block datas, monero.crypto-pool.fr is not stuck on the fork (block 202976)
The monero block explorer is stuck on the fork : http://monerochain.info/ (block 202648)
EDIT : Don't pay attention to the orphaned block from the block page (http://monero.crypto-pool.fr/#pool_blocks). The block page take informations from the monero block explorer but this explorer is on the wrong fork. Our blocks are not orphaned.
You can safely keep mining. The payments will resume soon.

OK, understood.
I guess the pending balance it's not updating because the pool is holding payments as a precaution, just in case there is another fork or some other problem, right? (i'm not complaining, just curious)

We are waiting for Poloniex to resume trading.
We want to be sure we are all on the same chain.

It is no use to resume payment if there are no active trading.

EDIT : I am asking Poloniex to resume trading on the chat.

EDIT2 :
from IRC #monero-dev
[14:16:16] <superresistant> are we garanted that there will be no rollback ?
[14:16:26] <superresistant> can the pool operators resume payment ?
[14:17:03] <fluffypony> superresistant: yes - one 70kb bad block doesn't mess the entire chain up irrevocably
[14:17:08] <fluffypony> and we're way past it anyway

We are resuming.

EDIT3:
Payment resumed.

[perl]

Efficiency off pool off last day ( 30 Hour )
Efficiency: 107.34% pour 386 Blocks

All is ready for continue

[ray88]

Can we increase the minimum threshold payment its starting to be expensive all these small payment with .1 fees!

[superresistant]

Can we increase the minimum threshold payment its starting to be expensive all these small payment with .1 fees!

We pay the 0.1 XMR fee from the pool to your wallet.
As a pool, we can pay over 100 people in one transaction with the same 0.1 fee.

If you are worried about sending from your wallet to the exchange, you can wait to have more XMR on your wallet or simply wait for the devs to lower the fees.

[ray88]

Can we increase the minimum threshold payment its starting to be expensive all these small payment with .1 fees!

We pay the 0.1 XMR fee from the pool to your wallet.
As a pool, we can pay over 100 people in one transaction with the same 0.1 fee.

If you are worried about sending from your wallet to the exchange, you can wait to have more XMR on your wallet or simply wait for the devs to lower the fees.

thanks thats fine with me