Bitcoin Forum
June 25, 2018, 12:41:24 PM *
News: Latest stable version of Bitcoin Core: 0.16.1  [Torrent]. (New!)
 
  Home Help Search Donate Login Register  
  Show Posts
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 »
1  Alternate cryptocurrencies / Mining (Altcoins) / Re: Baikal Giant-B on: January 31, 2018, 11:35:11 AM
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 ?  Roll Eyes Roll Eyes
2  Bitcoin / Project Development / Re: mmcFE v2.1.23-stable - A Clean & Simple Pushpool frontend (PHP/BASH/JS/MYSQL) on: April 08, 2013, 09:29:58 AM
Im working on it Smiley

Well, well, well, please do explain Smiley

Ive been working on making this project more relevant again... not sure where it will lead yet Smiley
3  Bitcoin / Project Development / Re: mmcFE v2.1.23-stable - A Clean & Simple Pushpool frontend (PHP/BASH/JS/MYSQL) on: April 08, 2013, 08:12:12 AM
Im working on it Smiley
4  Other / Beginners & Help / Re: Does anyone have a mirror of mmcFE - A Clean & Simple Pushpool frontend (PHP/BAS on: April 07, 2013, 11:46:29 AM
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



5  Bitcoin / Pools / Re: [ POOL CLOSED ] Mainframe Mining Cooperative on: February 04, 2013, 07:21:21 AM
With the benefit of hindsight I do not think there were too many days during last 4 years where investing into mining hardware and power was more cost effective than simply buying BTC. Yes, at the time it often was much less risky to mine than to buy BTC. Indeed, different risk profile of buying versus mining was always obvious with GPU's/CPUs.

Note that most people who paid for ASIC's that are to be delivered soon (hopefully) paid for it when BTC was at 5$. The cost of lost opportunity for them is already nearly 300% of ROI. This means that they need to quadruple their investment just to catch up with those who decided to pass on ASIC mining and simply keep/buy some BTC instead. Good luck with this.


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.

6  Bitcoin / Pools / Re: [ POOL CLOSED ] Mainframe Mining Cooperative on: February 03, 2013, 04:14:21 PM
Im still lurking! Smiley  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 Smiley
7  Bitcoin / Pools / Re: [ POOL CLOSED ] Mainframe Mining Cooperative on: October 01, 2012, 07:36:49 AM

 Still here also. MMC was so far ahead it hasn't been passed in usability and stats yet.

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
8  Bitcoin / Pools / Re: [ POOL CLOSED ] Mainframe Mining Cooperative on: September 30, 2012, 09:35:39 PM
lol, yea, it was a blast.

Vladimir! Smiley
9  Bitcoin / Pools / Re: [ POOL CLOSED ] Mainframe Mining Cooperative on: September 30, 2012, 09:03:23 PM
Hey buddy!  I'm still plugging away.

Sometimes I reminisce about the good old days of MMC, Vladimir, and the crew   Cheesy

haha Smiley good to hear! Smiley   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). Cheesy
10  Bitcoin / Pools / Re: [ POOL CLOSED ] Mainframe Mining Cooperative on: September 30, 2012, 08:53:56 PM
So hows life? Smiley  How many of you MMC'ers are still mining bitcoin?
11  Bitcoin / Project Development / Re: mmcFE v2.1.23-stable - A Clean & Simple Pushpool frontend (PHP/BASH/JS/MYSQL) on: September 30, 2012, 08:51:28 PM
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
12  Bitcoin / Pools / Re: [ POOL CLOSED ] Mainframe Mining Cooperative on: October 25, 2011, 08:00:53 AM
But do you mind telling me why you failed to auto pay me (far above the limit) forcing me to pay you the fee to withdraw the last of my BTCs? Anyway, thanks for letting me to withdraw them, I guess.

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...
13  Bitcoin / Pools / Re: Speculation on: October 23, 2011, 12:43:58 AM
Speculation: I suspect the mainframe mining pool was also hit by this DDOS attack.

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


14  Bitcoin / Pools / Mainframe Mining Cooperative has shutdown. on: October 20, 2011, 11:10:22 PM
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
15  Bitcoin / Pools / Re: BTCGuild and it's relation to DDoS attackers on: October 20, 2011, 03:21:58 PM
edit: post outdated
16  Bitcoin / Pools / Re: [0 GH][0%][Merged Mining] SIMPLECOIN.US [20BTC+500NMC Promo][Prop/PPLNS/SMPPS] on: October 19, 2011, 10:51:24 PM
why the hell would someone come after this pool? we are hardly a force to be reckoned with!



1) because the source is open and coding mistakes are easily found and exploited ?
2) because the pool is supporting non BTC cryptocurrencies which some people feel is reason enough ?
3) because they could ?

Good luck Mike.

well you use the sc software dont you? what did you change? or are you vulnerable too?

Nope... the code branched and mmcfe is its own monster.
17  Bitcoin / Pools / Re: [0 GH][0%][Merged Mining] SIMPLECOIN.US [20BTC+500NMC Promo][Prop/PPLNS/SMPPS] on: October 19, 2011, 10:49:32 PM
why the hell would someone come after this pool? we are hardly a force to be reckoned with!



1) because the source is open and coding mistakes are easily found and exploited ?
2) because the pool is supporting non BTC cryptocurrencies which some people feel is reason enough ?
3) because they could ?

Good luck Mike.

well you use the sc software dont you? what did you change? or are you vulnerable too?

It's highly unlikely that that it was the the simplecoin framework. This was on the pool server, not the web server Wink

ah right... not likely then or there would have been traces on the webserver.
18  Bitcoin / Pools / Re: [0 GH][0%][Merged Mining] SIMPLECOIN.US [20BTC+500NMC Promo][Prop/PPLNS/SMPPS] on: October 19, 2011, 12:46:09 PM
why the hell would someone come after this pool? we are hardly a force to be reckoned with!



1) because the source is open and coding mistakes are easily found and exploited ?
2) because the pool is supporting non BTC cryptocurrencies which some people feel is reason enough ?
3) because they could ?

Good luck Mike.
19  Bitcoin / Pools / Re: [ ~220 GH/s ] Mainframe Mining Cooperative - PPLNS, 8dec, SSL, API, LP on: October 09, 2011, 12:12:45 AM
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.
20  Bitcoin / Pools / Re: [ ~250 GH/s ] Mainframe Mining Cooperative - PPLNS, 8dec, SSL, API, LP on: September 21, 2011, 06:07:55 AM
Quote
hi,

do you have any plans regarding merged mining?
it'll come in 196nmc blocks...

https://bitcointalk.org/index.php?topic=44546.msg537256#msg537256
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!