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

[juggs]

<snip>
Clearly he is targetting the poor and weak!  He is a modern day Pol Pot!  

*hums "Holiday in Cambodia" by The Dead Kennedies*
</snip>

For this sir, you win the internet for the day! Purely because it reminded me of that track, and now I too am humming it....

It's a holiday in Cambodia
Where people dress in black
A holiday in Cambodia
Where you'll kiss ass or crack

[The Fat Miner]

Toss in a scammer accusation and a referral to SimonG's mythical pay-to-play invitation-only pool, and I believe I'm good  

H20 haz been stealing my 0.65 M/Hz hash rate and you LOZERS!1! are all followen' him blindly.

DON'T YOU SEEZ THE GRAPHESSSSS!!!

DON'T YOU!!!!



AS you can CLEARLY SEE, my 0.65 M/Hz hashz rate is NO WHERE TO BE SEEN

H20!!!! THEIFFFFF

WHERE'Z MY BITCOIN!!!!!

Sounds about right lol

[dgross0818]

As pointed out above, the difference between your local hashrate (what you see on your rigs) and the rate reported on Middlecoin (or any 3rd party graph) is due to your "luck" in the number of shares your workers solve

If I have a card that is hashing at 600 kH/s, I can expect it to solve a block of X difficulty in time T (the concept is way more important than the numbers in this example)

Sometimes that card will get "lucky" and solve the block a lot faster than "average"... other times it may take 5 times as long to solve a block of the same difficulty

I have a laptop with a pretty lame hashrate of 135 kH/s... with a pool difficulty of 1024, it "should" solve a share every 7-8 minutes or so (It's late and I probably messed that up) however, I've had times when it solved in 2 min, and others when I've gone 15 minutes without an accepted share.

When your cards solve blocks faster than "normal" your hashrate can actually be reported higher than it actually is, as all Middlecoin is doing is counting the number of accepting shares over a period of time, factoring in the difficulty, and then spitting out the hashrate that corresponds.

With a low pool difficulty of 64 (for example) you can expect to submit roughly 16 times the number of shares vs a pool with difficulty 1024.

In statistics, we use the Law of Large Numbers to explain how as the number of samples increases, the average result should converge, with a variance decreasing to 0 as the number of samples gets infinitely large.

With a lower diff pool, you are submitting enough shares, even with a "slower" rig that the hashrate should be fairly accurate over a period of time as short as an hour or two. When you combine a slower rig with a high-dif pool like MC, the hashrate can be over or under reported drastically when the sample time is so short.

This is why we keep saying please compare your daily average hashrate to what your miners are reporting locally. Obviously if your uptime is less than 24 hours you will need to multiply the local hashrate by (hours up during past 24 hours / 24) (The fraction of time the rig was online)

If you are still seeing an issue, then it's most likely due to not factoring in the shares you lost through stales/rejects. If it's still wrong, then most likely your WU units are substantially lower than your reported hashrate, potentially due to a bad graphics card config, latency, wrong server, crows nesting nearby, etc

[The Fat Miner]

So your saying the hash rate is irrelevant , It's the shares submitted, Ok any pointers on how to increase my efficiency levels ?

It's not irrelevant. There is a direct correlation between hash rate and shares submitted. More hash rate, more shares, higher payout.

If you deconstruct it, payout is measured by shares.  Shares, however, are not measured by hashrate.  To give you a reading, pool operators provide a metric that shows you what hash rate on average would submit the shares at the rate in which your miner is currently submitting shares.  

Efficiency levels?  Get your stales and rejects down.  I don't know why they are so high on this server.  H20 doesn't know either last time I checked, and that is much more important for him to work on than to explain to everyone on here how mining works.  

The graphs on Middlecoin are based souly on shares submitted ? Because that would give me an idea why I've lost "Power" if you like , So no ideas on how to reduce rejects ? Because I'm sure I don't , I've tried everything, Lowering intensity, Clocks, All sorts of settings.

[The Fat Miner]

As pointed out above, the difference between your local hashrate (what you see on your rigs) and the rate reported on Middlecoin (or any 3rd party graph) is due to your "luck" in the number of shares your workers solve

If I have a card that is hashing at 600 kH/s, I can expect it to solve a block of X difficulty in time T (the concept is way more important than the numbers in this example)

Sometimes that card will get "lucky" and solve the block a lot faster than "average"... other times it may take 5 times as long to solve a block of the same difficulty

I have a laptop with a pretty lame hashrate of 135 kH/s... with a pool difficulty of 1024, it "should" solve a share every 7-8 minutes or so (It's late and I probably messed that up) however, I've had times when it solved in 2 min, and others when I've gone 15 minutes without an accepted share.

When your cards solve blocks faster than "normal" your hashrate can actually be reported higher than it actually is, as all Middlecoin is doing is counting the number of accepting shares over a period of time, factoring in the difficulty, and then spitting out the hashrate that corresponds.

With a low pool difficulty of 64 (for example) you can expect to submit roughly 16 times the number of shares vs a pool with difficulty 1024.

In statistics, we use the Law of Large Numbers to explain how as the number of samples increases, the average result should converge, with a variance decreasing to 0 as the number of samples gets infinitely large.

With a lower diff pool, you are submitting enough shares, even with a "slower" rig that the hashrate should be fairly accurate over a period of time as short as an hour or two. When you combine a slower rig with a high-dif pool like MC, the hashrate can be over or under reported drastically when the sample time is so short.

This is why we keep saying please compare your daily average hashrate to what your miners are reporting locally. Obviously if your uptime is less than 24 hours you will need to multiply the local hashrate by (hours up during past 24 hours / 24) (The fraction of time the rig was online)

If you are still seeing an issue, then it's most likely due to not factoring in the shares you lost through stales/rejects. If it's still wrong, then most likely your WU units are substantially lower than your reported hashrate, potentially due to a bad graphics card config, latency, wrong server, crows nesting nearby, etc

So what you're saying is I'm an unlucky bastard ? 

[juggs]

I was saying something is wrong with the pool but nobody cared, now i see people are reporting the same problem i was reporting on Sunday  . let me guess your cgminer stats doesn't add up with the MC pool?!     

I gave up trying to figure it out, i even messaged h20 but he didn't give a fuck about it since there are lot of other pigs around to rob from. It feels like your cgminer submits the shares to h20's personal address 

I even tried to mine for 24hours with a new address, guess what the new address never showed in the database  , all in all h2o is robbing you without knowing it

here is my earlier post on Sunday,

then any cares to explain this to me???  what's happening here because i can't make a sense of it

https://i.imgur.com/sOXh1KW.jpg

and this ..

How did you get 1.5 milliion shares accepted and 45000 shared rejected in 15 hours at 1024 diff with 2 MH/s? Looks like your miners switched to other pool(s) while you weren't watching.

Probably not a different pool, just a screwed up config somewhere. I've done it myself, forget to include the right --scrypt setting on a card or two and they start reporting crazy high hash rates locally while submitting nothing but nonsense to the pool. It's easily done. And also easily corrected with some diligence.

[Damnsammit]

So what you're saying is I'm an unlucky bastard ?  

Blissfully ignorant, too.  

*popcorn*

[The Fat Miner]

So what you're saying is I'm an unlucky bastard ?  

Blissfully ignorant, too.  

*popcorn*

Seriously speaking though, I am starting to learn, Thanks to everyone for the advice, Including dgross0818 and yourself.

[aclass]

The easiest way to lower rejects is to ping each one of the servers and choose 2 or 3 with the lowest ping... Add the lowest as primary and the other as failover-only.

Wait for an hour and then monitor your miner to see what's the percentage of rejected shares. Rotate the servers above if needed until you get it.

AND NEVER USE WIRELESS ... unless you can not mine otherwise

[ckoeber]

AND NEVER USE WIRELESS ...

+1

Especially on a wireless network you do for generic surfing.

If you MUST use a wireless network; get a separate router and have it on a separate channel with a completely different IP setup, etc. to reduce broadcast traffic.

[Ioqua]

Really you think Wireless has that much effect? maybe I should go by some power-line plugs as there's no other reasonable way to get ethernet to the garage lol

[ckoeber]

Really you think Wireless has that much effect? maybe I should go by some power-line plugs as there's no other reasonable way to get ethernet to the garage lol

Power-line is even worse; don't know how your home is situated but if there is truly no standard wired Ethernet option you can do then the separate wireless network ( a decent N-based router on a separate channel/SSID) will give you better results than a Power-Line...

[uozer]

my balance seems to have flatlined despite my 1MH for the last 2 days. and i didnt receive any payouts.

anyone having the same?

[Ioqua]

my balance seems to have flatlined despite my 1MH for the last 2 days. and i didnt receive any payouts.

anyone having the same?

You sure you haven't mistyped your wallet address or something?

[aclass]

Really you think Wireless has that much effect? maybe I should go by some power-line plugs as there's no other reasonable way to get ethernet to the garage lol

Huge difference for me even when the rig is the room next to the router... Not an N network but just one wall away ...

[arbuzzinho]

guys, if u have problems with config, check out this site
you might find config u need
www.cgminer-config.com

[The Fat Miner]

The easiest way to lower rejects is to ping each one of the servers and choose 2 or 3 with the lowest ping... Add the lowest as primary and the other as failover-only.

Wait for an hour and then monitor your miner to see what's the percentage of rejected shares. Rotate the servers above if needed until you get it.

AND NEVER USE WIRELESS ... unless you can not mine otherwise

I had the it pointed at the asia server but was losing loads of shares due to disconnects, So Its now pointed at the default server which has a very high ping, Don't have much chance, It keeps losing shares due to disconnects.

[aclass]

What are your pings to useast eu and amsterdam?

The easiest way to lower rejects is to ping each one of the servers and choose 2 or 3 with the lowest ping... Add the lowest as primary and the other as failover-only.

Wait for an hour and then monitor your miner to see what's the percentage of rejected shares. Rotate the servers above if needed until you get it.

AND NEVER USE WIRELESS ... unless you can not mine otherwise

I had the it pointed at the asia server but was losing loads of shares due to disconnects, So Its now pointed at the default server which has a very high ping, Don't have much chance, It keeps losing shares due to disconnects.

[The Fat Miner]

What are your pings to useast eu and amsterdam?

I've not tried the Amsterdam sever yet, But i imagine it will be similar to the others because I'm in Asia, For the love of god I wish the Asia server come out of beta.

You think its worth trying the Amsterdam server? I was getting around 330ms pings to the one in Ireland, Very similar pings to all the others except Asia which is around 67ms

(Edit , Just pinged Amsterdam, 413ms average)

[Oden]

tbh, I had given up to figure out this bizarre issue with my hashrate & stats started on late Sat and had switched to another, since I couldn't not explain as why this is happening.  I mean i see cgminer and cgwatcher reporting shares being submited regardless of being accepted or rejected and I knew the address was correct ( god sake is a copy and paste and had checked many times) but yet I couldn't get any stats reports from either MC or any third party programs. even put up those screen shots so maybe someone might be able to explain better as to what's happening, also tried to mine with a new address for at least 12hrs to see anything changes but nothing change same thing, cgminer reports submitting shares & etc...

I was pretty darn sure that the issue was not on my side, since I had checked every point of failure I could have thought of it at my peak moment of frustration , hence it got me suspicious of the pool on Monday. So today I jumped into accusing h2o prematurely since I couldn't explain it any other way and also saw few people reporting similar problems. But arguing  with you guys today got me curious as to why this has happened and got  me interested again to try to figure this out, could have simply walked away from it and not waste any time.

so finally decided to take the rig down, delete both cgminer and cgwatcher, flush the dns, clean %appdata%, reset the router & cable box. Made a fresh bat file and ran straight it from cgminer ( without cgwatcher) on the same old address just to test it.

 being doing its thing for roughly an hour and woala....

 middlecoin or any other reporting stats sits are reporting back correctly. I'm confused as hell, at the same time feel ashamed for accusing h2o ( my apologies). first thing first, I take back everything i said about robbing, the issue was on my side all along even though i don't know if it was a bug or a hack. still wondering where the shares being submitted to

kudos to you sir!!