[ANN][AUTO-SWITCH] Profit-switch auto-exchange pool: CleverMining.com

[Schinder75]

Are there currently problems with auto payout? I'm mining for 4 days now, not even one payout is triggered. Current balance is about 0.01 btc.
Or do I missed something like minimum payout or something else?

[UdjinM6]

Are there currently problems with auto payout? I'm mining for 4 days now, not even one payout is triggered. Current balance is about 0.01 btc.
Or do I missed something like minimum payout or something else?

Make sure it's over 0.01 or just wait till the end of the week

Btw, it's right in the OP and on About page http://clevermining.com/about

Daily Payouts with 0.01 BTC minimum payout balance.
Additional weekly payout for small balances (0.001 BTC).

[Schinder75]

Are there currently problems with auto payout? I'm mining for 4 days now, not even one payout is triggered. Current balance is about 0.01 btc.
Or do I missed something like minimum payout or something else?

Make sure it's over 0.01 or just wait till the end of the week

Btw, it's right in the OP and on About page http://clevermining.com/about

Daily Payouts with 0.01 BTC minimum payout balance.
Additional weekly payout for small balances (0.001 BTC).

Ah ok, thanks for information. I just missed it. Balance is very short under minimum payout, so it should trigger in the near future.

[coinflow]

I'd also say, that this is the main problem.

It works like this:
The miner is working on a coin, while the pool already switched to another coin. The miner submits the done work to the pool and the pool answers: "Don't give me these results, they are no longer valid, because we are already working on another coin", throws it into the bin, and the submitted work is not counted for your REAL hashrate (the "pool-hashrate"). That explains the difference between what the mining-software shows and what the clevermining-website displays.

This isn't the case at CleverMining. When we switch to a new coin, all old work for previously mined coins is still valid and will be accepted (until there is a new block at these other coins which will obviously invalidate the work). This is the reason why you should never use --no-submit-stales at coin-switch pool. We do things the smart way and always accept work for previously mined coins. (if we didn't, rejected percentage would be an order of magnitude higher).

OK, if it works like you describe, why are there massive break-ins in the hashrate from time to time, which causes a really severe lowering of the overall hashrate?
On other pools, that don't switch, it doesn't occur. If all submitted work counts, a drop in hashrate should not even be the case, when the pool switches to the next coin.

[edonkey]

CM's hashrate is now nearly 75 GH/s! Maybe KnC is "testing" their Titans...

The conspiracy theory has always been that mining companies suck up coin until the difficulty pushes the hardware to break even, then they offload the hardware on us. As much as I hate it, it does seem to be a smart business practice.

[Terk]

I'd also say, that this is the main problem.

It works like this:
The miner is working on a coin, while the pool already switched to another coin. The miner submits the done work to the pool and the pool answers: "Don't give me these results, they are no longer valid, because we are already working on another coin", throws it into the bin, and the submitted work is not counted for your REAL hashrate (the "pool-hashrate"). That explains the difference between what the mining-software shows and what the clevermining-website displays.

This isn't the case at CleverMining. When we switch to a new coin, all old work for previously mined coins is still valid and will be accepted (until there is a new block at these other coins which will obviously invalidate the work). This is the reason why you should never use --no-submit-stales at coin-switch pool. We do things the smart way and always accept work for previously mined coins. (if we didn't, rejected percentage would be an order of magnitude higher).

OK, if it works like you describe, why are there massive break-ins in the hashrate from time to time, which causes a really severe lowering of the overall hashrate?
On other pools, that don't switch, it doesn't occur. If all submitted work counts, a drop in hashrate should not even be the case, when the pool switches to the next coin.

Because some users are switching between coin-switch pools if temporary pool results/luck is lower than usual, while people mining at a single-coin pools don't do this. Some people don't understand that even coin-switch pools have their variance and good/bad luck and it's best to pick the best pool based on long-term results (or other features/qualities you like) and stick to it.

(because if the pool has good results in the long term, then a worse than average period will be followed by better than average period and you will be fine in the long term if you stay. If you switched away after worse than average period you will miss the better than average period and your total results won't be as good as if you didn't switch away)

[rodeoclownicp]

any news on stuck balances?

[papoboy]

any news on stuck balances?

+1

[imall4btc]

CM is paying alright know, or there are payout issues?  

Thanks

P.S. Just switched my 5.5mH/s G-Blade to CM.

[cyberpitstop]

any news on stuck balances?

+1

+1

[Viturrex]

Registered just for this 

First off, thanks for a great pool. Been on it since Feb, and so far so good - keep up the great work.

Any chance we could see an option for payout in LTC? (similar to say ghash or coinking or hashcows)

Quite a few of your miners I'm sure are using scrypt asics, and as such, a payout option of LTC would be quite useful. It will also serve as a very useful force to help drive up LTC value, as a massive pool like clevermining, creating exchange pressure for all sort of alt coins --> LTC would create a much needed demand for LTC.

You should of course still keep the option for BTC payout, for those that wish it so.

Thanks again for all your effort on this pool - much appreciated

[rodeoclownicp]

terk about 3 weeks ago u mentioned u were going to go through stuck balances- i saw a few
+1 refering to that topic- please respond

[coinflow]

I'd also say, that this is the main problem.

It works like this:
The miner is working on a coin, while the pool already switched to another coin. The miner submits the done work to the pool and the pool answers: "Don't give me these results, they are no longer valid, because we are already working on another coin", throws it into the bin, and the submitted work is not counted for your REAL hashrate (the "pool-hashrate"). That explains the difference between what the mining-software shows and what the clevermining-website displays.

This isn't the case at CleverMining. When we switch to a new coin, all old work for previously mined coins is still valid and will be accepted (until there is a new block at these other coins which will obviously invalidate the work). This is the reason why you should never use --no-submit-stales at coin-switch pool. We do things the smart way and always accept work for previously mined coins. (if we didn't, rejected percentage would be an order of magnitude higher).

OK, if it works like you describe, why are there massive break-ins in the hashrate from time to time, which causes a really severe lowering of the overall hashrate?
On other pools, that don't switch, it doesn't occur. If all submitted work counts, a drop in hashrate should not even be the case, when the pool switches to the next coin.

Because some users are switching between coin-switch pools if temporary pool results/luck is lower than usual, while people mining at a single-coin pools don't do this. Some people don't understand that even coin-switch pools have their variance and good/bad luck and it's best to pick the best pool based on long-term results (or other features/qualities you like) and stick to it.

(because if the pool has good results in the long term, then a worse than average period will be followed by better than average period and you will be fine in the long term if you stay. If you switched away after worse than average period you will miss the better than average period and your total results won't be as good as if you didn't switch away)

I think, you did not understand what I meant. I wasn't referring to the overall hashrate of the whole clevermining-pool including all users, but the single hashrate of one user.
Why is it dropping, if you count each and every submitted share even of the previous mined coins, after the pool switched? If it was like this, the hashrate could not drop from let's say 80 MH/sec to 60 MH/sec. for some time (sometimes 5 minutes or more), right?

[PEARSON1FIED]

I think it's not fair when BIG players come to this pool with their Powerful mining hardware which costs at least 10.000$ and suck up all coins. Need  to add some limitations for BIG players (or for example add extra pool fee 7% - 10% for them)...pool hashrate is too high...and that's not fair for small miner owners...

[gtraah]

Why does this pool Not pay out your remaining coins!!!! HOw many times do people have to say the same thing over and over and OVER.... Soon as you stop mining and you have more than 0.01 even as high as 0.02 Left over! But because you stop mining these coins do not get paid.

Is this some sort tactic to clean up EVERYones left over coins after they stop mining here?

[roshii]

Why does this pool Not pay out your remaining coins!!!! HOw many times do people have to say the same thing over and over and OVER.... Soon as you stop mining and you have more than 0.01 even as high as 0.02 Left over! But because you stop mining these coins do not get paid.

Is this some sort tactic to clean up EVERYones left over coins after they stop mining here?

Auto payment system works as a charm on Clevermining, I never had a single issue.
Balance above 0.001 BTC are paid weekly, and daily if above 0.01 BTC
I stop mining every now and them and I always get my balance paid out.

Most likely your BTC address is wrong, but only pool admin can say...

Success

[imall4btc]

Hey, I think pool doesn't pays stuck balances. I had something like 0.00088230 BTC left over for a month here but I never got paid.

P.S. I've started mining at CM again though.

[roshii]

Hey, I think pool doesn't pays stuck balances. I had something like 0.00088230 BTC left over for a month here but I never got paid.

P.S. I've started mining at CM again though.

Threshold for weekly payment is at 0.001 BTC.
Your balance was slightly below which is why you did not got paid.

I assume that a lower threshold would be inefficient since transaction fee would "eat" most of the stuck balances.

[gtraah]

My address is fine I have mined a few bitcoins here and no issue with address when I stop I Definitley get stuck change In Unexchanged and Immature for more than 1 week and all together its more than 0.01 my address is 10000% fine,  I started mining again here today will see what happens when I stop again.. I am not the only one with that problem a few pages back me and another few guys having the same issue

[roshii]

OK, I get your point now. I never noticed that behaviour but will pay attention during my next mining pause.
That shouldn't happen indeed