|
Hi MOAMiner devs,
I used to have multple rigs running, up to around 16 GPUs at most, but since profits are way down lately and I live in a country where electricity is VERY expensive - I am now mostly just running a few GPUs to mine specific coins on low power algorithms which I think may have a bright future, and I HODL those coins instead of exchanging to BTC or algo mining.
Is there any point running MOAMiner with just a few GPUs, like 4 1070s when I pay $0.18 per kWh for electricity? I suspect I will be lucky to make $0.10 a day right? And I know that most of those algo mining pools have minimum payouts.
Also I noted that you support only Windows 10. I really don't like Windows 10 with all it's telemetry and data gathering, so I hope you might try a Linux version in future.
I do have a Windows 8.1 machine and may try it and see if it will run on that just for fun.
|
|
|
|
|
Hey - you should use CryptoDredge for cryptonight-heavy - it's much faster than XMR-Stak for Nvidia GPUs.
|
|
|
|
|
HEY Nvidia miners!
you should seriously check out CryptoDredge instead of XMR-Stak.
I am mining Loki (CN-heavy) with 1070s and I honestly get 20% more hahs rate. I am not the dev or getting paid or anything - I just think you should check it out.
|
|
|
|
|
Hi there AMD cryptonight miners.
I am getting at least 3.6kh/s in cryptonight-heavy consuming around 500W at the wall, with 4 Nvidia cards (and an i7 CPU) and some cool software called CryptoDredge.
I just wondered how that compares to what is possible with AMD rigs in terms of hash rate vs. power consumption.
I am honestly not trying to start a stupid tribal war here, I'm just curious because electricity is SO ridiculously expensive here in Australia and cryptonight variant mining seems to be the only gig left if you are getting ripped off for energy.
If I'd had a crystal ball I may have bought a Vega or 3 instead of all my 1070s but I reckon 3600 h/s @ 500W is pretty good no?
|
|
|
|
DAMN! I'm really disappointed  This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy. I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s. I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400). XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s ..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!! WOOT! I said to myself - I've found my new favourite miner. BUT as always seems to be the case it was too good to be true.  I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks. I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak. I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence. Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out. Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3. xmr-stak 2.5.1 vs CD 0.9.2 on cnv7 (3300 vs 3580) https://imgur.com/a/B9HubsIthis is what optimized xmr-stak can do in cnv8 (3200). 1080 Ti, 1080, 1070 Ti and 1070. https://i.imgur.com/8e4cVeD.jpgOK so what I can see from your info is that you have core clocks lowered considerably and memory clocks as high as possible. I might try that but it seems that no matter what i do, XMR-Stak is stable and keeps running but with a much lower hash rate than CryptoDredge - but when I run CryptoDredge, even with all GPUs at factory settings, my system reboots. I was wondering, does the CD watchdog cause reboot or just stop the miner. I was also wondering if I should just install Ubuntu and run CD in linux to see if that stops the goddamn rebooting. OK so something occurred to me. I was originally using this machine for gaming so the display was coming from the 1080. I have now gone into bios, activated the onboard graphics and I'm using that for display, so now all the GPUs are just running cryptodredge and the 1st GPU isn't trying to mine and provide display simultaneously. I hope this may solve my reboot problems but I will let everyone know. Rookie mistake maybe? I know that when I used to mine ETH I always had onboard video disabled and used the 1st GPU for display and mining but I don't remember the rules for Nvidia and custom versions of ccminer like this one. ! after 2 days of pulling my hair out and f&%*ing around, I have solved my problem. It was power distribution. The rig I was testing on has 1 750W power supply and a secondary 1200W server supply. I was stupidly powering a 1080 and 2 x 1070s on the 750W supply and only 1 x 1070 on the secondary. No wonder it was rebooting! So now I am a Cryptodredge convert. Thank you Cryptodredge devs for a really great miner. I have an improvement of at least 20% mining cryptonight-heavy algo. 1070 cryptonight-heavy XMR-Stak 720-760 h/s CryptoDredge 870-900 h/s 1080 cryptonight-heavy XMR-Stak 670-690 h/s C ryptoDredge 805-810 h/s I can also easily run a cpu miner concurrently (which I wanted to achieve because XMR-Stak uses both CPU and GPUs) and I get another 150 h/s. The whole rig measures around 500W. So that is about 3.6 kh/s for 500W. I wonder if those AMD vega miners can do that well? Also, XMR-Stak has a 2% dev fee (unless you compile yourself) and CryptoDredge is only 1%. I think CryptyoDredge must officially be the best cryptonight variants miner for Nvidia GPUs. Thanks again devs - your miner is awesome! |
|
|
|
Considering that the website is dead and all there seems to be here is speculation and hopeful people listening to the crickets churping...... I think XNN is DEAD  May it rest in peace. |
|
|
|
DAMN! I'm really disappointed This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy. I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s. I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400). XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s ..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!! WOOT! I said to myself - I've found my new favourite miner. BUT as always seems to be the case it was too good to be true. I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks. I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak. I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence. Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out. Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3. xmr-stak 2.5.1 vs CD 0.9.2 on cnv7 (3300 vs 3580) https://imgur.com/a/B9HubsIthis is what optimized xmr-stak can do in cnv8 (3200). 1080 Ti, 1080, 1070 Ti and 1070. https://i.imgur.com/8e4cVeD.jpgOK so what I can see from your info is that you have core clocks lowered considerably and memory clocks as high as possible. I might try that but it seems that no matter what i do, XMR-Stak is stable and keeps running but with a much lower hash rate than CryptoDredge - but when I run CryptoDredge, even with all GPUs at factory settings, my system reboots. I was wondering, does the CD watchdog cause reboot or just stop the miner. I was also wondering if I should just install Ubuntu and run CD in linux to see if that stops the goddamn rebooting. OK so something occurred to me. I was originally using this machine for gaming so the display was coming from the 1080. I have now gone into bios, activated the onboard graphics and I'm using that for display, so now all the GPUs are just running cryptodredge and the 1st GPU isn't trying to mine and provide display simultaneously. I hope this may solve my reboot problems but I will let everyone know. Rookie mistake maybe? I know that when I used to mine ETH I always had onboard video disabled and used the 1st GPU for display and mining but I don't remember the rules for Nvidia and custom versions of ccminer like this one. |
|
|
|
DAMN! I'm really disappointed This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy. I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s. I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400). XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s ..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!! WOOT! I said to myself - I've found my new favourite miner. BUT as always seems to be the case it was too good to be true. I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks. I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak. I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence. Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out. Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3. xmr-stak 2.5.1 vs CD 0.9.2 on cnv7 (3300 vs 3580) https://imgur.com/a/B9HubsIthis is what optimized xmr-stak can do in cnv8 (3200). 1080 Ti, 1080, 1070 Ti and 1070. https://i.imgur.com/8e4cVeD.jpgOK so what I can see from your info is that you have core clocks lowered considerably and memory clocks as high as possible. I might try that but it seems that no matter what i do, XMR-Stak is stable and keeps running but with a much lower hash rate than CryptoDredge - but when I run CryptoDredge, even with all GPUs at factory settings, my system reboots. I was wondering, does the CD watchdog cause reboot or just stop the miner. I was also wondering if I should just install Ubuntu and run CD in linux to see if that stops the goddamn rebooting. |
|
|
|
DAMN! I'm really disappointed This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy. I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s. I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400). XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s ..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!! WOOT! I said to myself - I've found my new favourite miner. BUT as always seems to be the case it was too good to be true. I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks. I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak. I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence. Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out. Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3.
|
|
|
|
CryptoDredge 0.9.2, windows 10 pro x64 Mining CN-heavy, after the dev fee it seems to start the same job over & submits duplicate shares in the same order as the first time:  Edit: Yeah it did this repeatedly, eventually putting my reject rate at about 36%. Edit 2: Issue solved with version 0.9.3 Would you mind sharing your 1070 settings to achieve ~900h/s? |
|
|
|
Just a word of warning, I updated my 1080ti from nvidia driver 398.36 to the latest one 416.16 and my hashrate on phi2 dropped from 10.5mh down to 6.0mh.  Uninstalled 416.16 with DDU and reinstalled 398.36 problem solved Also Top job on making Cryptodredge well worth the dev fee. On 0.92 My phi2 hashrate is double what it was using Zenemy 1.20 I tip my hat to you good sir (or madam ??) I experienced a very similar situation. I was using 397.xx and using xmr-stak to mine loki (cryptonight-heavy). When I "upgraded" to 416.xx I saw a drop of around 20-30%. I am going to try this miner for a while to see how it does at mining cn-heavy in comparison to xmr-stak. If it does manage 760h/s from a 1070 as claimed that is slightly better than I am currrently doing with xmr-stak and with a 1% dev fee instead of 2%. I guess I will also run a CPU miner like XMrig for the 150h/s extra that xmr-stak adds by using cpu and gpus simultaneously. I will report back on my results. |
|
|
|
|
As someone else may have already pointed out (I was too lazy to read more than the OP), mining has been declared dead so many times before and not just in 2018. I remember people saying that ETH mining would be dead by design (switched to POS) by now ages ago.
I have been mining for quite a while and I have seen this declaration over and over.
It's dead if you are narrow minded, ignorant, lazy or stupid. If however you can read, have some technical skills and a willingness to research and experiment can usually make at least a small daily profit. That's if you only mine for daily profit and you sell out to bitcoin or (worse) FIAT currency often.
If you have the patience to HODL you can get lucky. I wish I had read this advice and paid attention to it in early 2017. I would have made at least $200K.
There are some great projects out there with really interesting and innovative ideas behind them - especially amongst the various coins that use variants of the cryptonight algorithm.
Of course about 90% of coins are either scams or will never really take off, but part of the fun of this hobby (if it is a business to you I pity you) is picking the good ones.
|
|
|
|
I am used to seeing warnings from Windows Defender, etc about various mining software, and occasionally I have to click an extra few times to make Windows run a wallet... BUT when I try to browse to http://bitcoininterest.io/ I get a bright red screen and the following message: The site ahead may contain harmful programs
Firefox blocked this page because it might try to trick you into installing programs that harm your browsing experience (for example, by changing your homepage or showing extra ads on sites you visit).
Advisory provided by Google Safe Browsing. This is the first time I have seen this warning and I must have visited 100's of sites related to different crypto-currencies, tokens, etc. This doesn't inspire confidence. I'm guessing this has probably been addressed already if this is old news, but if it is a new thing - this could seriously damage this coin's future. |
|
|
|
walpool.com - scam, dont mine here !!!
my wallet: hvxyLjX1cWpBPNYLsCbLM3LDNUeuixaWEEv61dMboWiNMqrECSX9c3a4ZejeTspDcJ3fvUzExUTBvNB K1JKgcrkY58dGuGNkSe
not PAY!
although the difficulty has gone crazy with the pumped price - if you still want to mine HAVEN I recommend haven.miner.rocks - I mined there for 12 hours and got paid, but since everyone else seems to be mining it too I went back to mining Loki. I like the idea behind Haven Protocol, but there are too many big questions so far unanswered about the workability of it's economics. If you are just mining to dump for BTC then sure, but I mine to HODL. |
|
|
|
~
Hi, What I should do to stake my LOKIs? I found that LOKI is stakeable now, right? I guess that staking is for all, not for only service nodes. Please help me. Staking with LOKI coins, really?
How to config my wallet to stake my LOKI coins?
Or it will automatically stake after syncing with LOKI network? I'm pretty sure that whenever you read a reference to "staking" on the Loki network, this refers to the service node stake, not staking coins in a regular wallet like you would with a "proof of stake" coin. Loki uses a combination proof of work plus service nodes nodes (like masternodes used by Dash, PIVX, etc). That is why the mining reward dropped dramatically a couple of weeks ago - because a large chunk of it is now going to people lucky (and rich) enough to have 12000-45000 Loki to stake in a service node. |
|
|
|
|
Is there excess demand for this kind of product? We already have SIA, STORJ, FILECOIN, MAIDSAFE and others.
|
|
|
|
|
As I had a look over the GNT project, I couldn't help wondering: are they going to utilize all the GPUs out there as part of their "decentralized supercomputer"?
Altcoin mining from last year means there is a huge capacity available for OpenCL or CUDA usage. Or is it just dedicated to CPUs?
|
|
|
|
am I the only one using ethminer? its capable of 54Mh if your overclock is, what is the benefit of phoenix/claymore? don't they have dev fees? why pay that if you don't have to
I have been using ethminer https://github.com/ethereum-mining/ethminer/releases for months. I use the latest RC versions unless I have problems then I got back to the stable 0.14.0 and I get at least as good hash rates as any of the fee miners but with NO FEE! I just never understood why anyone would use a fee based miner if you use Nvidia GPUs. crazy! |
|
|
|
thanks for making this. I tried to follow instructions, but I had trouble with visual studio since I already have a few versions of it installed, the cuda downloader for visual studio integration failed. Yours worked instantly! 2 ez  you are welcome. I have expeirenced a very strange connect error to nanopool on only one of my machines.... Anyone else getting this issue? I'm not sure what the hell happens (because so far I have been asleep each time) but I have some issue which seems to crash three instances of the miner (2.4.4) running on two machines. Last night it was after running great for 16 hours, mining Loki (which has a very low difficulty right now which is good, but has taken a price hit - but I am HODLing anyway). Did you manage to compile 2.4.5 yet? I was going to try to teach myself how sometime but it's like going back to f'ing school..... no luck on trying with 2.4.5 yet. Probably sometime tomorrow since Ill be at a location where I can uninstall and reinstall everything for the third time to try and compile it. The issue was a fluke; seems right before the completion of the new windows 18xx update. I tried running 2.4.2, and it gave the same no connect error. When I came home later that day my machine had rebooted itself automatically, and 2.4.4 launched no problems again. It was an odd one. Go into the CPU config, and remove the CPU threads.... leave it blank brackets {}. See if stability comes back. I have a LGA775 machine right now that gets TLS socket errors and reconnects every so often. The auto emails from nanopool from that machine are quite annoying. I got sick of windows sneaking in updates I had all my rigs running 10 pro with updates totally disabled and somehow they all updated so after playing on google for awhile I was able to find a win 10 pro stripped down with no apps or anything I haven't had one issue since I was also sick of win 10 updates and all that "telemetry" running. I now use win 8.1 on all my rigs. xmr-stak runs OK for Nvidia GPU mining - I get up to 740h/s per gtx1070 (30 threads, 60 blocks, core 0, memory +750, powerlimit 75%). @JaredKaragen - did you ever manage to compile 2.4.5? I really need to teach myself all that is necessary to compile for Windows or even maybe run linux. |
|
|
|
Someone has turned a shit load of them on.
Zcash difficulty doesn't change very quick. I seen soo many blocks go in the last few hours.
Block time meant to be 150sec I think and it was af 10sec and diff barely moved and they are happy fo have asics on thier network
fuck zcash. They were supposed to be decentralized and "privacy" transactions. They have never gotten the z address transactions to work and now they are an ASIC coin so they are neither decentralized or private. What is the point of zcash now? |
|
|
|
|
Show Posts
