Hi folks - just a quick note to let you know that MultiMiner 4.2.3 is out and includes out-of-the-box support for additional algorithms and new FutureBit ASICs, along with various bug and stability fixes. You can download MultiMiner from downloads.multiminerapp.com. If you have any problems or suggestions, please report them at issues.multiminerapp.com. To learn how to configure MultiMiner, including adding unsupported algorithms, check out help.multiminerapp.com. Happy mining!
|
|
|
Shell scripts and precompiled binaries have been updated to reflect the following: Changes- Fixed linking of libusb with CGMiner
- Fixed linking of libevent with BFGMiner
- Added SGMiner-NH 5.6.1
- Added SGMiner-Pascal 5.5.0
|
|
|
Hey folks, wanted to drop a quick line to let you know that MultiMiner 4.2.2 is now available: http://downloads.multiminerapp.comhttp://thread.multiminerapp.comAlong with the usual bug and stability fixes, version 4.2.2 adds support for Pascal to the out-of-the-box algorithms: - CryptoNight
- Equihash
- Ethash
- Pascal
- Groestl
- Keccak
- Lyra2RE
- NeoScrypt
- Quark
- Scrypt
- Scrypt-Jane
- Scrypt-N
- SHA256
- X11
- X13
- X14
- X15
Additionally, MultiMiner allows the user to add any unsupported algorithm, coin, and miner, as long as there is a CGMiner, BFGMiner or SGMiner fork that supports the algorithm. See the following topics for more information on adding unsupported algorithms: Thought this may be of interest to the alt-coin mining folk. Happy mining!
|
|
|
Hi folks - just a quick note to let you know that MultiMiner 4.2.2 is out and includes out-of-the-box support for additional algorithms, along with various bug and stability fixes. You can download MultiMiner from downloads.multiminerapp.com. If you have any problems or suggestions, please report them at issues.multiminerapp.com. To learn how to configure MultiMiner, including adding unsupported algorithms, check out help.multiminerapp.com. Happy mining!
|
|
|
Hey folks, wanted to drop a quick line to let you know that MultiMiner 4.2 is now available: http://releases.multiminerapp.comhttp://thread.multiminerapp.comAlong with the usual bug and stability fixes, version 4.2 adds support for CryptoNight, Equihash, and Ethash to the out-of-the-box algorithms: - CryptoNight
- Equihash
- Ethash
- Groestl
- Keccak
- Lyra2RE
- NeoScrypt
- Quark
- Scrypt
- Scrypt-Jane
- Scrypt-N
- SHA256
- X11
- X13
- X14
- X15
Additionally, MultiMiner allows the user to add any unsupported algorithm, coin, and miner, as long as there is a CGMiner, BFGMiner or SGMiner fork that supports the algorithm. See the following topics for more information on adding unsupported algorithms: Thought this may be of interest to the alt-coin mining folk. Happy mining!
|
|
|
Build scripts and binaries for macOS are available below if anyone is interested:
|
|
|
Homebrew formulas, Shell scripts, and precompiled binaries have been updated to reflect the following: Changes- Added SGMiner-GM 5.5.5
- Updated BFGMiner to 5.5
- Updated CGMiner to 4.10
- Updated SGMiner to 5.1.1
- Updated libusb to 1.0.21
- Updated curl to 7.57.0
- Updated jansson to 2.10
- Updated libmicrohttpd to 0.9.58
- Updated libevent to 2.1.8
- Updated uthash to 2.0.2
|
|
|
Hi Guys,
I was installing BFGMiner 5.2.0 on Mac OS - Yosemite, upgrading from v 5.1 with Homebrew and down at the last a few steps, I got this error - any ideas?
=== Terrances-iMac:~ citronick$ brew install bfgminer Error: Formulae found in multiple taps: * nwoolls/cryptocoin/bfgminer * nwoolls/xgminer/bfgminer
Please use the fully-qualified name e.g. nwoolls/cryptocoin/bfgminer to refer the formula.
Terrances-iMac:~ citronick$ brew install nwoolls/cryptocoin/bfgminer ==> Installing bfgminer from nwoolls/homebrew-cryptocoin Error: Formulae found in multiple taps: * nwoolls/cryptocoin/uthash * nwoolls/xgminer/uthash
Please use the fully-qualified name e.g. nwoolls/cryptocoin/uthash to refer the formula. ===
Tried a few times but no luck - any ideas?
TMT
brew tap nwoolls/xgminer brew install bfgminer For more info please refer to the instructions at:
|
|
|
Welcome back to the fold. Hope you stick around for awhile. Sidehack could use a little of your help integrating with his Gekkoscience devices. CK took a little stab and we've been left using a fork ever since.
Shoot me an email at nwoolls at gmail dot com and / or take a look at the thread for Gekko support on GitHub: * https://github.com/nwoolls/MultiMiner/issues/301If there's a CGMiner fork that can mine it and I can get access to the device it shouldn't be a problem. Can you pls provide fresh links to mobileminer as old ones doens't work anymore.
There is no MobileMiner anymore. I moved on from that a few years ago when Bitcoin mining at home dropped off as that happened to coincide with personal changes for me (career, home, etc). There were a couple of other folks / companies interested in picking up MobileMiner but those fell through. So as of now it is no more. I've been told that someone else hijacked the domain with malware so I've been removing screens & links to MobileMiner but please let me know if you (anyone) see anymore. I don't want to be linking out to malware.
|
|
|
Hi folks - just a quick note to let you know that MultiMiner 4.2 is out and includes highly requested out-of-the-box support Ethash, CryptoNight and Equihash mining. It was already possible to add these algorithms manually but now they are supported automatically. Additionally, more of the config for algorithms and coin APIs has been exposed (via configurable multipliers for algorithms and configurable URL params for coin APIs) to help keep the program future-proof and allow users to keep using the program as new algorithms emerge. You can download MultiMiner 4.2 from downloads.multiminerapp.com. If you have any problems or suggestions, please report them at issues.multiminerapp.com. To learn how to add unsupported algorithms, check out help.multiminerapp.com. Happy mining!
|
|
|
Bitcoin transactions have 2 distinct states: 1) The transaction is sent out on the network 2) The transaction is confirmed in a block The last 2 payouts are still in state 1) They'll get to state 2) either when another pool confirms them (unlikely coz of the high transaction fees) or we find our next block Can you talk a little bit about why this may be different from block-to-block? I totally get (or at least I think I do) that payouts for previous blocks may wait until a new block is mined by kano.is. What I am not clear on is why I would not get a payout (yet) when a block is mined by kano.is, when I did get a payout when previous blocks were mined (either for that block or for shares of previous ones). IOW, I got a payout very soon after blocks 500622, 500907, and 501739. My understanding is that those payouts may have been for previously mined blocks. However, if that is the case, why would I not get a payout when 501835 was mined, for the previous shares or current? I could jump to my own conclusions but would love to have some light shed by those who know more. Is it that the payouts for the previously mined block were confirmed by another pool, but those for 501835 are not (yet)? If so, why were the previous payouts so (relatively) quick after the block was mined, compared to 501835? I'm much more curious than I am doubtful or suspicious - I'm sure the payout(s) will come I'd just love to know more about the tempo.
|
|
|
May be all the users of mobileminer should donate enough so nwoolls can support it. I can donate manually every month 1% of my earnings. Or we need to find who will continue it. Server is not s problem. Let's think about it together.
At this point I am not interested in hosting or maintaining MobileMiner. I am no longer mining at all (as it no longer makes sense to do at home paying electricity) so this isn't really an area I'm investing time or resources in. Additionally most miners are not willing to pay on top of electricity as it takes away from their profit. That said if someone wants to purchase the entire stack I am open to discussions and can be reached at nate @ mobileminerapp.com or nwoolls @ gmail.com. Nate, We're still open to the offer of %50 profit split even if we have to rewrite the end points in PHP Thanks it's definitely an option I may take. I don't mean to be irresponsive to your offer - any of them won't be taken right away (unfortunately). A lot of stuff going on personally and professionally. But I think either way it should be up again at some point under different stewardship.
|
|
|
May be all the users of mobileminer should donate enough so nwoolls can support it. I can donate manually every month 1% of my earnings. Or we need to find who will continue it. Server is not s problem. Let's think about it together.
At this point I am not interested in hosting or maintaining MobileMiner. I am no longer mining at all (as it no longer makes sense to do at home paying electricity) so this isn't really an area I'm investing time or resources in. Additionally most miners are not willing to pay on top of electricity as it takes away from their profit. That said if someone wants to purchase the entire stack I am open to discussions and can be reached at nate @ mobileminerapp.com or nwoolls @ gmail.com.
|
|
|
Anyone else having issues with mobileminer? Since ystday it shows offline all my machines Please see the post in the MobileMiner thread: https://bitcointalk.org/index.php?topic=622655.msg11620806#msg11620806ATTENTIONHello all. Unfortunately it's time (past time really) to shut down the MobileMiner services and apps. Mining at home is just not generating enough interest, and margins are too slim for miners, to keep things running (and to keep myself interested). Things will stay running until July 1st and any active subscriptions will no longer be charged. Thank you for your feedback, interest and patronage. Happy mining! ATTENTION
|
|
|
i would like to mine x15 maryjanecoin to help the network
There should be no problem with that. MultiMiner can mine any coin or algorithm supported by CGMiner and BFGMiner forks. Please refer to the documentation. You do not have to pick a coin from the list (as it says on the screen).
|
|
|
URGENT - PLEASE READ - MOBILEMINER IS SHUTTING DOWNHello guys, I'm sorry to be here to announce this but yesterday evening I received an email from Nate Wools (Mobileminer author) telling me his service is going to be shut down on 1th July 2015. That said, you have to turn off Mobileminer from your Minera before 1th July (I'd recommend you to turn off it ASAP). What does happen if you leave it on? Probably nothing, but your Minera will still try to connect to that service every minute and you will probably suffer from timeouts, so it's really better if you turn off it before the service will be shut down. Unfortunately I can't do anything but completely remove it in the next Minera version I'm going to release in about a week. We should be really thankful to Nate for all his work and I wanna personally thanks him for all his efforts. Thanks Nate! This is the Nate email every MobileMiner API user received: Dear MobileMiner API user,
We thank you for your support in adopting the MobileMiner API for mobile monitoring of home mining. Unfortunately home mining is no longer a realistic and profitable endeavor, which has lead a significant number of miners to cease operations or cut their costs. This leaves MobileMiner in an unfortunately situation where it no longer makes sense to offer as a service.
This email serves as an additional notice that the MobileMiner service will be shutting down as of July 1st, 2015. At this time the mobile apps have been removed from their respective stores and notices have been places on web properties. On July 1st the websites and APIs will be taken offline.
Nate Woolls Let me know if this poses a problem or if you need something delayed until you can put out a release. The domain will still resolve but should result in an HTTP 503. I'd be happy to put something in place to help if this causes an issue (such as a dummy endpoint that returns HTTP 200). I'm also talking to a couple of folks about continuing on the service under other stewardship, so if you do remove the functionality you may want to make it conditional (for now). Let me know if there's anything I can do to make the transition smoother.
|
|
|
BFGMiner picks up and uses my block erupters, however, MultiMiner sees them, and uses one of them. My erupters are connected straight into my motherboard into my USB3 ports. Any suggestions?
You have one of two options: - Either upgrade to MultiMiner 2.0 and bfgminer 3.7
- Or specify an intensity under the SHA-2 arguments in the Settings dialog (such as -I 9)
This was a bug in bfgminer (and cgminer) that caused dynamic GPU intensity to disable ASIC threads. And why the multiminer doesn't see my Silicon Labs CP210x USB to UART Bridge? Make sure you have the correct drivers installed: https://github.com/nwoolls/MultiMiner/wiki/Drivers#drivers
|
|
|
Any options to save this?
If someone else wants to acquire the code and rights and carry on with it they can contact me at nate@mobileminerapp.com. I've talked to a couple of folks but nothing concrete so far. It's really not a model that makes sense with the current state of mining. People aren't (in general) paying a fee on top of their other mining fees. And servers cost money, as does code maintenance. The fact that I don't personally mine anymore (doesn't make financial sense if you pay for electricity) doesn't help.
|
|
|
ATTENTION
Hello all. Unfortunately it's time (past time really) to shut down the MobileMiner services and apps. Mining at home is just not generating enough interest, and margins are too slim for miners, to keep things running (and to keep myself interested).
Things will stay running until July 1st and any active subscriptions will no longer be charged. Thank you for your feedback, interest and patronage. Happy mining!
ATTENTION
|
|
|
yes it is a gridseed blade. I have 5 of them 3 are running on a raspberry pi.
Hard to say - sounds like BFGMiner isn't detecting them properly. There should be two devices, not one. You can troubleshoot the device detection using the following info: https://github.com/nwoolls/MultiMiner/wiki/Local-DevicesThe information on the log files specifically should demonstrate the problem.
|
|
|
|