I'm getting something similar with 1.8.3 and 18.6.1 drivers on a mixed RX 560 / 570 rig. Will be going back to 1.8.1 here shortly if the "low difficulty share" errors persist.


One other bug I noticed is that the min_rig_speed parameter seems to only be looking at one of the GPU's hashrate, rather the sum total.

No, that's a really good point about running a computer just to keep wallets open for staking. My electricity costs $0.12/kw-hr so running that laptop costs me around $0.10 per day and I can guarantee you it isn't earning anywhere close to that from staking two different POS coins. Fortunately, I use the laptop to monitor my mining rigs as well so it would be running 24/7, anyway.

I received a stake with the 1.2.0 wallet! I actually wanted to buy some more TZC but it seems it isn't available on stex (and I can't remember if it was ever available on bittrex)... which exchanges have it these days?

Perhaps, but my balance is now 0... The new wallet has both of the addresses I generated in the original wallet, shows the most recent transactions from before the upgrade, and required the same password to unlock it for staking, but balance is 0.

If you ever wonder why people are slow to upgrade their wallet this is a prime example why.

EDIT - I scrolled back through the post history and found a recommendation by you to run trezarcoin-qt with the switch -zapwallettxes=1 so I am trying that. ...waiting for rescanning to complete... and.... *most* of my balance is back - the most recent stakes I received when still running the old wallet have disappeared. Still, I seem to have solved the problem myself and I must say I really like the changes you made concerning staking.

Updating to 1.2.0 appears to have solved the problem, though I won't know for sure for at least a day because it seems the new wallet program has to download the entire blockchain all over again.

Yes, and while I can't say I've claimed victory just yet, so far it appears that dialing back a little on the memory clock is helping. Prior to that Windows 10 would BSOD with a TDR video failure, sometimes before starting the miner, and even after I DDU'ed 18.6.1 and reinstalled it (pixel patched, etc.).

So far I have been mining for a couple hours at 1860 on the mem clock (1200 on the core clock) at full power and not really seeing a reduction in hashrate from when I was running at 1200/1900.

Incorrect six ways to Sunday.

Block reward from staking (sprouting) is 1000 BeanCash, so if the calculator says you'll make 250 BITB/BEAN per month then it will take you, on average, 4 months to receive a stake (sprout). Assuming the wallet is open 24/7, that is.

If the wallet is only open 12 hours per day then it will take twice as long to receive a sprout (again, a statistical process). Consequently, the larger the number of BITB/BEAN in your wallet the more accurate the sprouting calculation tends to be. I use an old laptop for my wallets and set the screen turn-off time when not being used to 5 minutes so it consumes hardly any power - maybe 20W-40W or so.

The latest CN fork - r, v4, whatever it's called - uses a little more power than the previous fork for my mix of RX 570 and RX 560 cards, but overall it is still using less than Ethash. And I am not even undervolting or power limiting the cards anymore (got tired of chasing stability problems - figured it was better to use 10% more power and not wake up to a rig that crashed right after I went to sleep [because that's when they always crash, amirite?]).

LTHN, which I've been mining continuously for over a year. I don't care so much whether it is profitable or not because it has an actual product that makes sense to pay with crypto - a distributed VPN.

Man have I had some serious problems with my last running mining rig that has been cranking away on CN variants for over a year straight but I just wanted to thank the OP for making a great miner which easily earns its devfee, and I am well aware I can run JK's version of xmr-stak compiled with no devfee.

Because I am still sorting out problems with the rig (keeps BSOD'ing with a Kernel Power 41 error) I just have a single RX 570 running but getting a consistent 810 H/s with Adrenalin 18.6.1, Afterburner set to 1200/1900, and the gpu_conf parameters are intensity 58, worksize 8, threads 2, fragments 8. Temp is a cool 52C, but that's with just one card loaded on the Onda d1800 6-card mobo.

The same card gets around 735 H/s with xmr-stak with otherwise same/similar configuration and settings; needless to say, I'll gladly pay 0.85% to get 10% more hash.

Yeah, a similar thing happened with TrezarCoin, but at least they are developing a use case called TrezarTravels; BitBean or BeanCash or whatever the fuck this disaster is called has absolutely nothing going on except inflation. Bring on the Weimar Republic style wheelbarrows to carry around $100 worth of BEAN.

Meh, I'm feeling a bit salty these days because my last running mining rig decided to start throwing a bunch of Kernel Power errors and it's been a year since I had to mess with pixel clock patcher and all the other fun stuff that goes along with getting AMD cards to mine.

Lol... I finally got a sprout on my original 5000 BITB after a year. Too bad I need to get 10 more sprouts just to break even. 

Crypto - the dotcom bubble 2.0

It looks like my wallet which has been running continuously for over a year (old version - have downloaded 1.2.0 but not yet updated) is reporting an error "Checkpoint is too old. Wait for block chain to download , or notify developers." Since the wallet has been running continuously I presume the blockchain file is up to date, so does this mean I need to update the wallet or is something else going on?

It took them long enough... This thread so infuriated me I basically quit the forum for a couple of months. I got tired of seeing it repeatedly show up in the top of my "new replies" list.

Thanks for your (more tireless than me) efforts to shut this garbage down.

Nah, I only PM mods if it is absolutely and truly necessary and, besides, I explained why the OP should be banned and the thread locked when I reported the OPs of these threads.. In fact, I've reported the OPs multiple times with a similar explanation given just in case different mods attended to each report.

What is so frustrating is that it is so blatantly obvious that the conversations occurring in these threads are endlessly recycled and often nonsensical, even if they no longer qualify as plagiarism, per se. The smart thing to do - and one requiring the least amount of time/effort by the mods - would be to lock the thread and ban the OP (or at least just lock the thread). The worst that could happen is the OP creates a new account to complain in meta which would basically result in a lot more people looking at their misdeeds and concluding the banishment/thread-locking was righteous and just.

Meh... not anything I can do about it except not bang my head against this proverbial wall.

It's been a couple weeks and both the Neluns and SafeInsure scam threads are still going strong after learning to not plagiarize/recycle old posts, while the Neogame.io campaign has admitted defeat and cancelled its ICO. So, 1 win; 2 losses.

Since the mods were requiring multiple examples of plagiarism before banning what were obviously stolen accounts co-opted by the thread bumping service I've basically given up. Hunting for plagiarists while I drank my coffee each morning was an entertaining pastime, and deprived of such I found my interest in the forum overall waning.

^^^@tranthidung - I don't bother reporting posts for pyramid quotes for much the reasons you said. Mods were requiring multiple examples of plagiarism before banning accounts and that should be a "one and done" type of violation; who knows how many pyramid quote posts would be required before banning, and even then its likely to be a warning first. Basically, a case of, "ain'tnobodygottimefodat."

Sure, the interval between sprouts with just 5k beans is quite extended, but I should have received at least one sprout by now (it's been 9 months). I may buy another 15k beans to bring the sprouting interval down to around 2 months, but no way am I going to spend more than this token amount - another $18, basically - on a project I otherwise never viewed as anything but an interesting experiment.

1.7.0 is working great for me on my 4x RX 560 (XfX 2GB) rig mining CNv8. I'm getting 460-490H/s per card with intensity set to 25.0 and using MSI AB 4.5.0 to set core at 1200, mem at 1900 and 100% PL (running an Anorak powersave BIOS). I really like the restart miner if hashrate drops below a certain value function as it seems that one or both of the middle two cards on this rig will drop in hashrate by about 150H/s every so often.

All in all, I'm happy to pay the dev fee vs. running xmr-stak compiled to have no devfee, as the latter barely did better than 400H/s per card and it had stability problems when it did run. Unfortunately, I am running at a razor thin margin of profitability vs. power cost right now, and it is only because the weather turned cooler recently that I am keeping this rig running at all (everything else was turned off and/or sold earlier this year).

It would be far, far better to just lock the thread (and ban the OP) but given my experiences reported above I'm not holding out much hope that will happen. I haven't tried reporting bots for pyramid quoting, mainly because I am skeptical they will be marked good but I'm also not really how sure how best to word my comment for such. I might ask Welch in his guide thread about that when I have a few spare minutes.

Took the other side of this trade; NVDA likely hasn't a sold a single damn GPU in the last quarter; the 20xx series hasn't inspired much beyond yawns; recent game releases have gone full retard on the social justice thing and core gamers ain't having it.

Consequently, I've loaded up on the NOV23 190/185 put spreads because I'm bearish but I like to limit my risk.