[ANN] profit switching auto-exchanging pool - www.middlecoin.com

[twotimer]

You're connecting to port 3333?

Yep, didn't change a thing in the config which used to work until recently.

Didn't see any announcements here or on the main page at middlecoin.com either, did I miss something?

[1714851834]

1714851834

[1714851834]

1714851834

[1714851834]

1714851834

[1714851834]

1714851834

[1714851834]

1714851834

[Eastwind]

any advice how to get better numbers?
http://www.middlecoin.com/reports/1NZ3JiWLfvwi7J8AFaYZqYQHGSU7wRB9UW.html

I'm having 5% stales but i see enough people don't having this problem.

Running 4x 7950 cards

My config =
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "120",
"hotplug" : "5",
"kernel-path" : "/usr/local/bin",
"log" : "5",
"queue" : "1",
"scan-time" : "30",
"scrypt" : true,
"shares" : "0",
"gpu-threads" : "1",
"gpu-dyninterval" : "7",
"gpu-engine" : "1100,1100,1100,1050",
"gpu-fan" : "60-85,60-85,60-85,60-85",
"gpu-platform" : "0",
"gpu-memclock" : "1500,1500,1500,1450",
"gpu-memdiff" : "0",
"gpu-powertune" : "20,20,20,20",
"gpu-vddc" : "1.081",
"intensity" : "19,20,20,19",
"temp-target" : "78",
"temp-overheat" : "83",
"temp-cutoff" : "86",
"temp-hysteresis" : "3",
"vectors" : "1",
"worksize" : "256",
"lookup-gap" : "2",
"shaders" : "0",
"thread-concurrency" : "21712",
"no-pool-disable" : true

Reduce the intensity to 18 and increase TC to 24000.

[Freekje]

eu stratum is down ?

[mpdas108]

eu stratum is down ?

Seems to be going on and off recently...

[kirtap]

eu stratum is down ?

i've been having problems with all the stratums so something is going on

[arandy]

any advice how to get better numbers?
http://www.middlecoin.com/reports/1NZ3JiWLfvwi7J8AFaYZqYQHGSU7wRB9UW.html

I'm having 5% stales but i see enough people don't having this problem.

Running 4x 7950 cards

My config =
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "120",
"hotplug" : "5",
"kernel-path" : "/usr/local/bin",
"log" : "5",
"queue" : "1",
"scan-time" : "30",
"scrypt" : true,
"shares" : "0",
"gpu-threads" : "1",
"gpu-dyninterval" : "7",
"gpu-engine" : "1100,1100,1100,1050",
"gpu-fan" : "60-85,60-85,60-85,60-85",
"gpu-platform" : "0",
"gpu-memclock" : "1500,1500,1500,1450",
"gpu-memdiff" : "0",
"gpu-powertune" : "20,20,20,20",
"gpu-vddc" : "1.081",
"intensity" : "19,20,20,19",
"temp-target" : "78",
"temp-overheat" : "83",
"temp-cutoff" : "86",
"temp-hysteresis" : "3",
"vectors" : "1",
"worksize" : "256",
"lookup-gap" : "2",
"shaders" : "0",
"thread-concurrency" : "21712",
"no-pool-disable" : true

Reduce the intensity to 18 and increase TC to 24000.

tnx i'll try that and see what it does

[cycobilly]

eu stratum is down ?

i've been having problems with all the stratums so something is going on

yeah, useast looks down too.

[Catswold]

Right now, your best bet is to just use the default middlecoin.com URL for mining.  useast is down and apparently eu is down as well.

[KS]

any advice how to get better numbers?
http://www.middlecoin.com/reports/1NZ3JiWLfvwi7J8AFaYZqYQHGSU7wRB9UW.html

I'm having 5% stales but i see enough people don't having this problem.

Running 4x 7950 cards

My config =
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "120",
"hotplug" : "5",
"kernel-path" : "/usr/local/bin",
"log" : "5",
"queue" : "1",
"scan-time" : "30",
"scrypt" : true,
"shares" : "0",
"gpu-threads" : "1",
"gpu-dyninterval" : "7",
"gpu-engine" : "1100,1100,1100,1050",
"gpu-fan" : "60-85,60-85,60-85,60-85",
"gpu-platform" : "0",
"gpu-memclock" : "1500,1500,1500,1450",
"gpu-memdiff" : "0",
"gpu-powertune" : "20,20,20,20",
"gpu-vddc" : "1.081",
"intensity" : "19,20,20,19",
"temp-target" : "78",
"temp-overheat" : "83",
"temp-cutoff" : "86",
"temp-hysteresis" : "3",
"vectors" : "1",
"worksize" : "256",
"lookup-gap" : "2",
"shaders" : "0",
"thread-concurrency" : "21712",
"no-pool-disable" : true

You can also remove the following lines:
"shares" : "0", = will stop submitting shares after an infinite number of shares (i.e. never) = default behavior, so no need for this line.
"gpu-dyninterval" : "7", = used with dynamic intensity. you're using fixed intensity -> not needed.
"gpu-memdiff" : "0", -> works with "auto-gpu" -> does nothing like that + you have specified fixed GPU+RAM speed -> not needed.
"vectors" : "1", -> not used for scrypt mining -> does nothing.
"shaders" : "0", -> overridden by thread-concurrency -> not used.

[the_unholy_grail]

Why is useast and EU so unstable over the past 24 hours? Really cutting into the profits 

[MrBobC]

Let's say we have lots of rigs and typed our payout address incorrectly for one of them and it now has a balance of 0.2BTC.  How would I go about getting this sent to the correct address?  2 of the characters were switched.

[gsrcrxsi]

Why is useast and EU so unstable over the past 24 hours? Really cutting into the profits 

Then set the default uswest server as a backup/failover.

If you're pool mining without multiple failover pools, you're doing it wrong.

[the_unholy_grail]

Why is useast and EU so unstable over the past 24 hours? Really cutting into the profits 

Then set the default uswest server as a backup/failover.

If you're pool mining without multiple failover pools, you're doing it wrong.

I do have multiple failover pools but the ping for uswest is too damn high.

[Ioqua]

Teach me for not having three failover pools 

[artiface]

Let's say we have lots of rigs and typed our payout address incorrectly for one of them and it now has a balance of 0.2BTC.  How would I go about getting this sent to the correct address?  2 of the characters were switched.

You probably don't.  If payments were sent to an address you don't control, they will be lost.  Bitcoin payments are not reversible.

[MrBobC]

Let's say we have lots of rigs and typed our payout address incorrectly for one of them and it now has a balance of 0.2BTC.  How would I go about getting this sent to the correct address?  2 of the characters were switched.

You probably don't.  If payments were sent to an address you don't control, they will be lost.  Bitcoin payments are not reversible.

Yes, but I don't see where a payout actually happened.  1MmBUf6KDTQsNGBEyrsxrTFNCbCT1vtTEK should have been 1MmBUf6DKTQsNGBEyrsxrTFNCbCT1vtTEK.  I don't see any payouts for the first one though, just a balance of 0.2.

[Catswold]

Send a PM to h2o with all the info.  IF it can be corrected, he will do so.  It appears that you were lucky and the address to which you directed it is no currently a legitimate BTC address, so the coin remained in your balance.

Oh, and now you know why you should always use copy and paste for your wallet addresses rather than manually typing them in.

[JCviggen]

Let's say we have lots of rigs and typed our payout address incorrectly for one of them and it now has a balance of 0.2BTC.  How would I go about getting this sent to the correct address?  2 of the characters were switched.

You probably don't.  If payments were sent to an address you don't control, they will be lost.  Bitcoin payments are not reversible.

It's very very very (VERY) unlikely to create a valid address with typos.

That said, typing addresses is a bad idea, always copy/paste.

[gsrcrxsi]

Teach me for not having three failover pools 

My pool/failovers are:
1. Middlecoin useast
2. Middlecoin uswest
3. Hashcows
4. Poolerino EAC pool

As a result, no cut in to profits. I never even get to pool 3/4. They are there just in case. Also ping is really inconsequential. Blocks aren't found fast enough for an extra 100ms lag to really make much difference.

Furthermore, afaik useast is BETA. Expect 50% uptime and be grateful for more. Along those same lines, uswest is non-beta, so expect 98% uptime and grateful for more.

You have no one to blame but yourself for your high expectations and poor mining practices. If you think you can make more elsewhere (lol), there's the door. Good luck.

[fyff]

So eu and useast as a failover didn't work out going to be adding a third pool for failover