LOL, I seem to have a struck a nostalgic nerve here! 

Where's the DOS 4.01 wallet? 

Just that it requires a lot of hashrate to mine DERO (ie - the difficulty is high). Today isn't so bad, but for most of the last 3 months my 1.9kH/s Cryptonight rig would only make about 4-6 DERO per day.

Aww, shucks...  

This coin may be difficult to mine, but the project is easy to support especially compared to all the unsavory pump-n-dump and Ponzi scheme coins out there.

@Desp suggested I switch from port 5555 to 7777 and that seems to have greatly reduced the disconnects - so far only 1 in 2 hours, where before I was getting disconnected every 10-30 minutes. I'm still seeing about 2.5% rejected shares, though, but this is likely due to my distance from the server.

That said, I've temporarily stopped mining XUN because of the NiceHash attack. And note that even if the "officially sanctioned" pools agree to not allow NH, all it takes is one pool letting them in to screw up your entire network. The same thing happened to DERO a couple months ago and the dev just gave up on trying to keep NH out (the "if you can't beat them, join them" approach).

EDIT - looks like ITNS is getting pounded by NiceHash, too. Network hashrate for it is now at 20 MH/s when it is normally around 5 MH/s.

Yo @CaptDero, did you change the priority for outgoing payments on the official pool because the last one sent to me occurred 40 minutes ago but it still hasn't shown up in the wallet and the daemon reports it is synced up.

Normally I wouldn't worry about this, but Windoze decided to update itself* on the computer I run my wallets on (no mining) and I've had a helluva time getting everything working again.


* - and yes, I stopped the Windows Update Service, but that no longer seems to be a sure-fire way of disabling updates.

EDIT - just as I posted this the transaction went through, so this message is moot. Leaving it here just in case anyone else wonders about their mining payments.

You probably can't without physically inspecting the chips used.

Those of you running Awesome Miner might want to check out this thread which reports a potential vulnerability: https://bitcointalk.org/index.php?topic=3114689.0

I really dislike Discord, but okay... Same username there as here.

Am I the only one getting frequent disconnects (socket error: invalid target) and a higher than normal rate of rejected shares (for invalid solution) of around 2.5% on alpha.ultranote.org? I'm using xmr-stak 2.2.0 and don't see any such problems with other CN coins (DERO, ITNS, TRTL and EDL).

Also, the alpha pool doesn't seem to accept pings, but my ping time to beta.ultranote.org is a bit longer than I would like to see at 121ms so I'm assuming it is the same for alpha. Maybe the above issues are due to a longish packet transit time?

You are really playing with fire shitposting to this thread, then quoting your own shitpost in yet another shitpost of a reply. This is the very definition of sig spamming.

Can you explain how to do the reset command, because after Windows 10 did it's usual and infuriating update and reboot last night my wallet is stuck at, "Waiting on Daemon to start sync..." and manually running walletd.exe as an administrator only shows the command window for the briefest of moments. I double-checked that both the daemon and wallet .exe files have access to public and private networks via the firewall permissions and I also tried running turtlewallet.exe with the /reset switch just in case that is what you meant by, "doing a reset command". No joy.

So, a bit of help would be welcome...

EDIT - wallet also updated itself: current wallet version is 1.0.6625

UPDATE - I reinstalled the previous wallet version - 1.0.6617.7 - on a different computer, copied the .dat file over to it, permitted the daemon access to public/private networks, skipped installing the new version when prompted and now it seems to be working correctly. So it appears something broke in the wallet update.

Yeah, I remember CaptDero saying to keep mining on the official pool, but my personal philosophy, learned the hard way, is to stop mining a coin whenever there are chain split issues with it. I normally point my highest hashrate rig at DERO because it is so damn hard to mine, but while all the forking mess was going on I shifted it over to some rinky dink Cryptonote coins and pounded the proverbial crap out of them. Good times.

Since no one seems to have posted about this to the TRTL thread yet: https://asicminermarket.com/product/baikal-giant-n-monero-miner/

Basically, an ASIC miner for Cryptonight that does 20kH/s...

Hah, I just voiced a similar suspicion in the DERO thread, which you have been known to frequent as well...  

There almost certainly was some premining going on based on the step change in difficulty of several CN coins starting about 2 months ago, but I did not see the same increase in difficulty occur with ITNS (or a couple other even smaller CN coins I have mined such as IRD, TRTL & EDL). That's likely because Baikal didn't even try to do any premining of the small CN coins because they knew it would be self-defeating; the same restraint/judgment will not be shown by the buyers of these miners, however.

Yeah, okay, I admit I might have gotten a little over-excited there. How much damage is done to any one CN coin will depend on just how many of the Baikal Giant N get pointed at it and there isn't likely to be all that many released in the first batch. But I don't think I need to tell you that a coin with a network hashrate of 5-6 MH/s is not going to fare nearly as well as XMR which is hovering around 1 GH/s.

Perhaps, but Baikal says they will be shipping their Giant N cryptonight miner in about a week so any CN coin that hasn't hard-forked to stop it is going to get the SIA treatment.

I suspect this also explains DERO's peculiarly high network difficulty for the past few weeks, as Baikal, just like Bitmain, undoubtedly does "extensive testing" of their miners prior to shipment (ie - uses them to mine for themselves first).

I will sell off all but a token position of any CN coin I have mined that does not hard fork to protect itself against the Baikal Giant N. You basically have 2-3 weeks to get your shit together or you can experience what SIA just went through.

Because changing the computation - ie, tweaking the algo - renders the ASIC obsolete (the computation is literally hard-coded into silicon) and this won't affect GPU/CPU software at all (just change the code and recompile).

EDIT - sorry, I didn't address your actual rebuttal that if the entire network hashrate decreases then - presumably - so will difficulty. Yes, that may work.

This is my understanding as well, but one problem with increasing the scratchpad size to defeat ASICs is that it also reduces the hashrate of GPU/CPU miners; perhaps monotonically So that seems like a shoot-yourself-in-the-foot kind of solution.