Hi there, I wish to buy a Windows 8.1 Key.
|
|
|
Are you reporting on the proper dogecoin fork? (Client 1.5+)
|
|
|
You really need to adjust the profitability of Dogecoin, the possible reward is halved.
|
|
|
Hi, i have a problem. If i set the thread concurrency over 24700 the miner doesn t mine!
I have a r9 290x, windows 7, cpu sempron 145
With this setup get 880khs: -I 20 -g 1 --thread-concurrency --lookup-gap 2 --gpu-powertune 30
gpu clock 938 memory clock 1500
can someone help me?? Embarrassed
thx
read scrypt-readme.txt in the miner folder for tuning help. You aren't setting a thread concurrency with that config. Try this one: -I 20 -g 1 -w 512 --thread-concurrency 32765
|
|
|
True. I just prefer the Coinchoose "profitability adjusted for stales" option because I think that's more along the lines of true profitability. I've put in a request for the fix in the Coinchoose thread, so hopefully the admin helps out!
Once Coinwarz offers bitcoin payment for the API, I may switch, but I don't feel like paying with paypal...
Here's a build that should work around the current CoinChoose.com API issues: https://www.dropbox.com/s/yvqdjk2w3xl526i/MultiMiner-2.5.5.zipExcellent. I tipped you over on reddit for the fix! Thanks!
|
|
|
True. I just prefer the Coinchoose "profitability adjusted for stales" option because I think that's more along the lines of true profitability. I've put in a request for the fix in the Coinchoose thread, so hopefully the admin helps out!
Once Coinwarz offers bitcoin payment for the API, I may switch, but I don't feel like paying with paypal...
|
|
|
Can you fix the null difficulty issue with BitGem? It is causing improper JSON format errors
|
|
|
Fair enough, Coinwarz is just tougher to deal with due to their API limits.
|
|
|
Anyone else having issues with the CoinChoose API today? I did a fresh install on my machine about 12 hours ago, and haven't been able to get a solid return from Coinchoose since then, so MultiMiner is acting weird.
|
|
|
nwoolls, just curious: are you tracking SGminer at all? It's a fork of cgminer 3.7.2 to create a scrypt only miner. I think it might be worth it to keep track of this, as Luke-Jr has stated he doesn't support altcoins before, and it's quite possible he'll let the scrypt capability stagnate. Also with the rumours that the bitcointalk admins are going to remove all altcoin-based forums from this site, it's looking like this will become a hostile environment for altcoin develelopment. I think most(or maybe just a large portion) of the MultiMiner users are scrypt mining (since there are more scrypt coins out there), and it would be worth keeping track of a miner like this. Here's the thread over at the litecoin forums. https://litecointalk.org/index.php?topic=13190.0
|
|
|
Hi, Is there a way to avoid to push in background bfgminer output better then modify and compiling the source? I had a look at source code and your comment about the hashrate improvement but I'd like to have the possibility to enable "-q" option by using it or not in the string for miner configuration (or better in the GUI as a tick ) You can add arguments like that in the settings dialog, then click on "Advanced miner settings" and enter it in the correct text box according to the algorithm you're using.
|
|
|
I trust coinchoose's profitability rating more than coinwarz since you can sort by profitability accounting for stales. It doesn't have the calculator, but if you can do math you can do it yourself. According to coinchoose, about 8% of doge blocks will be orphaned or stale. Keep those numbers in mind
|
|
|
Can you add LottoCoin, MoonCoin and EarthCoin please?
Thank you!
|
|
|
just checked the frontend again, get the following message
Update: DB issues forced a rebuild. Please switch to Another pool for Now. Things Should be Back to normal by Morning. coins Are safe.
Yeah that's an old message, it doesn't display that now.
|
|
|
Update: DB issues forced a rebuild. Please switch to Another pool for Now. Things Should be Back to normal by Morning. coins Are safe. Chill, people. It'll be back.
|
|
|
Please fix the API! It's been over 12 hours since the SQL error has been there.
|
|
|
What prompted the "Privacy policy" and "Terms of use" agreement?
|
|
|
Yes, my apologies for that. However, it should be easy to re-enter pool information if you use one of the default pools as your login information will be pre-populated from previous keychain entries regardless of Asteroid version. Actually you just gave me an idea, perhaps I can allow custom pools to be saved in a similar manner... Anyway, Asteroid does include code to migrate preferences from version to version, but the format changed slightly between the two most recent versions and I think there's likely a bug or two in there too. I'll have a look for 0.9.6, and thanks for the feedback Pool settings aren't as annoying as having to re-enter my MobileMiner API key. Pool settings are generally easy to remember, but an API key requires me to find it and enter it in manually.
|
|
|
Asteroid still only displays the hashrate of 1 of my 3 erupters in the UI, but the "Miner Console" lists the proper hashrate. They show up as "AMU-1, AMU-2, AMU-3" instead of "ASICMINER USB Block Erupter" as the image on the website indicates it should be... What's going on?
Also, none of my settings were saved when I upgraded from 0.9.4. Very frustrating.
|
|
|
If you already have the debug version installed, will it still install the new debug version? Version 2.0.2 of MultiMiner is now available with the following changes: - Both Hardware Errors and Rejected Shares are now shown as a percentage
- Notifications are logged as JSON to %appdata%
- Current coin is now shown checked in the device context menu
- Application no longer automatically downloads -Debug releases
- Application now uses azurewebsites.net when communicating with MobileMiner
- Fixed an error scanning hardware after a device is removed and re-added
- Fixed cross-thread operation errors after MobileMiner credential warnings
- Fixed inconsistencies between the pools shown in the UI and the pools currently being used to mine
- Fixed errors deleting pools while mining
- Fixed orphaned devices / configurations not being re-paired
- Fixed the Block Found notification being triggered by the wrong data point
- Fixed wrongly formatted dates in the History window for some cultures
- Fixed links to CoinChoose.com when CoinWarz.com is set as the Coin API
Thanks for the feedback and bug reports folks. Keep 'em coming
|
|
|
|