Should be.  I haven't tried pulling it down to make sure I didn't miss something.. but it should all be there.  I tag the files with the version, not much else, so if the last git matches the version here, you're good.

M

Same here.  I was just about to ask that.

I suspect there's an orphan somewhere.  You'd know if the payout suddenly disappeared.

M

Of all the mobile devices out there, the Windows phone would probably be the easiest to port it to, because it is .net.  If you use the visual studio express 2012 or higher (if there is a higher?) then you should be able to build it as a windows app.  Not sure of the intricacies.

M

Maybe some day I'll make a portable version of my apps.  For now, however, my time is extremely limited.  And, I'm one of the few people in the world who doesn't have a mobile device, of any sort.


I prefer the one in the app for tracking purposes, but either one will work, I won't complain.

Thanks!

M

Estimates are just that.  Estimates.  That's why I don't trust them.  Especially when they don't disclose how they estimate!

Mine is not an estimate.  It's what things are NOW.  If more hashpower is not added, it's how it will be next difficulty change.  Obviously hashpower will likely be added, which will increase it.  But considering we're 3.5 days from next change (at current hash power), I don't see it jumping from 23.6% to 30%.

In case you're wondering how I know, my M's Pool Monitor (see sig) has the calculations built into it based on the block info from blockchain.info.  Take the timestamp of the most recent block, subtract it from the timestamp of the block immediately before difficulty change, and divide that into how many blocks have been solved.  As of now that works out to 8.09 minutes a block.  Scale that to 10, and you get a 23.6% increase.  A little bit of math and I can predict the next change will be on 6/29 at 07:47 ET.

(This also means the closer we get to difficulty change, the more accurate the value is.)

M

fyi I disagree with the difficulty estimate.  I don't trust any site, I do my own calculations based on data from blockchain.info.  I'm seeing a current difficulty increase of 23.9% to 16,676,044,930.66.

Current time between blocks is 8.07 mins.

Change is slated to occur around 7:10 ET on 6/29.

M

ah!  apparently I forgot to rename it.   thanks.

M

fwiw, a while back I also emailed bitmain about p2pool.  I also asked that they work with Kano ... and give him the code to their S2 so he can figure things out.  I got the same response, about forwarding info to their engineers.

The symptoms are as others described: they max out around 920-930gh/s upon startup, and slowly decline over time from there.

I agree with what others have said: all bitmain has to do is setup their own node and point an S2 to it to see what's going on. 

M

I thought about adding database calls to store them off.  But that's the further it got.

M

That's the one with a bunch for sale but none being bought.

M

Thanks. I thought I found a place to sell them, but they have no buyers.  For now I'm just holding these.

M

Hmm, you'd think I would have noticed that by now.

What exactly is activity?

M

That's a lot of electricity, or really expensive!  I'm using about 0.06 BTC a month.


Looked to me to be around 266?

M

That's easy to defeat.  Use more than one address!

M

Version 2.21b:

- Added the ability to change Ant credentials w/o having to delete/readd them.
- Added an option to show the selection column on the Ant display grid.
- Added a new column ACount, showing the number of alerts for that Ant.  Sort by that column to have those with alerts bubble to the top.

Download link: MAntMonitor221b.zip

M

I'll add a numeric Alerts column.  You can sort it by column if you wish and those with alerts should (?) bubble to the top automatically (I hope).

M

Good idea.  I'll add an option, as for some people that'll just take up valuable screen estate.

M

I intend to add SSH support in this version.  That'll re-enable the reboot on Xs functionality.  I also intend to have "reboot on demand" functionality.  I should be able to put pool manipulation functionality in there as well.

M

Thanks!  Apparently I need more sleep.  I logged into my website, but forgot to actually upload the file.  Should work now..

Download link: MAntMonitor22b.zip

M

Here's version 2.2b for those who might be interested in new features or doing some testing for me. 

v2.2b
- Changed the hash rate, HFan, HTemp, and freq columns to be numeric fields so that they sort properly.
- Added a tooltip text for the Pools cell to show more pool info: pool #, URL, User, and status (Alive/Dead).
- Added the ability to keep separate userid/passwords for each Ant, one set for SSH, and one set for Web.
   - Note that existing users will have all their web usernames/pws set to what you had stored there when it was just one field.
   - If you need to change it for existing Ants, you can either remove it, then readd it, or edit the registry entry in HKCU\Software\MAntMonitor\Ants\RespectiveAnt
- Fixed the problem with multiple alerts for one Ant not being properly handled.

Download link: MAntMonitor22b.zip

Feedback is most welcome!

M