The official MacMiner thread [BTC/LTC-CPU/GPU/FPGA/ASIC]

[Anonymailer]

Also I intend to update bfgminer and some other stuff today too!

[BrandonMcPherson]

I had to send my unit back a couple of weeks ago, so I haven't been keeping up here. My replacement arrives tomorrow, hence me sticking my nose in again.  I have a Raspberry Pi set up, but I was hoping to be more civilized this time around.

Is the Gridseed support baked into the regular release? The last one I tried was the Gridseed7 version, and I was never able to make it work.

[Anonymailer]

MacMiner has been updated and it is necessary for MobileMiner users to update for that functionality to continue.

I'm also particularly interested for gridseed users to give the bfgminer included a shot as this is the latest from github.

[DanZaph]

I'm also particularly interested for gridseed users to give the bfgminer included a shot as this is the latest from github.

I  have two Gridseed 5-chip units, currently mining with minerd via Terminal, one device per minerd. I am willing to try 1.5.20b1 but would like some setting information. Also do I need to have two instances of MacMiner, one per Gridseed unit?

[Anonymailer]

I'm also particularly interested for gridseed users to give the bfgminer included a shot as this is the latest from github.

I  have two Gridseed 5-chip units, currently mining with minerd via Terminal, one device per minerd. I am willing to try 1.5.20b1 but would like some setting information. Also do I need to have two instances of MacMiner, one per Gridseed unit?

Unfortunately using the CPU miner window which uses minerd you do have to have two instances but I'm hoping you'll now be able to use the devices in one instance of the GPU window with manual flags either

-S gridseed:all

or

-S dualminer:all

i :: think :: the latter is for 1 chip and vice versa but not totally sure.

[DanZaph]

I'm also particularly interested for gridseed users to give the bfgminer included a shot as this is the latest from github.

I  have two Gridseed 5-chip units, currently mining with minerd via Terminal, one device per minerd. I am willing to try 1.5.20b1 but would like some setting information. Also do I need to have two instances of MacMiner, one per Gridseed unit?

Unfortunately using the CPU miner window which uses minerd you do have to have two instances but I'm hoping you'll now be able to use the devices in one instance of the GPU window with manual flags either

-S gridseed:all

or

-S dualminer:all

i :: think :: the latter is for 1 chip and vice versa but not totally sure.

Good: "-S gridseed:all" works for me, finds and mines with both Gridseed devices.
Bad: Neither of my BTC miners work, back to 1.5.18e.

[Anonymailer]

Good: "-S gridseed:all" works for me, finds and mines with both Gridseed devices.
Bad: Neither of my BTC miners work, back to 1.5.18e.

Well that's awesome progress with the gridseeds! What are the BTC miners that are not working?

[DanZaph]

Bad: Neither of my BTC miners work, back to 1.5.18e.

What are the BTC miners that are not working?

The miners that did not work were an ASICMiner V3 Erupter Cube and a BFL Jalapeño.

[Anonymailer]

The miners that did not work were an ASICMiner V3 Erupter Cube and a BFL Jalapeño.

I'm using a BFL Jalapeño with this version - we've probably got a backend behaviour here - one thing I would suggest is starting the BTC miners BEFORE starting the gridseed miners on LTC mode

If that's not it, I wonder whether it's an issue with the proxy for the cube…

[DanZaph]

The miners that did not work were an ASICMiner V3 Erupter Cube and a BFL Jalapeño.

I'm using a BFL Jalapeño with this version - we've probably got a backend behaviour here - one thing I would suggest is starting the BTC miners BEFORE starting the gridseed miners on LTC mode

If that's not it, I wonder whether it's an issue with the proxy for the cube…

I'll try that.
But it is really late for the those miners, they are no longer profitable at the current BTC price with poor luck so I am shutting them down in the next week. My electricity cost is $0.08/kWh.

[Anonymailer]

I'll try that.
But it is really late for the those miners, they are no longer profitable at the current BTC price with poor luck so I am shutting them down in the next week. My electricity cost is $0.08/kWh.

You mean the BFL and the cube? Sad to see the earlier ASICs becoming redundant already! The gridseed should be profitable for scrypt for a while..

[DanZaph]

You mean the BFL and the cube? Sad to see the earlier ASICs becoming redundant already! The gridseed should be profitable for scrypt for a while..

It is close, yesterday was un-profitable, today marginally profitable. I also see where waldohover shut down Jupiter miners.

[Anonymailer]

You mean the BFL and the cube? Sad to see the earlier ASICs becoming redundant already! The gridseed should be profitable for scrypt for a while..

It is close, yesterday was un-profitable, today marginally profitable. I also see where waldohover shut down Jupiter miners.

Not optimistic about the future value of any particular coin then?

I found the root of the continuing MobileMiner issues and have updated to fix that as well as added some sanity checks in hope of fixing the mysterious and elusive crashing bug some users are experiencing on second app launch.

[nwoolls]

I found the root of the continuing MobileMiner issues and have updated to fix that as well as added some sanity checks in hope of fixing the mysterious and elusive crashing bug some users are experiencing on second app launch.

As always feel free to give me a shout if you ever need a hand with the MobileMiner API. Thanks again for supporting it!

[DanZaph]

Not optimistic about the future value of any particular coin then?

Scrypt looks good, the tradeoff of processing power for memory gives lower power requirements providing possibly a long life against the cost of power.

[Anonymailer]

Thanks Nate! I think I'm good for now.. we'll see!

I'm worried that ASIC will kill scrypt - it was built specifically to be ASIC resistant so what's it for now?

[nwoolls]

I'm worried that ASIC will kill scrypt - it was built specifically to be ASIC resistant so what's it for now?

Seems like a constant cat-and-mouse game. Now GPU miners are looking at Scrypt-N and X11. The problem is, if they gain enough popularity, then you'll see a HW implementation of those as well. With enough interest any SW algorithm can be done in HW in theory.

[DanZaph]

I'm worried that ASIC will kill scrypt - it was built specifically to be ASIC resistant so what's it for now?

Kill it from what perspective? The _real_ reason for "mining" is to verify transactions. ASIC scrypt is really good for this because it is very low power, efficient, green.

Coin was not created in order to make money mining. Mining rewards were created to solve the chicken-egg problem of getting people to run verification servers, uh, that is miners to bootstrap BTC.

So, yeah, LTC was naive in trying to make GPU mining easier than ASIC, if they had been smart they would have realized that ASICs would come to scrypt. Or maybe they knew and purposely sought a more efficient process but had to mis-direct the mining community in order to get the miners involved in scrypt.

[XFox]

I found the root of the continuing MobileMiner issues and have updated to fix that as well as added some sanity checks in hope of fixing the mysterious and elusive crashing bug some users are experiencing on second app launch.

With 1.5.20b2 I see this error in system log (e-mail address and application key obscured):

Code:

08/05/14 16:19:35,357 MacMiner[72481]: Error getting https://api.mobileminerapp.com/api/RemoteCommands?emailAddress=xxx@xxx.xxx&applicationKey=xxxx-xxxx-xxxx&apiKey=26efrOXrizmEF3, HTTP status code 404

[nwoolls]

I found the root of the continuing MobileMiner issues and have updated to fix that as well as added some sanity checks in hope of fixing the mysterious and elusive crashing bug some users are experiencing on second app launch.

With 1.5.20b2 I see this error in system log (e-mail address and API key obscured):

Code:

08/05/14 16:19:35,357 MacMiner[72481]: Error getting https://api.mobileminerapp.com/api/RemoteCommands?emailAddress=xxx@xxx.xxx&applicationKey=xxxx-xxxx-xxxx&apiKey=26efrOXrizmEF3, HTTP status code 404

The RemoteCommands endpoint should also be passed a MachineName on the QueryString:

http://www.mobileminerapp.com/#api

Code:

{Root URL}/RemoteCommands?emailAddress={Email Address}&applicationKey={Application Key}&machineName={Machine Name}&apiKey={API Key}