Yes... i was wondering if anyone can shed any light on why the hiked the price so high on the second batch when the ROI has gone so much lower after release of first batch?   Anyone have ideas?   Just because they can ? 

Ive been working on making this project more relevant again... not sure where it will lead yet

Im working on it

This is the still the official and original source link without any third party taints or fixes:

http://mmcfe.mfis.net/
or
svn co svn://svn.mfis.net/mmcfe

All very good points, Vladimir.  I do find it interesting to keep an eye on whats happening though especially with the first 300 units now out there.  Time will tell, as always.

Im still lurking!   Looking at the new ASIC offerings and getting very tempted to jump back in and play some more even though i know ill be too late for the easy ROI

Is that so?  That kind of surprises me... I always that usability was nice and stats were pretty but i seem to remember alot more overal features abvailable from deepbit and btcguild

Vladimir!

haha good to hear!   I fired up the old MMC servers today to see if could re-purpose them and then i got stuck digging through the old code remembering the "old days".   AFter more than 6 months downtime,  i still have miners trying to connect to the servers when i brought them up again.  Someone is really not paying attention to their boxes (legitimate or not).

So hows life?   How many of you MMC'ers are still mining bitcoin?

You guys should have left my README intact and read it and understood it.  Some of those github projects ive seen are mangling good code because of lack of knowledge of how its supposed to work.  A couple points to those considering to use what ive seen on github:

1) linking to absolute webroot files as in '/index.php' is part of a security policy and running this software in a sub-directory is NOT recommended.  Just because is works doesnt mean its right.
2) adding .php extensions throughout the code is a shame and not needed.  Follow the README instructions!

The original source without mods is here:

http://mmcfe.mfis.net/

Anni

1) you never set a threshold for auto payments.  It was still set at 0 which means its turned off.  If you would have read the instructions you would have already known this.

2) Even if you had, the min. threshold amount is .10 (also clearly stated) and you never mined more than ~0.05 BTC with us anyway which was paid out when you requested.   

Some people are impossible to please.  Do you really come here to bitch about .0005 BTC TX fees?  Tsss...

Close.  We got word that we were next on the "hit list" and that a large scale attack was imminent (more than 11gbps).   I had very little time to make a decision.

Faced with this situation and knowing that my datacenter didnt have the capacity to cope with an attack of this scale i made the decision to spare other mission critical services, colleagues, employees, and other paying customers the loss of revenue, headaches, and inconvenience an attack of the scale would have caused.

I resent being forced into this situation.  It doesnt feel right to shut Mainframe down.

Now i have also had to re-evaluate the entire situation and realize that there simply is not enough revenue being generated from this pool for it to support itself outside of my own network and the danger to my other clients, colleagues, etc. is too great to justify keeping this personal hobby project of mine up and running at the detriment of everyone else in this network.   (In case its not clear,  i co-own the company where the pool was hosted so the bandwidth and server costs were negligible as long as it was hosted in my own network)   

At any rate,  the pool just doesnt make enough to pay for the type of hardware and bandwidth needed to run it properly and the person who was donating this hardware and bandwidth (me) can no longer do it.  I cant say im really happy about any of this (Im not) but sometimes the most logical action is not always the most popular one or the one you really feel like doing.  I just dont see any other options right now.

It was fun.  I wish it could go on.  Im proud of 0 downtime and 0 problems during our 3 month run.  We had a good service which was stable, reliable and just worked and we had the best miners in the community.  I guess its not a bad record to go out with.   

- Anni

Mainframe is shutting its doors.   Dont worry we werent hacked and all BTC is safe and will be paid out on the same schedule as normal.

I will write more about this when i get the time.  Sorry it was so sudden.  There was no other choice.

You can still login here via the old stats page to retreive your funds:
http://mining.mainframe.nl/stats

Once logged in you can reach most of the old site and order a manual payout, change payment addresses, etc.  This part of the site will stay up for at least 2 weeks for everyone to get their BTC out (unless the site is brought up on other servers in the meantime)

EDIT:  More information here:
https://bitcointalk.org/index.php?topic=24650.msg589039#msg589039

edit: post outdated

148434 was payed out normally.  The block before that one which is no longer listed (148284 i believe) was orphaned and mainframe has never paid for orphaned/invalid blocks.   Hope this addresses your concerns.

Ill parrot part what some of the other ops have said as well.  Mainframe is looking into this but not jumping in with both feet for the following reasons:

1) unsure of demand for this from miners
2) same reasons Inaba mentions (lack of coherent and centralized information)
3) same reasons Luke-Jr mentions.  Im also not willing to jeopardize a stable BTC pool with unproven merged mining code (unproven in a live full scale production environment)

If some of these issues are addressed im happy to look at implementing it as well.

Im willing to at least consider it.  Can anyone provide me some links that will give me a consice overview of the issue so i can begin research ?

Oh and i forgot to mention - We had a pool record this month of 13 blocks in 2 days!