Pages:
Author

Topic: [ANN][AUTO-SWITCH] Profit-switch auto-exchange pool: CleverMining.com - page 64. (Read 554380 times)

full member
Activity: 120
Merit: 100
does clevermining mine LTC if there is no other altcoin that is more profitable?
newbie
Activity: 44
Merit: 0
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

Yep. I have this very same problem. I quit mining Scrypt like 2 months ago, but have left over coin in immature and unexchanged that didn't go anywhere the entire time I quit mining. I got so tired of looking at it I sent 1 CPU core to do some work to see if I can get it taken care of. Hopefully it helps clear it all out so I can get it paid out and move on for good.

I took a screenshot before I started cpu mining and I will take another once I have enough in ready for payout to see if it locks up again with different numbers in immature and unexchanged.
newbie
Activity: 7
Merit: 0
Hi,

I am running a total of 28.522mh/s according to Hashra blade controller (I have 5 grid seed blades) however according to clevermining user stats I am running at 21mh/s

I have been running over 24 hours and can confirm my current stats

28.526 Mh/s current hashrate 28.526 Mh/s avg hashrate 274764 / 11817 Acc./Rej.
4.30 % rejection rate
8526 Hardware errors

Any idea why clevermining is so off?

bobby

Does hashra show "difficulty 1" accepted shares anywhere? If you had that you could calculate how your hashrate looks like based on shares you submitted, which is how the pool calculates it.

Here is a extract


Jul 10 19:09:29 MinerClass log[26808]: 10 PGA(s)
Jul 10 19:09:29 bfgminer[2265]: Accepted 00fe5ff7 GSD 0 Diff 0/0
Jul 10 19:09:29 bfgminer[2265]: Accepted 00c49f04 GSD 7 Diff 0/0
Jul 10 19:09:29 bfgminer[2265]: Accepted 014a805c GSD 6 Diff 0/0
Jul 10 19:09:29 MinerClass log[26808]: Device Details
Jul 10 19:09:30 bfgminer[2265]: Accepted 00bceccf GSD 6 Diff 0/0
Jul 10 19:09:30 MinerClass log[26808]: Summary
Jul 10 19:09:30 MinerClass log[26808]: 1 Pool(s)
Jul 10 19:09:31 bfgminer[2265]: Accepted 00d2809c GSD 8 Diff 0/0
Jul 10 19:09:32 bfgminer[2265]: Accepted 01382f7f GSD 4 Diff 0/0
Jul 10 19:09:32 bfgminer[2265]: Accepted 015c7b5e GSD 6 Diff 0/0
Jul 10 19:09:32 bfgminer[2265]: Accepted 00e712a7 GSD 5 Diff 0/0
Jul 10 19:09:32 bfgminer[2265]: Accepted 01044b53 GSD 6 Diff 0/0
Jul 10 19:09:32 bfgminer[2265]: Accepted 00355cdc GSD 8 Diff 0/0
Jul 10 19:09:33 bfgminer[2265]: Accepted 0105c6f2 GSD 6 Diff 0/0
Jul 10 19:09:34 bfgminer[2265]: Accepted 00e9e23c GSD 4 Diff 0/0
Jul 10 19:09:35 bfgminer[2265]: Accepted 01457a1b GSD 7 Diff 0/0
Jul 10 19:09:35 bfgminer[2265]: Accepted 017faf91 GSD 5 Diff 0/0
Jul 10 19:09:36 MinerClass log[26808]: 10 PGA(s)
Jul 10 19:09:36 bfgminer[2265]: Accepted 00c1a5bc GSD 8 Diff 0/0
Jul 10 19:09:36 MinerClass log[26808]: Device Details
Jul 10 19:09:36 bfgminer[2265]: Accepted 010bf695 GSD 4 Diff 0/0
Jul 10 19:09:36 bfgminer[2265]: Accepted 007e7970 GSD 4 Diff 0/0
Jul 10 19:09:37 bfgminer[2265]: Accepted 00873f83 GSD 0 Diff 0/0
Jul 10 19:09:37 bfgminer[2265]: Accepted 0053863e GSD 4 Diff 0/0
Jul 10 19:09:37 bfgminer[2265]: Accepted 019aa769 GSD 5 Diff 0/0
Jul 10 19:09:37 bfgminer[2265]: Accepted 01162fc0 GSD 5 Diff 0/0
Jul 10 19:09:38 MinerClass log[26808]: Summary
Jul 10 19:09:38 MinerClass log[26808]: 1 Pool(s)
Jul 10 19:09:38 bfgminer[2265]: Accepted 01310332 GSD 7 Diff 0/0
Jul 10 19:09:39 bfgminer[2265]: Accepted 005b8856 GSD 6 Diff 0/0
Jul 10 19:09:39 bfgminer[2265]: Accepted 019233a5 GSD 8 Diff 0/0
Jul 10 19:09:40 bfgminer[2265]: Accepted 00a8fae1 GSD 8 Diff 0/0
Jul 10 19:09:40 bfgminer[2265]: Accepted 01db47ae GSD 8 Diff 0/0
Jul 10 19:09:40 bfgminer[2265]: Accepted 01760cac GSD 1 Diff 0/0
Jul 10 19:09:40 UpdateCache[5164]: 10 PGA(s)
Jul 10 19:09:40 bfgminer[2265]: Accepted 0193cfa2 GSD 8 Diff 0/0
Jul 10 19:09:40 UpdateCache[5164]: Device Details
Jul 10 19:09:41 UpdateCache[5164]: Summary
Jul 10 19:09:41 UpdateCache[5164]: 1 Pool(s)
Jul 10 19:09:41 bfgminer[2265]: Accepted 0089c89e GSD 5 Diff 0/0
Jul 10 19:09:41 bfgminer[2265]: Accepted 001e84d7 GSD 6 Diff 0/0
Jul 10 19:09:41 bfgminer[2265]: Accepted 0139bd06 GSD 4 Diff 0/0
Jul 10 19:09:42 bfgminer[2265]: Accepted 0167625b GSD 6 Diff 0/0
Jul 10 19:09:42 bfgminer[2265]: Accepted 01b421a3 GSD 0 Diff 0/0
Jul 10 19:09:43 bfgminer[2265]: Accepted 002ced7d GSD 9 Diff 0/0
Jul 10 19:09:43 bfgminer[2265]: Accepted 010b5d5e GSD 8 Diff 0/0
Jul 10 19:09:43 bfgminer[2265]: Accepted 01358868 GSD 7 Diff 0/0
Jul 10 19:09:43 bfgminer[2265]: Accepted 016ad641 GSD 8 Diff 0/0
legendary
Activity: 3654
Merit: 8909
https://bpip.org
Hi,

I am running a total of 28.522mh/s according to Hashra blade controller (I have 5 grid seed blades) however according to clevermining user stats I am running at 21mh/s

I have been running over 24 hours and can confirm my current stats

28.526 Mh/s current hashrate 28.526 Mh/s avg hashrate 274764 / 11817 Acc./Rej.
4.30 % rejection rate
8526 Hardware errors

Any idea why clevermining is so off?

bobby

Does hashra show "difficulty 1" accepted shares anywhere? If you had that you could calculate how your hashrate looks like based on shares you submitted, which is how the pool calculates it.
member
Activity: 77
Merit: 10
I think Terk should just amend the policy and say anything below .0005BTC (just throwing a number out there) after fees will be abandoned after a month if the user does not start mining again. I can't see how it's worth the hassle for him and it would certainly cut down on posts about this.

Alternatively, do a once-a-month payment run which clears out any small balances, for users who haven't mined in the last X days.


+1

Totally agreed with your suggestion, murraypaul. This way it'll be good, easy and beneficial for all of us.  Smiley
newbie
Activity: 7
Merit: 0
Hi,

I am running a total of 28.522mh/s according to Hashra blade controller (I have 5 grid seed blades) however according to clevermining user stats I am running at 21mh/s

I have been running over 24 hours and can confirm my current stats

28.526 Mh/s current hashrate 28.526 Mh/s avg hashrate 274764 / 11817 Acc./Rej.
4.30 % rejection rate
8526 Hardware errors

Any idea why clevermining is so off?

bobby
sr. member
Activity: 476
Merit: 250
I think Terk should just amend the policy and say anything below .0005BTC (just throwing a number out there) after fees will be abandoned after a month if the user does not start mining again. I can't see how it's worth the hassle for him and it would certainly cut down on posts about this.

Alternatively, do a once-a-month payment run which clears out any small balances, for users who haven't mined in the last X days.
hero member
Activity: 868
Merit: 1000
I think Terk should just amend the policy and say anything below .0005BTC (just throwing a number out there) after fees will be abandoned after a month if the user does not start mining again. I can't see how it's worth the hassle for him and it would certainly cut down on posts about this.
member
Activity: 77
Merit: 10
0.00088230BTC is hardly worth it after the wallet/exchange fees. You're going to be left with like .00058 that's worth a whopping 36 cents or so. This is really crying over spilled milk.

I'm NOT talking about the current balance. I had a balance approx. of 0.00088230BTC left with CM for more than a month, and was not paid! Any answer to that? Smiley I think whatever balance is left should be paid(manually, if it doesn't meets the set threshold) to a miner in full(especially if the miner quits at your pool & asks for it{continuously!}), isn't it? I've seen some cases like this at CM. I didn't ask for it as it didn't matter to me much.

P.S. As the "stuck balance" topic is again discussed, I said what I experienced. Smiley
hero member
Activity: 868
Merit: 1000
0.00088230BTC is hardly worth it after the wallet/exchange fees. You're going to be left with like .00058 that's worth a whopping 36 cents or so. This is really crying over spilled milk.
member
Activity: 77
Merit: 10
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. Smiley

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.

I'm NOT talking about the current balance. I had a balance approx. of 0.00088230BTC left with CM for more than a month, and was not paid! Any answer to that? Smiley I think whatever balance is left should be paid(manually, if it doesn't meets the set threshold) to a miner in full(especially if the miner quits at your pool & asks for it{continuously!}), isn't it? I've seen some cases like this at CM. I didn't ask for it as it didn't matter to me much.

P.S. As the "stuck balance" topic is again discussed, I said what I experienced. Smiley
jr. member
Activity: 34
Merit: 5
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
sr. member
Activity: 420
Merit: 250
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
jr. member
Activity: 34
Merit: 5
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. Smiley

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.
member
Activity: 77
Merit: 10
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. Smiley
jr. member
Activity: 34
Merit: 5
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
sr. member
Activity: 420
Merit: 250
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?
newbie
Activity: 13
Merit: 0
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...
legendary
Activity: 840
Merit: 1000
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?
sr. member
Activity: 252
Merit: 250
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
Pages:
Jump to: