Bitcoin Forum

Economy => Marketplace => Topic started by: danetix on January 31, 2012, 03:32:29 AM



Title: BTCmon updated v1.5 to support merged mining (more pools too!)
Post by: danetix on January 31, 2012, 03:32:29 AM
Hi everyone,

We've updated our iPhone app to v1.5

What's New in Version 1.5
- Added merged mining support for BTC Guild, Mt. Red, Slush
- Added mining pools 50BTC, BTCMine, ABCPool, EclipseMC, BitClockers, Ozcoin and BitLC
- Minor bug fixes and performance enhancements

Project thread: https://bitcointalk.org/index.php?topic=44608.0
Website: http://btcmon.com
App Store: http://itunes.apple.com/us/app/btcmon/id463386122?mt=8&ign-mpt=uo%3D4

Let us know what you think!


Title: Re: BTCmon updated v1.5 to support merged mining (more pools too!)
Post by: Littleshop on January 31, 2012, 03:37:16 AM
BTCmon is the best!  I love how fast I can check on my miners and the exchanges.   It has a very clean look as well. 


Title: Re: BTCmon updated v1.5 to support merged mining (more pools too!)
Post by: danetix on January 31, 2012, 03:49:56 PM
BTCmon is the best!  I love how fast I can check on my miners and the exchanges.   It has a very clean look as well. 

Glad you are enjoying it! Thanks for the review!


Title: Re: BTCmon updated v1.5 to support merged mining (more pools too!)
Post by: freshzive on February 08, 2012, 04:39:01 AM
I've noticed one issue with BTCMon: for miners that do over 1GHash (i.e when using something like cgminer that pools lots of workers), the app shows something like 1.24Mh/s instead of 1.24Gh/s. Is it possible to fix this?

Other than that, I love the app, use it everday :)


Title: Re: BTCmon updated v1.5 to support merged mining (more pools too!)
Post by: danetix on February 13, 2012, 03:05:11 PM
I've noticed one issue with BTCMon: for miners that do over 1GHash (i.e when using something like cgminer that pools lots of workers), the app shows something like 1.24Mh/s instead of 1.24Gh/s. Is it possible to fix this?

Other than that, I love the app, use it everday :)

Thanks for reporting the problem. With your help, we'll have it fixed in the next update.  :D