Yeah, I agree... you can run tightvnc server on the Pi and access it that way if you don't want to go through the whole VPN server setup.

As has been noted, Eligius is not PPLNS.  I think you might want to do a bit of reading and learn about how PPLNS works.  Your work most certainly does not get "flushed every few hours" as you assert in your post.  Examples:

Kano's pool - your share is counted for 5 times the difficulty.  At the pool's current hash rate, that's about 7.4 days.
p2pool - your share is counted 3 times the difficulty or 3 days, whichever is shorter.
BTCGuild pays for 10 shifts, so about 20 hours.

Sorry... I should have been clearer.  There is no version for the ARM processor of the Pi.  The Linux version is based on the x_86 chipset.  Not sure it'll work... Maybe it'll compile from source?  Haven't tried it myself.

I don't believe there is a teamviewer option for the raspberry pi.

The halving should prove to be quite interesting.  When it went from 50 to 25, there wasn't a whole lot of fanfare... of course, in 2012 there weren't as many players in the market.

That's likely what's happening.  The S3 at standard clock needs 340W from the wall on a decent-rated PSU.  Your 400W PSU probably can't push enough power to the miner.  How many S3s do you have?  I run 3 of them on a single EVGA 1300 G2 and that PSU is rock solid.  Can't say enough good things about it.

You can setup your Pi to be a VPN server so you can remote login to your miners.  It's a bit of work to get it running, but once you do, it's the next best thing to being there .  I'd suggest starting here: http://readwrite.com/2014/04/10/raspberry-pi-vpn-tutorial-server-secure-web-browsing

Great points Phil.  If you've rented a rig and the rig owner bails... either on purpose or by accident, you're refunded for whatever remains on your contract.  If the rig spends more than 20 minutes of the first 30 minutes of your rental offline, the contract is cancelled and you get a full refund automatically.  Otherwise, you've got up until 12 hours after your contract ends to file a dispute (ticket).  Yup, it's a manual process that requires your attention.  Any disputes I've had have always been resolved very quickly (usually less than an hour after I've opened up the ticket).

MRR also allows you to contact the rig owner.  While it's a pretty crude implementation, it does allow you to try and work out any problems on your own.  As a rig owner, I've got the ability to donate time to a renter.  So, let's say I lose my power for an hour or so, I can contact my renter and let him know that I've extended his contract by an hour to compensate him.

Honestly, NH/WH handles this better by just swapping in some other rigs to maintain your order... assuming of course there are any rigs available at your price point.

I like both services, and I definitely think there's a place for them both to coexist in this environment.  Each has their strengths and weaknesses.

The part in bold is wrong.  I assumed you meant blocks, but now that you have stated you didn't then that entire assertion is incorrect.

The shares the miner submits are not "good enough for NMC but not good enough for BTC".  It is in fact that the shares he submitted were counted for both NMC and BTC.  He earned NMC because the shares he submitted were paid out when blocks of NMC were found.  No blocks of BTC were found so he didn't earn any.  When the pool finds a block of BTC, assuming he's got any shares, he'll be paid.

As a gear owner
Using any mining rental site will add latency.  You can't state that MRR does, but you do not.  That's simply a false statement.  For example, if I choose to use WH, I have to point my gear to your pool.  When my gear is rented, it's still pointed (at least from my end) to your pool.  You are redirecting the traffic from there to whatever pool the renter has chosen for his order.

When my gear is not rented, my gear is pointed to whatever backup pool I've set.  With any BitmainTech miner, I've only got 3 pools I can configure via their web interface.  If I'm using WH/NH, 2 of the three slots are taken.  Therefore, I've only got a single pool to which I can point my miners if/when my gear isn't rented.  If that pool happens to go down, my miners are idle.  That's unacceptable.

With MRR, I have the option to set up to 5 pools that my miner can point to.  So, I can set my miners to connect to MRR's servers and still have two possible backups that my gear will fail over to.  Further, I can easily change to which pools my gear is pointing with the click of a button from anywhere.  I can do it while I'm sitting at an airport waiting for my flight.  I can do it from the hotel.  Wherever I want.  And, I don't have to setup any kind of proxy server at my home and expose that.  The convenience of being able to easily remotely monitor my gear and change things on a whim by clicking a button is a far better level of service offered by MRR.

As a gear renter
With MRR, I have the ability to see exactly from where my hashing is being sourced.  If I'm going to mine on a pool that's on the east coast of the US, I don't want gear in China providing the hash because I'm going to have to deal with the latency of hash coming halfway across the planet.  I can also see descriptions of the rigs that will be providing my hash, so I'll know that if, for example, I want to mine on p2pool, I won't pick any Neptune or S2s or Avalon tubes because they either flat out don't work with p2pool or hash at lower-than-advertised rates.

Further, and this is in regards to canceling a rental, sure, you can cancel a rental on WH/NH at any time.  Your rental can also be stopped at any time because somebody decided to pay more than you did, so the gear that was hashing for you is now hashing for somebody else.  With MRR, you've got a contract for a specified time.  That gear is yours.  If I rent gear for a week, I want that gear to be under my control for a week, not wonder if it'll mine for 3 days and then stop and maybe pick back up again 5 days later.

Your case was because it took the network that long to find a block.  OP's case was that he submitted transactions that were not being confirmed even though blocks were being found in the meantime.  As has been noted throughout the thread, the reason was fee-free unconfirmed transactions that were included in the inputs he used, therefore he was forced to wait for those transactions to confirm before his could.

It's not that this miner in particular found the blocks, but rather contributed to the pool's finding of the NMC blocks, and he was awarded some NMC accordingly based upon whatever payment method the pool uses.

Well, p2pool did much better this week with seven day luck of 127.84%.  Also, in the closest race since I've been doing this, p2pool found a block at almost exactly 19:00 UTC.  Looks like it will be included in next week's payout run as it just missed the cutoff by a few seconds.  Because I didn't get to this post until after that block was found, it's influence in the luck is already there... so this week's and next week's luck values might be a bit off because of it.  Like I wrote... it was seconds after the 19:00 cutoff that the block was found.  Both miners beat expected earnings.  NastyPoP was only 101.35%, whereas NastyP2P was 167.63%.

At any rate, here are this week's numbers:

5/1 - 5/8
NastyPoP - 0.03294026BTC
NastyP2P - 0.05447989BTC
Expected - 0.0325BTC
Luck - 127.84%

OP updated

That's what I was suggesting earlier... if NH/WH can provide a warning to the person creating the order if/when they do something like miss a decimal point, that would at least help to assuage the pain.

Nice!  One of my S1s found a block last year in April... unfortunately it was mining on p2pool when it did, so I didn't get the benefit of the solo block.  That's the only BTC block my gear has ever found.  Found plenty of alt-coins while merge mining, though.

Ahh... that's right... it was one of the C1s that found it.

200GH/s found a block on this pool?  Wow!  I thought you were the record holder... wonder if ck.'s got the stats somewhere that could answer us.  In any case, it's great to see solves that run the gamut of hash power pointed here.


Ooops

No idea, but my rig was rented for a week.

I'm pretty sure the limit for pseudo share is 1000, so that's why no matter what value you put above 1000, it will always top out there.  I know there was a commit to the repo a while back that allowed you to set the share-chain share difficulty up in the millions.

I'm pretty sure you hold the record for finding the block with the smallest amount of hash power here as well... block 33 was yours and found with an S2 if I remember correctly.  Total hash rate of your worker that found the block was 2TH/s or so...

You've definitely had some good luck

Oh good... another "I want to print magic internet money and get rich!" thread.  OP, assuming you're even still around, you might want to take a look around the forums a bit and read a few threads to find out whether or not you should even consider getting into mining.  Just coming on and asking for everyone to provide you the answers on how to get rich mining is not going to work.

LOL... obviously the larger the space, the less the impact the S1 will have.  Throw that same S1 into a small closet or a half-bath and you'll notice the heat .  Remember, each S1 is generating about 360W of waste heat running at standard clock speed.