It sounds like miners will get their earnings cut by an additional 16.5 percentage points; correct?

Interesting idea that sounds somewhat like what RavenCoin and PigeonCoin do. They use 1 of 16 well known/established PoW algorithms on each block, with the algo chosen randomly for RVN (X16r) or shuffled for PGN (X16s). While this approach can theoretically be ASICed just like any other, it would require a massive undertaking to implement all 16 algos on one chip and therefore makes it supremely uneconomical.

Note, however, that one of the things I like about mining CryptoNight is it uses much less energy than, say, Ethash or Neoscrypt (to name 2 algos that do well on AMD cards). Conversely, one of the things I don't like about CN is that it sucks on Nvidia cards (a $1000 GTX 1080 can barely exceed a $150 RX 560).

While I do agree that DERO would be seen as a trailblazer for coming up with a truly ASIC-proof algo, I also agree with @cpmcgrat that this would be a major distraction versus pursuing smart/private contracts. Also it would invalidate all the work that CaptDero just did on rewriting DERO in golang, and I rather suspect that would be difficult for him to toss out. Hence I still think that either going with CryptoNight Heavy or following Monero's lead are the least-risky courses to choose from.

Wallet 1.4.2 successfully resynced from scratch and all my ITNS are back. I also successfully exported the 256b mashup of all 4 keys and separated them out to be able to use the new rebase wallet, eventually, according to the seriously convoluted instructions in this reddit: https://www.reddit.com/r/IntenseCoin/comments/89gw15/guide_converting_your_141142_wallet_to_the_145/?st=JFSFQH68&sh=236d5812

However, it is still a mystery why I needed to delete the %appdata%\intensecoin folder and resync from scratch in the first place, as Windows had not crashed with the wallet open, which was the likely cause when I had to do this before. So, a puzzle wrapped in an enigma, or whatever.

There are no tokens, there was no ICO. Are you a bot or a moron?

When I first started mining ZEN - it seems like it was just months ago... probably because it was  - I tried Suprnova and had uniformly bad luck with it. Perhaps I'll give it another shot. I just recently tried zen.miningspeed.com and received an unbelievable 0.057 ZEN after 24h at 2800 Sols/s... which makes that the worst payout, ever, topping the previous contender which was 40% of expected BTC from multi-coin mining the Neoscrypt algo on Zergpool (avoid that one like the plague, if it is even still around).

Yesterday was terrible for me too on Zhash.pro. Every pool with PPLNS/PPLNT seems to have it set very conservatively to start dropping your older hashes if it takes even a slight bit longer than average to find a block. To Zhash.pro's credit I once called them out on this very issue and they actually looked into it and made some tweaks that dramatically improved profitability. However, I have come to the conclusion that PPLNS/PPLNT is a bad deal for everyone except pool operators. Sure it punishes pool hoppers, but it does not actually reward those who loyally mine day in/day out as proponents of these payment schemes try to claim.

I've just resigned myself to receiving an average of around 85-90% of whatever minethecoin.com predicts based on average hashrate and 24h difficulty.

I'm an EE and I can assure you if Bitmain, Baikal, etc., truly used ASICs - rather than FPGAs - then they absolutely cannot be changed after manufacture, not even to do something as simple as a logical invert on a single bit somewhere in the algo. This is because the functionality in an ASIC is purely hardware-based, not software, and unlike an FPGA, this functionality is - quite literally - burned into it. Now, an FPGA - Field Programmable Gate Array - is usually considered a stepping stone to an ASIC in that it implements functionality in hardware, but unlike the ASIC the hardware is an array of, well, programmable gates (actually, logic function blocks connected to an I/O matrix). This allows changing the algo in an FPGA even faster than one can load a different mining program on their desktop, but the tradeoff is that FPGAs are generally an order of magnitude or more slower than an ASIC and an order of magnitude higher in cost even if every last LUT and I/O pin is used (which is never the case).

Roughly speaking, FPGAs are nearly as flexible as a GPU, use less power for a given hashrate, but can cost nearly as much; ASICs are a one trick pony with the highest electrical efficiency but which are very cheap to produce (but very expensive to develop), relatively speaking.

The change that Monero made to go to v7 is fairly minor and the current ASIC design should be easy to modify, so, yes, the next batch of ASICs could very well do both the original CN algo as well as v7, but the existing batch of ASICs can only do the original CN algo and nothing else.

Hence why I said the only surefire way to block ASICs is to change the algo - even slightly - every few months. It would still be possible to make an FPGA miner, but those are far less of a threat to decentralization than ASICs for the reasons outlined above.

Yes, I have noticed that Windows Defender has been flagging more wallets as malware lately and have adding them to the exception list proactively. It's getting to the point where I am going to give up and just add c:\ to the exception list and be done with it completely.

As I mentioned already - ahem - the old wallet, and the new one, would sync a few blocks each time I ran either of them before hanging. However, the problem with the new wallet may have been because I used the blockchain import binary to - theoretically - bootstrap the blockchain for the new wallet but I had failed to rename the old %appdata%\intensecoin directory first... so, files likely got overwritten or corrupted or something. Anyway, I renamed said directory and have proceeded with syncing the blockchain all over again with 1.4.2 so that I can - hopefully - recover my wallet


Wow, those are some seriously consumer-unfriendly instructions and not at all what I tried to do on my own (which may be why what I did didn't work). I'll give that a shot after 1.4.2 finishes syncing and if it keeps crashing, because to be perfectly blunt, I am sick of beta testing wallets and hard forks this week.

I am experiencing similar problems with the new wallet beta, 1.4.5, except this time the daemon syncs up fine but the GUI wallet hangs after a random number of blocks are synced. Since I've been screwing around with this for nearly 2 days, which is about 47.75 hours longer than I should spend on a wallet software upgrade, I renamed the %appdata%\intensecoin directory and am starting over from block 1 with the 1.4.2 wallet.

Also, the instructions for importing an existing 1.4.2 or earlier wallet into the 1.4.5 wallet are incomplete/incorrect, but seeing as I can't even the newer wallet to work I can't really provide more details than that.

An increase in the network hashrate from 10MH/s to 20MH/s is equivalent to 13500 additional RX 570 GPUs coming online. If that happened over the course of several months I'd believe it was organic growth, but not in the span of a few days. Also, network hashrate has dropped back down to ~10MH/s even more quickly than it ran up, but not instantaneously as happens with NH, so the obvious conclusion to me is that a bunch of ASICs focused on DERO for a couple of days then moved on.

That said, I really think that waiting until ASICs nuke your network is the wrong approach anyway. Now that it has been proven that CryptoNight is not, indeed, ASIC resistant, all coins that use the CN algo should modify it every few months to ensure Bitmain and other bad actors can't pull the same sleazy stunt of developing an ASIC in secret, mining the shit out of it for a few months, then dumping it on the public for a price that all but ensures it will never be profitable.

Mind you, I have nothing against ASICs and would actually much prefer everyone used them rather than inefficient GPUs, but the world we live in right now makes it difficult for people/companies in countries where the rule of law is preeminent (the US, EU, etc.) to compete against companies in countries we can't touch legally and which have no compunction about stealing your IP or reverse engineering it then churning out copies made by slave laborer children (can you say, "Foxconn"? I thought ya could).

Wrong thread - this is for a fork of xmr-stak that was compiled without the devfee and with colored text output and it has not been updated for the new Monero algo.

Wait, how would you know if there are ASICs present if they are on a private pool or solo mining? I understand how you can figure this out on the official pool - and likely get this information from other public pools on the network, but not from private pools or solo miners.

Not that I doubt you, just that I am not aware of how this can be determined, especially for a CN coin which ensures privacy by default.

PIA seems to overlap with TorGuard, or am I missing something here?

EDIT - unlike the OP, I'm not worried about the government, but I have had two attempts - that I know of - to redirect my miners to another wallet, and I am strongly considering a VPN for that reason as well as just the general creepiness with Google and Amazon following me everywhere I go and then serving up ads/product recommendations based on such. That just creeps me the fuck out, really, and makes me even less inclined to buy whatever they are selling, but I digress....

FWIW, most of his posts are to the Tokens subforum under Altcoins. I'm probably much more interested in altcoins than you, and even I don't bother with the tokens and ICOs on account the vast majority of them are scams.
 


Lol, I was going to write the same thing right before putting him on ignore. @tsoyens01 is clearly fishing for merit by repeatedly posting to Meta, but didn't get the memo that shitposting here will just get him added to the ignore list of the very people most able to give him merit. Looking at his post history only cements my decision to ignore him as just and good.

Actually, it hasn't been answered even once: we have only been told there is a good reason for delaying implementation of any of the several solutions under consideration, not the reason itself, nor even a timeline for the deployment of a solution. Consequently, all I know right now is that mining DERO with a GPU or CPU while its network hashrate is >12MH/s is like throwing a hotdog down a hallway. So I'll buy the equivalent of a few weeks worth of what my rig would mine pre-ASIC invasion and have said rig do something more productive with its hashpower.

So, wallet 1.4.2 is now unable to sync more than a few blocks each time it is opened and hangs when exiting, forcing me to kill the process with task manager. I see there is a new beta wallet available that seems to address a similar issue, but I am not real keen on beta testing wallets, nor on having to delete the entire %appdata%\intensecoin directory tree and start over from scratch, but it looks like I'm going to have to do one or both.

Huh... I wonder if this is why I have twice received a PM from a sig campaign manager welcoming me to their campaign and reminding me to wear the signature. I thought this was a new form of spam, but looking into one of the campaigns further I see my username on their google spreadsheet with an ETH address that most certainly isn't mine.

But again, what is the point if I don't wear the signature? Whoever used my username with their ETH address isn't going to comply with the sig campaign rules and therefore won't get paid, right?

<NB - I have not participated in any bounties or sig campaigns so not totally clued in on how this works, but I did watch from the sidelines as one of the Intensecoin campaigns went into meltdown mode because of some snafu with Slack usernames so I assume not following the rules = no pay>

Sorry, only meat popsicles allowed.

Lol... just saw a 20 handle on hashrate. I'm done with mining DERO for now. Wake me up when the fork goes through.

I've had the best results with https://zen.zhash.pro.