Author

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

newbie
Activity: 42
Merit: 0
what does 'rejected untracked stratum share from pool 0' mean? all my reject is showing this message.
member
Activity: 93
Merit: 10
sg server!? SWEET! is it up?? can I point and use it yet??  Cheesy
legendary
Activity: 2128
Merit: 1005
ASIC Wannabe
my GPU rig cannot seem to handle a set difficulty of 512. on other pools at 128 or 256 it runs fine on all 4 cards, but at 512 GPU 2 is declared sick in less than 30 seconds

any ideas? its a sapphire R9 270x

That is odd. Hard to say without more information about your setup. If only GPU 2 is failing, it sounds like a thermal problem. Try jacking your fan up to 100 as a test. Of course it could be a myriad of other issues: not enough power, drivers, even monitor setup or could just be a bad card. Pure assumptions here.

turns out a reboot did the trick for whatever reason. I had a similar issue before on another card where i was seeing only about 60-80% of the expected hashrate

however, some of these low-difficulty coins are wrecking havoc on my reject rate - 7-12% for the last little while, mostly whenever it switches to coins with network difficulty <50
newbie
Activity: 48
Merit: 0
Same for me. I'm waiting for EU. There is already eu.clevermining.com (nl.clevermining.com) responding for ping, but it's probably not ready to use.

Yay! Finally 60ms and not 250+ Tongue

asia server in singapore

Pinging sg.clevermining.com [128.199.227.18] with 32 bytes of data:
Reply from 128.199.227.18: bytes=32 time=133ms TTL=49
Reply from 128.199.227.18: bytes=32 time=134ms TTL=49
Reply from 128.199.227.18: bytes=32 time=130ms TTL=49
Reply from 128.199.227.18: bytes=32 time=135ms TTL=49

Ping statistics for 128.199.227.18:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 130ms, Maximum = 135ms, Average = 133ms

what happened ?

Pinging us.clevermining.com [54.200.13.55] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 54.200.13.55:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

are the servers up yet terk ? as far as i could remember, ping for me to usa server & sg server is almost same. seems like usa server is slightly better.


110ms to sg.clevermining.com
nice!!
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
Same for me. I'm waiting for EU. There is already eu.clevermining.com (nl.clevermining.com) responding for ping, but it's probably not ready to use.

Yay! Finally 60ms and not 250+ Tongue

asia server in singapore

Pinging sg.clevermining.com [128.199.227.18] with 32 bytes of data:
Reply from 128.199.227.18: bytes=32 time=133ms TTL=49
Reply from 128.199.227.18: bytes=32 time=134ms TTL=49
Reply from 128.199.227.18: bytes=32 time=130ms TTL=49
Reply from 128.199.227.18: bytes=32 time=135ms TTL=49

Ping statistics for 128.199.227.18:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 130ms, Maximum = 135ms, Average = 133ms

what happened ?

Pinging us.clevermining.com [54.200.13.55] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 54.200.13.55:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

are the servers up yet terk ? as far as i could remember, ping for me to usa server & sg server is almost same. seems like usa server is slightly better.

yrj
newbie
Activity: 20
Merit: 0
I just checked 30 days stats and realized, that there're some unexchanged bitcoins from, for example, 2nd of February. It was a long time ago. Does it mean that miners would never get those money?
newbie
Activity: 40
Merit: 0
my GPU rig cannot seem to handle a set difficulty of 512. on other pools at 128 or 256 it runs fine on all 4 cards, but at 512 GPU 2 is declared sick in less than 30 seconds

any ideas? its a sapphire R9 270x

That is odd. Hard to say without more information about your setup. If only GPU 2 is failing, it sounds like a thermal problem. Try jacking your fan up to 100 as a test. Of course it could be a myriad of other issues: not enough power, drivers, even monitor setup or could just be a bad card. Pure assumptions here.
newbie
Activity: 31
Merit: 0
Is normal the first payment takes longer ?
I have more than 0.02 btc and nothing...

http://www.clevermining.com/users/14DuKiay4rGiYSqjkRdMtWtu7oaRpiipkc#
legendary
Activity: 2128
Merit: 1005
ASIC Wannabe
my GPU rig cannot seem to handle a set difficulty of 512. on other pools at 128 or 256 it runs fine on all 4 cards, but at 512 GPU 2 is declared sick in less than 30 seconds

any ideas? its a sapphire R9 270x
newbie
Activity: 40
Merit: 0

Vardiff does not matter for profits. It helps lower short term variance on stats and smooths out results for lower power rigs. That is why it exists. Again, profits are not effected by it.
And do you honestly care about stats? I rarely check the website. I just leave my computer on and let my 0.01 bitcoin payouts roll in multiple times a day. I would rather have Terk working on actual useful things like new servers, instead of making stats 2% more accurate.

Exactly.
hero member
Activity: 588
Merit: 500
Get ready for PrimeDice Sig Campaign!


Sure vardiff matters, the guy just doesn't understand.

Vardiff does not matter for profits. It helps lower short term variance on stats and smooths out results for lower power rigs. That is why it exists. Again, profits are not effected by it.
[/quote]
And do you honestly care about stats? I rarely check the website. I just leave my computer on and let my 0.01 bitcoin payouts roll in multiple times a day. I would rather have Terk working on actual useful things like new servers, instead of making stats 2% more accurate.
newbie
Activity: 19
Merit: 0
did we have an brief outage? my fail over kicked in

Same here, switching pools makes one of my machines crash.. anyone else have that problem?
newbie
Activity: 59
Merit: 0
did we have an brief outage? my fail over kicked in
member
Activity: 81
Merit: 10
Same for me. I'm waiting for EU. There is already eu.clevermining.com (nl.clevermining.com) responding for ping, but it's probably not ready to use.

Yay! Finally 60ms and not 250+ Tongue
full member
Activity: 307
Merit: 102
so i take it the new once a day pay system is in effect? the one where if you have more than 0.001 when pay out hits then you get paid instead of the rolling payouts ?

just noticed your response above disregard  Grin

It's not in effect yet, but payouts for balances 0.001 BTC has been sent just an hour ago. We always had a weekly payout for 0.001 balances on Sunday 0:55am UTC.

oh i see i didn't account for that , that explains the payouts awesome.
hero member
Activity: 616
Merit: 522
so i take it the new once a day pay system is in effect? the one where if you have more than 0.001 when pay out hits then you get paid instead of the rolling payouts ?

just noticed your response above disregard  Grin

It's not in effect yet, but payouts for balances 0.001 BTC has been sent just an hour ago. We always had a weekly payout for 0.001 balances on Sunday 0:55am UTC.
full member
Activity: 307
Merit: 102
so i take it the new once a day pay system is in effect? the one where if you have more than 0.001 when pay out hits then you get paid instead of the rolling payouts ?

just noticed your response above disregard  Grin
hero member
Activity: 616
Merit: 522
Terk, I appreciate your response about changing the way the payout system will function. The main issue I have with it is the fact that when the small payouts go out I have anywhere from 0.04xxx - 0.06xxx still in my "wallet". I only receive a small portion out of that amount - 0.1xxx or so. I hope you change the way the payouts work when you do a single payment a day. It would be even more frustrating to see a single payment go out at say 9PM, and then see 0.04xxx - 0.06xxx balance still on my account which would carry over the next day, and start all over again.

I don't think that's the case. On every payout, all of the payable balance is paid. If you have 0.06 payable balance, then 0.06 is paid. If you have 0.06 total expected balance, but only 0.01 payable and 0.05 immature+unexchanged, then of course only payable balance is paid.
hero member
Activity: 616
Merit: 522
After receiving a payout on the 27th I left to mine some new alt for a few days.

Upon returning here at my stats

Immature   0.00007900 BTC
Unexchanged   0.00053781 BTC
Ready For Payout   0.00124554 BTC
Total Expected   0.00186235 BTC

Why do I still have immature and unexchanged funds?

After 48+ hours shouldn't everything be matured/exchanged and moved into ready for payout?

Unexchanged: we have some trades made on Feb 21st to 24th on an exchange that went later offline (coinmarket.io). This is nothing to worry as we managed to withdraw most of our funds before it went offline - I try not to keep balance on exchanges and withdraw multiple times per day (I think we got back like 90% of what we sent there, but I need to check). I just need to manually process list of trades on this exchange and enter them into our database. With all the crazy tech stuff that's been going on in the recent days, I just didn't have time for any non-critical stuff. I plan to process it after launching new servers, on Sun/Mon. You can see these amounts on a 30-day profits page and I highlighted them in this screenshot: https://i.imgur.com/EfTXaw1.png

And I repeat: most of these coins are already exchanged and BTC are withdrawn from the exchange. But these were manual trades as the exchange didn't have an API and I need to fetch them to our database manually. I didn't have access to trades list as the exchange was offline, but it went online for a short period of time two days ago and I downloaded transactions list. I'll process it soon.

Immature: On the same page/screenshot you can see immature balance by day. Having immature in last 4 days is nothing unusual, especially with weak coins which difficulty went high after couple coin-switching pools jumped on them and then left. As you can see these balances aren't high, it's less than 1% of our total profits three days ago. We just need to wait and they'll eventually mature.

We also have some near-dust immature balances from previous days, like 0.0039 BTC from Feb 21st or 0.0176 BTC from Feb 16th. I'll look into this within next few days, when I will be processing manual trades from the exchange that went down.
hero member
Activity: 616
Merit: 522
I think it does. Otherwise tuning vardiff would not exist.
On wemineltc I am receiving various difficulties ranging from 64 to 600 depending on the particular rig's hashing power.
Taking into account that there is only one server in US and reject ratio is high due to latency I suspect that that it matters even more.
Currently i see across all rigs that difficulty is set to 512. Might be hard coded value.

Since clevermining is still in development I wonder what is Terk's opinion.

Should we use separate btc addresses for each mining rig?!
Is he working on sub-workers. Like for example "btcaddress_worker1"?!
Or should we just use one address for all of them?!

What is Terk's preference on this?

Lack of vardiff doesn't affect your profits if you're in for a long term. Vardiff enabled reduces variance, so you will earn your share even if only mining for an hour. With vardiff disabled your variance can be high and if you want to mine for only an hour, you might get a significantly higher or lower profitability than the pool average, depending on your miner's luck during this hour. If you mine for a day or longer though, it will all even out - some hours will be lucky, some unlucky, but at the end of the day your daily results will be the same as if you had vardiff enabled.

Vardiff helps only reducing variance and making you feel better as you see consistent results every hour. It doesn't help anything else. So it's not really my priority as I have lots of other more urgent things to implement. If you understand that your daily results are not affected, you shouldn't panic seeing your reported hashrate going up and down every hour.

You can use the same or different addresses for each rig - it's up to you. If you need to track individual rigs results then using separate addresses is currently an only option. If you don't need that, it's probably more convenient for you to just use one address.

Sub-workers feature is on my nice-to-have todo list. It has even lower priority than re-enabling vardiff.
Jump to: