Sounds like to me you have no clue what you're talking about because he's not wrong.

Looks like the kernels have become popcorn.

Delicious.

Those estimates for AHP are often inflated in Nemos for whatever reason (AHP's API I suspect). The NPlus BTC/day estimates have been fairly accurate for me. Otherwise, you'll have to actually test them both to accurately compare profits.

As a continuation of my AHPPlus report using v1.3/1.3.2:

48h: Accumulated another 1.25977 mBTC, making earnings approximately identical to what NH would've given me.
72h: Added another 1080Ti and accumulated another 1.64016 mBTC, which is about 0.03 mBTC more than what NH would've given me.

With that being said, I'd say my confidence interval in this case is relatively low. My previous testing a few weeks back with AHP24h led me to profits that were nowhere close to estimates. I haven't tried the regular AHP batch file, but I've found that AHP24h profit estimates are a good approximation (once you reach high trust levels) of what you should expect to earn.

Yessir.

To update anyone who was following my long-ass report, I'm scheduled to make much more on AHP today, probably looking at 1.35-1.40 mBTC depending on luck, which is MUCH closer to default estimates than what I experienced in my other 96 hours.

In an attempt to see if I could match earnings estimates, I decided to hop onto ahashpool for 24hrs. I had spent 72hrs on AHP before, and the results were less than satisfactory. That test is documented in my older posts if anyone's interested.

Equipment:

- 3 1080Tis @ 200w
- 1 1070Ti @ 150w

I downloaded the release of NPlusMiner 1.3 and I was on my way. I selected xevan, hsr, phi, tribus, x17, Nist5, Lyra2RE2, blake2s, and neoscrypt as my algos. I also selected skein, but again, it never stopped benchmarking so I just ditched it because I'm impatient. The benchmarking process yielded me 0.000061901 BTC; this amount will be subtracted from my first 24hrs later.

- My switching gain was 4%
- I suffered about 30 minutes of downtime
- The test started (benchmarking finished) on Feb 21 9:35pm. I stopped it at 10:35pm of the following day to account for the downtime.

I waited another 30 mins for any stray earnings to register. My total earned was 0.00118892 BTC. After subtracting the earnings from the benchmarking section, I'm left with 0.001127019 BTC. Let's break this down to what each card amounted to approximately:

- 1080Ti: 0.3 mBTC*3 cards = 0.9 mBTC
- 1070Ti: 0.22 mBTC*1 card = 0.22 mBTC

I haven't dabbled with any other Yiimp-based pools except for Zergpool briefly; most of my mining is from NH. In the same time frame, I've earned about 0.34-0.37 mBTC for each 1080Ti and about 0.23-0.26 mBTC for each 1070Ti. My actual earnings are usually within very close proximity to estimates. The greatest outlier I've seen was less than 5%. This leads me to my conclusion.

The good: After reaching 100% trust level in NPlus, the "average BTC/D" reading is extremely accurate. I still enjoy the UI, there's something classic about it.

The bugs: Skein benchmark never stops for me, this has happened to me twice in isolated situations.

The switching behaviour is also very strange. The first time I boot after finishing benchmarks, my sleep time is 30 secs. X17 is the most profitable at this time. As X17 warms up during this minute, the program sees that X17 is the most profitable algo, yet, it'll restart X17 and I gotta warm up again. Talking about warming up, without changing the default intensity, I warm up starting from around 53mh all the way to 70mh. Once in a while, I'll warm up from 64mh to 70mh. Not sure what's causing the latter, but I wish I could reproduce it. Takes about 10 mins to warm this damn thing up if I have to start from 53mh.

After my first round with 30 sec sleep time, it turns to 180 secs. I didn't touch the "-interval" option at all. It's not even in my batch file. HSR is now the most profitable algo. I think to myself "alright, the program probably just thinks it's temporary, so it hasn't switched algos". I wait for 20 minutes. The switcher hasn't refreshed once ever since sleep time turned to 180 secs. The computer isn't frozen and neither is the miner. I think to myself again "ah fuck it, X17 will probably be on top soon enough anyways, I'll just leave it and let's see how long it takes". Almost 2 hours pass and I can safely conclude it's probably a glitch at this point. I manually restart. After the reboot, we're back to 180 sec sleep time; the miner refreshes and switches properly now.

The ugly: Outside of the BTC/D from reaching 100% trust, the earnings estimates are still wildly inaccurate from my experience. I'm not sure why this is, but fuck AHP is all I'm saying.

Thanks for reading.

You're using AHP Plus right because AHP24hr isn't as effective right? I'm testing ZergpoolPlus right now and Neo/X17 are the usual suspects, so I figured some people were still using a Neo miner.

I figured I should link this poll here too.

https://www.strawpoll.me/15122211

MrPlus has been wondering if he should replace Palgin's HSRminer with alternatives.

Also, why isn't this thread merged with the NPlus miner thread anyways? Seems like Nemo and MrPlus are collaborating on this project.

As requested (kinda).

http://www.strawpoll.me/15122211

Just took the latest files off your repo (the makings of 1.3 I'd assume) and tested it with a 1070Ti.

Bench-marking of skein and tribus for ZergpoolPlus went on for 20-30 mins before I manually cancelled them. X17 and NIST5 working fine so far. I'm wondering if this is because there's no "-interval" command in the start.bat file (was I supposed to re-insert that?). Also profits seem stupid-high right now, let's see how accurate they are.

Also is it possible for me to just replace Palgin's "hsrminer_neoscrypt.exe" with just_a_miner's fork (rename it to the same .exe)? Or will I have to fiddle with the Powershell files too? On second thoughts I should just try it for myself.

For what it's worth, I've had a fairly good experience with HSRminer, particularly with Just_a_miner's fork. I like to restart it once every 8 hours or so and it'll often produce the hash rates I see on client-side.

I've heard good things about KlausT if you're willing to mess with intensity, but I haven't tried that myself. Stock KlausT is underwhelming IME. NH's Excavator (1.4.4 I believe?) is also excellent for Neo when it comes to 1080Tis/TitanXPs. Not sure what their licensing details are, but might be worth replacing HSRminer if it's (relatively) easy to integrate.

Well, no, because the idea is that 1.4MH/s in Neo might be more profitable than 520sols in Equihash for example, which might've led to NH not using Equihash 90% of the time.

I might run a test myself if we get another major dip.

Thanks for the testing once again. I'm assuming you didn't load HSRminer or the newest revision of Excavator onto NHML? If you used the default miner (Klaust 8.18 I believe) without any intensity changes, it might be significantly slower than the two I mentioned. Also I believe Lyra2REv2's prone to price manipulation unfortunately.

AHP pumped out some solid numbers; I wonder if the gains were mostly due to the skyrocket in Verge's pricing.

Don't you think this is more demeaning and more of a dick move than my snarky statement?


I don't expect anyone or everyone to read all 3000+ posts, but if there's recent buzz about a new patch, you'd think the changelog is nearby. In addition, almost any competent dev has the changelog on their Github, it's standard practice.

? Not sure where you've been looking.

https://bitcointalk.org/index.php?topic=1777336.msg30312532#msg30312532

https://github.com/nemosminer/NemosMiner-v2.4.2/releases

Ugh, these results tempt me so much to go back to AHP, but I don't know if I can after my unpleasant experience with it during the dip.

Thanks for the testing nonetheless.

EDIT: Nvm, turns out I didn't bother reading and thought it was 24h when it was really 48h.

Just had a chance to give this a shot after the rave reviews. Here are my brief, anecdotal stats of 6x1070Tis running @ 85% TDP:

PalginHSR: 8.18kH/s
NH's newest version of Excavator: 8.1kH/s
Klaust 8.18 (NHML 1.8.1.: 7.7kH/s
J_A_M HSRfork (high intensity): 8.23kH/s

Of course, this is before any fees, so you can really see J_A_M's fork and Excavator pull through as my primary miners. I also favor HSR's UI. YMMV with hash rates (as seen throughout all of these miner threads), so please do your own testing and check pool-side rates.

@Just_a_miner: Please consider adding an ETH wallet

Second 0 (start): Algorithm X is most profitable

Second 1200 (your setting): Algorithm Y is most profitable

IF Algorithm Y is _% (your setting) more profitable than Algorithm X, switch to Algorithm Y. Otherwise, stay on Algorithm X.

By that I'm guessing you mean the earnings actually match projections now, or are relatively close?

Thank you for the testing, always good to have another data point. However, I think 200 minutes is far too short. 12hrs would be much more appropriate, or better yet, 24hrs.