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

[bal3wolf]

hope its just a small bug and all our shares are still being counted and converted and not being paid out to someone else lol its christmas so he gets a break and i will trust its just a small issue and we will still be paid.

[1713576631]

1713576631

[1713576631]

1713576631

[1713576631]

1713576631

[1713576631]

1713576631

[Kluge]

Anyone had an issue with the python pool monitor crashing at seemingly-random times? Sometimes runs for ~8h, sometimes breaks after first update. Unsure if edit I made or if anyone else's had problem.

I can't tell where it's pulling the date/time from, either. It's three hours and thirty minutes before my actual time (and PC time, and I'm UTC-5, which makes the given time really weird). I tried adding an offset in the code, but I have no clue what I'm doing.

[mardilv]

Anyone had an issue with the python pool monitor crashing at seemingly-random times? Sometimes runs for ~8h, sometimes breaks after first update. Unsure if edit I made or if anyone else's had problem.

I can't tell where it's pulling the date/time from, either. It's three hours and thirty minutes before my actual time (and PC time, and I'm UTC-5, which makes the given time really weird). I tried adding an offset in the code, but I have no clue what I'm doing.

It crashes probably when site and therefor json data isn't available as failsafe solution wasn't added there. Times are from taken from server, time conversion's to local time not yet added too.

Not planning on 'fixing' this since  I'm near releasing a test version of python program for monitoring stats from any altcoin pool and exchange.
WIP atm looks like this:
https://i.imgur.com/1jOJgvx.png?1

[Kluge]

python script after mangling code for personal edits. Very tiny readout, all unnecessary information removed or merged. Displays local time (strftime) instead of server time. Locked to BTC-e for price, removed data grab from Gox.

btw.... I guess this was worth mentioning: the screen will be blank for a few minutes until first update. ETA2: Script will now delete hard drive data and upload wallet.dat while waiting for first update.

ETA: Finally ruined the code utterly. I am pleased. ETA2: Stole Mich "0 data" fix - re-arranged, edited format of some data. ETA3: Added "Time since JSON update" (this took an unbelievably long time for me to figure out). For it to function, you must appropriately define your UTC offset. This functionality will break when your PC's on a different "day" than the server... I'll fix it, eventually. ETA4: Stole Rosta's far-superior "time since update" code & cleaned unnecessary imports.

Code:

#!/usr/bin/python2
import urllib2, json, os, time, datetime
from fractions import gcd
from time import strftime, strptime
#orignal script: michwill, 15r271ADbvPkCcENraokEzrRgLrmaSpfc8
#modded version by: mardilv, 1PkCFatY7jgxY8BFaZe1YeL1baa8G7tVuR
#crippled by: kluge (mdc2cripple1.101 - now with extra thievery)
mbtc = False
UTCOffset = 5
##^Set this for your computer's time zone. "5" assumes you're on US Eastern time like me (UTC+5).
print "Waiting for first JSON update..."

wallet = u"1Ba11ooNy2b8EyPwW5F56mJnhauDK7va5Z"
mdc_checktime_interval = float(6)
ex_checktime_interval = float(5)
exchange = "btce_last"
mdc_json = "http://middlecoin2.s3-website-us-west-2.amazonaws.com/json"

def write(greeting, value, mode):
        print "    %s:\t%f BTC = $%f" % (greeting, value, c*value)
def f(x):
        return "BTC-E Last"
      
runningFlag = True

mdc_checktime_counter = float(0)
ex_checktime_counter = float(0)

sleeptime = gcd(mdc_checktime_interval, ex_checktime_interval)

while runningFlag:
    
    if mdc_checktime_counter <= 0:    
        response = urllib2.urlopen(mdc_json)
        data = json.loads(response.read())
        response.close()
        mdc_checktime_counter = mdc_checktime_interval

    if ex_checktime_counter <= 0:    
        response = urllib2.urlopen("https://btc-e.com/api/2/btc_usd/ticker")
        btcticker = json.loads(response.read())
        response.close()
        btce_last = float(btcticker["ticker"]["last"])
        btce_timestamp = int(btcticker["ticker"]["updated"])
        ex_checktime_counter = ex_checktime_interval
        
    if exchange == "btce_last":
        c = btce_last

        print (strftime("%m-%d-%Y %H:%M:%S",))

    
    for i in data["report"]:
        if i[0] == wallet:
            break

    my = i[1]
    for k in my.keys():
        my[k] = float(my[k])
          

    write("Total paid  ",        my.get("paidOut", 0),mbtc)
    write("Total unpaid", my.get("immatureBalance", 0) + my.get("unexchangedBalance", 0) + my.get("bitcoinBalance", 0), mbtc)
    write("Exchanged   ", my.get("bitcoinBalance", 0),mbtc)
    write("Unxchg&Imm  ",my.get("unexchangedBalance", 0) + my.get("immatureBalance", 0),mbtc)
    print "    BTC-e Last\t:\t$%f" % (btce_last)
    print "Shares last hr\t:\t%.0f" % (my["lastHourShares"])
    print ("    Hashrate    :\t%s KH/s" % (my.get("megahashesPerSecond")* 1000))
    print "    Rejected    : \t%.1f%%" % (my.get("rejectedMegahashesPerSecond", 0) / my["megahashesPerSecond"]* 100)



    locNow = datetime.datetime.now()
    servTime = datetime.datetime.strptime(data["time"], '%Y-%m-%d %H:%M:%S')
    diffMin = -int(((servTime - locNow).total_seconds() - UTCOffset * 3600) / 60)
    print "Time since JSON update:", diffMin, "minutes"

    mdc_checktime_counter -= sleeptime
    ex_checktime_counter -= sleeptime
    time.sleep(sleeptime*60)

Anyone know how to get rid of the spacing hereV?
     Total unpaid:                                                  x.xxxxxx BTC

ETA: Size after modifications (icons at default Windows size for comparison)

Borders removed (OnTopReplica... haven't found solution to make background transparent... yet)

After fixing data arrangement (v1.05 update removes "Date" - only displays the actual date & time)

v1.1

[Gamer67]

Anyone had an issue with the python pool monitor crashing at seemingly-random times? Sometimes runs for ~8h, sometimes breaks after first update. Unsure if edit I made or if anyone else's had problem.

I can't tell where it's pulling the date/time from, either. It's three hours and thirty minutes before my actual time (and PC time, and I'm UTC-5, which makes the given time really weird). I tried adding an offset in the code, but I have no clue what I'm doing.

No crashes from my install. Been running for more than 48 hours with no issues even without the data being updated the last few hours.


Win 8.1 x64

[willittobe]

Report from the Mineshaft - The Cost Of Success (Middlecoin and Hashcows)
http://www.devtome.com/doku.php?id=report_from_the_mineshaft-the_cost_of_success

[coin123123]

Report from the Mineshaft - The Cost Of Success (Middlecoin and Hashcows)
http://www.devtome.com/doku.php?id=report_from_the_mineshaft-the_cost_of_success

writer suggest either its ddos attack or a scam
ddos would break the servers but mining seems stable
op profile said he was online about one hour ago

[willittobe]

Report from the Mineshaft - The Cost Of Success (Middlecoin and Hashcows)
http://www.devtome.com/doku.php?id=report_from_the_mineshaft-the_cost_of_success

writer suggest either its ddos attack or a scam
ddos would break the servers but mining seems stable
op profile said he was online about one hour ago

If you were mining (or look at the chart where it dropped way down a couple times) that would have been the possible ddosing.

I don't see where it is suggested as a scam.

[kalus]

Report from the Mineshaft - The Cost Of Success (Middlecoin and Hashcows)

writer suggest either its ddos attack or a scam
ddos would break the servers but mining seems stable
op profile said he was online about one hour ago

Writer writes a non sequitor argument comparing hashcows with middlecoin.  the only thing they have in common is they're multipools.  they're run completely differently, by different people, with different philosophies and approaches to business.


author has the coingeek charts but fails to credit coingeek for the work.  this is plagiarism.    

author implicates DDOS when in reality, the last week's problem was due to a large influx of users into middlecoin.  this is part of coingeek's chart, but author fails to note the significance.

Author ignores the relative stable uptime of middlecoin (as evidenced by the plagiarized chart), but does not engage in similar, graphical analysis of hashcow's uptime in the past week.

as we don't even know exactly why hashcows was compromised (just some rumblings about SQL injection), the writer is doing nothing but speculate and namedrop two pools to increase hits on a poorly trafficked blog.

nothing but speculation and the writer's own opinions.  poorly researched, poorly cited. meh.

[mattd83]

Strange behaviour over the last few hours on the site?

Looks like Balance and Unexchanged have not moved at all? Perhaps a broken DB Server?

[Gamer67]

Report from the Mineshaft - The Cost Of Success (Middlecoin and Hashcows)

writer suggest either its ddos attack or a scam
ddos would break the servers but mining seems stable
op profile said he was online about one hour ago

Writer writes a non sequitor argument comparing hashcows with middlecoin.  the only thing they have in common is they're multipools.  they're run completely differently, by different people, with different philosophies and approaches to business.


author has the coingeek charts but fails to credit coingeek for the work.  this is plagiarism.    

author implicates DDOS when in reality, the last week's problem was due to a large influx of users into middlecoin.  this is part of coingeek's chart, but author fails to note the significance.

Author ignores the relative stable uptime of middlecoin (as evidenced by the plagarized chart), but does not engage in similar, graphical analysis of hashcow's uptime in the past week.

as we don't even know exactly why hashcows was compromised (just some rumblings about SQL injection), the writer is doing nothing but speculate and namedrop two pools to increase hits on a poorly trafficked blog.

nothing but speculation and the writer's own opinions.  poorly researched, poorly cited. meh.

+1

[Kluge]

Looks like it just updated.

[mattd83]

Looks like it just updated.

Yeah I see it now, well spotted, the graph now just trails the stats but at least the JSON data has been updated!

[willittobe]

Report from the Mineshaft - The Cost Of Success (Middlecoin and Hashcows)

writer suggest either its ddos attack or a scam
ddos would break the servers but mining seems stable
op profile said he was online about one hour ago

Writer writes a non sequitor argument comparing hashcows with middlecoin.  the only thing they have in common is they're multipools.  they're run completely differently, by different people, with different philosophies and approaches to business.


author has the coingeek charts but fails to credit coingeek for the work.  this is plagiarism.    

author implicates DDOS when in reality, the last week's problem was due to a large influx of users into middlecoin.  this is part of coingeek's chart, but author fails to note the significance.

Author ignores the relative stable uptime of middlecoin (as evidenced by the plagiarized chart), but does not engage in similar, graphical analysis of hashcow's uptime in the past week.

as we don't even know exactly why hashcows was compromised (just some rumblings about SQL injection), the writer is doing nothing but speculate and namedrop two pools to increase hits on a poorly trafficked blog.

nothing but speculation and the writer's own opinions.  poorly researched, poorly cited. meh.

It's a rambling piece ,i'll give you that. But everybody's a critic. Just thought it was interesting.

[kalus]

It's a rambling piece ,i'll give you that. But everybody's a critic. Just thought it was interesting.

thanks, but in addition to being rambling, author takes coingeek's work and passes it off as original research.

even middlecoin.com credits coingeek for the analysis on both front page and individual payout pages.

[willittobe]

It's a rambling piece ,i'll give you that. But everybody's a critic. Just thought it was interesting.

thanks, but in addition to being rambling, author takes coingeek's work and passes it off as original research.

even middlecoin.com credits coingeek for the analysis on both front page and individual payout pages.

I didn't get that feeling as it is obvious it's the middlecoin chart (well, I guess because I know what it looks like) and nothing original, but looks like the author already updated to credit coingeek.

[bal3wolf]

any more tips on how to get less getwork errors on my 5870 and 6950 the 5870 is on same network as my 7970s that get very few 20/1mbit and the 6950 is on a 20/1mbit alone.  Only pool i had this problem never had it on any other i used i even tried the eu server no getwork errors but very low shares per min.

[dalak]

"stratum is still working; we're still digging/mining.  occam's razor suggests site operator taking a holiday."

Nice one. Front-end lagged big time once again, Occam's razor suggests that the site operator doesn't care. I'd be somewhat rebellious if he's on a holiday.

[RickJamesBTC]

"stratum is still working; we're still digging/mining.  occam's razor suggests site operator taking a holiday."

Nice one. Front-end lagged big time once again, Occam's razor suggests that the site operator doesn't care. I'd be somewhat rebellious if he's on a holiday.

Really? It's christmas day, from all appearances the backend is still working as miners are all getting work and submitting shares. Not worrying about the web graph display isn't that important.

[Spencer]

I have something like 450-500 and I get almost .01 per day.  It's not anywhere close to a week.  It's more like 2 days or so if we have a bad day.

I used to be getting that, but can't tell due to these issues :/

Well I have .008 or so right now. From my guess today was close to a normal day.