What happened with PC (X11)?

Nm, end of POW apparently.

merc82, can you clarify about the btc/mhash/day numbers:

On the site it says they have been adjusted to scrypt mhash..

on this thread you mentioned somebody multiplying by 3 to get the correct profit ratio...

Which is it, or am I confused?

Basically i'm trying to figure out if it's worthwhile to switch to x11.
(which for some reason I can only get less than 2x my normal scrypt rate from, I am assuming this has to do with drivers,
anybody have a known-working setup for 7950s to get 3x the scrypt rate?)

Nvm...

Somewhat related, what coin has a diff of 100 right now? 

Besides a communication channel, we need some kind of feedback or rating system between renters/leasers. Like others have mentioned, "hash verified" would also be a good designation to have.

I'm sure the to-do list is already getting pretty big and eventually all desired features will be added in.

Wow, intriguing service. Will give it a try. Can't wait to see all the features implemented, it should only get better.

Only thing I don't like is that there is a single point of failure for trust as far as the coinage goes. Needs to be instant and transparent like leaserigs, ideally.

Since I remember some people on this thread talking about how easy scrypt mining was, I figured I should link this up: http://www.devtome.com/doku.php?id=the_myth_of_the_lazy_miner

http://www.devtome.com/doku.php?id=the_myth_of_the_lazy_miner

Unless you're running a single gpu, get ready for some involvement...

This. ++

Gee, I wish I wasn't the only person having the issue where I can only stay connected for 20 minutes at a time before stratum starts dumping shares into the void.

Meanwhile other pools still work just fine, and my configuration never changed.

Extremely odd and frustrating.

Alright, I am done dumping my money into a black hole.

I hope that's enough information to fix this crazy-ass bug.

Let me know if you fix it?

Here's something else that is odd, however, that I just realized.

Even as any trace of "accepted' or "rejected" disappears after those first 20 minutes, the WU doesn't just plummet, as it would if nothing at all was really being submitted. Instead, the WU does it's usual thing- goes down some, goes up some, fluctuates as normal.

So it *appears* that for some extremely frustrating reason, the report and display goes offline after that first period of time, but continues to function afterward in the background. Will have to confirm this.

Extremely confusing. Any ideas h2o? I didn't touch a thing until I started having this issue, so I can't think of how it isn't something weird on the server side causing it, but who knows.

[EDIT]

So just letting one rig ride 'in the dark' for a while resulted in this another half hour or so later:

Pool 0 stratum share submission failure
Stratum connection to pool 0 interrupted
Lost 61 shares due to stratum disconnect on pool 0
Pool 0 difficulty changed to 1024
Pool 0 communication resumed, submitting work
Stratum connection to pool 0 interrupted
Lost 1 shares due to stratum disconnect on pool 0
Pool 0 difficulty changed to 1024

And then it's back to Accepted/Rejected shares.

The plot thickens?

[Second addition]

I let another rig do the same thing as the first, and the exact same thing happened, down to the same number of shares lost: 61 and 1.

Extremely curious indeed. What evil bug is it that I stalk here?

Oh, and third rig just popped at 61 and 1 shares lost. Beyond coincidence, now.

This still isn't the case for me. After the 20 minutes or so of regular, a-ok hashing, it just goes into no-man's land.

Catch 22 there.

Nope, it's not that.

Er... how about the feature of staying on the most profitable coin?

From what I can see, WDC ain't it right now, but the cows are on it.

Doge would be much better...

Logic error?

I believe everything was running smooth with 1024 difficulty for at least a few hours, anyway. My overall WU actually went up slightly with that change. Okay, checking into it- looks like everything was actually fine for almost an entire day. Issue began occurring shortly after the payout for the 17th (Jan. 18, 2014, 2:36 a.m.) My own configuration did not change at all during this time.

Cgminer continues to chug away as normal, except it no longer has accepted shares. No rejects, no nothing. Diff changes appear as usual, new blocks are detected as usual, etc- it just keeps hashing away, but entirely futilely. Not an "Accepted" or "Rejected" in sight. (Oddly, once in a while there is still "stale share detected, submitting as user requested", even though there wasn't an actual share to do that with.)

As I normally have cgwatcher set to restart cgminer if more than 2 minutes go by with any accepted or rejected shares, I can watch via the logs the extreme regularity by which it happens, every 20 minutes or so.

Still having shares stop submitting after ~20 minutes like clockwork. No actual freeze with cgminer, just shares no longer get submitted at all, even as it continues to hash away.

Is no one else experiencing this? It's not on my end, I ruled out pretty much every variable, tried different versions of cgminer, et al. Something had to have changed server side, and it affects uswest, useast, and eu at the least (I didn't try asia). Tried a different address- same deal.

Meanwhile testing on other pools and it's fine. Hashcows for instance has no issues as far as this symptom goes.

Since last night, and all during the night, my rigs have all been stalling out every 20 minutes like clockwork. That is, everything is working fine, hashing away, but suddenly no shares will be accepted after ~20 minutes or so of normal function. Cgwatcher eventually reboots cgminer, even though cgminer didn't freeze and is to all appearances still hashing away. Config hasn't changed on my end and was previously working great.

So I conclude it's gotta be server issues. I end up with a ~12% loss of hashrate because of this.

Something else...

Useast (possibly others, haven't tested) started acting up this evening. Share submission will randomly stall out on a rig here and there. Sometimes again and again pretty rapidly.

Hashrate as reported by the server down 25%. I assume due to constant rebooting after x minutes of no shares (via cgwatcher.)