I can provide my single data point: I sold all my ZEN in large part because I was disappointed at the decision to embrace Equihash ASICs. Networks are secured based on the total energy cost to a first order and distribution of the hashpower geographically to a second order; ASICs tend to reduce both factors. Security is the most important and this is explained many times in this thread. This project once faced 51% attack and this had devastating effects on price, duo to various speculation which accrued immediately after this event. We cannot afford this to happen again. In case of fork we would be very vulnerable without efective protection and in this transition we could be an easy targerg for another attack. This decision not to fork was the most rational decision in current situation. What puts ZEN most at risk of a 51% attack (besides a fault in its consensus algorithm) is that it attracts a small minority of the total Equihash hashrate that is available globally. Consequently, as long as you can rent Equihash hashpower on NH, MRR, etc. far in excess of your coin's network hashrate you are vulnerable to attack. Again, with the proviso that your consensus algo is susceptible to this kind of manipulation in the first place. The real solution to decentralise mining is and almost always has been the blockDAG, that's why it's a fully funded project that's already well underway. On this I agree with you - DERO is a CryptoNight-based coin that has already implemented a BlockDAG type consensus algo and it has successfully withstood all attempts at 51% attack (so far, anyway). GPU mining Situation with GPU mining is not good anyway and without this fork.
GPU mining becoming less and less profitable and causes are various not only ASIC.
Horizen cannot be blamed for this situation.
Bearish Trend In this situation with lot of speculation around BTC and volatile market you cannot expect miracles. Meh. The market is partially to blame, sure, but taking just the last month as an example, BTC is down <4%, ZEC is down <9% while HoriZen is down >14%; ZEN is clearly underperforming the benchmark crypto, BTC, as well as its closest peer, ZEC. Why rebranding? Well this extending of brand and changing of logo was strategic move to avoid future potential problems. That was a good reason to change the logo, yes, but not to change the name. ZenCash had fairly good name recognition which also implied it was a currency. HoriZen, in contrast, is more of a hokey pun of a name which doesn't provide any clue as to what it is. Frankly, when I see "HoriZen" it makes me think of a yoga studio or a landscaping company that specializes in Japanese rock gardens... Also we are distancing our project form ZCash, we are not only cryptocurrencie, we are platform now  Distancing from ZEC is all well and good, but trying to claim HoriZen is more than just a currency at this point in time is misguided. This is because if you ask anyone who has more than just heard of crypto (ie - has mined or traded it) what crypto is the vast majority will say it is a replacement for fiat currencies. Trying to distance a project from the primary perceived function of crypto only makes sense if there a laser-like focus on solving a specific problem and using crypto to do so is highly advantageous. What, in essence, does HoriZen do - or intend to do - better than anything else? Send private messages? No, Telegram, Signal and even ProtonMail are better at that. Furthermore, Secure/Super nodes are just another form of masternode PoS scheme and the vast majority of MN coins are shitcoins and/or scams. Why ZEN wanted to associate itself with scammy shitcoins is beyond me, and diverting 20% of mining rewards to pay these Super/Secure nodes only added insult to injury (and made already terrible mining profitability even worse, of course). I realize this all sounds kind of harsh and I do think you, personally, are a credit to the ZEN team overall, but the coin went in a direction I no longer find compelling so I stopped supporting it. And based on the price action over the last few months - ever since the rebrand took effect, basically - the market seems to agree with me. |
|
|
|
|
Holy smokes this thread has gone off the rails... Y'all need Jesus somethin' fierce. Or maybe Cthulu...
|
|
|
|
...I much prefer to set intensity myself, however, so if anyone cares to share their settings for the 2GB RX 560 I'd appreciate it.
...
I have RX 560 2gb rig mining XMR. I use manual intensity, all cards needed lower intensity than the auto intensity. I recommend start at 26 and keep decreasing by 0.5 increment if not stable. Some of my cards had to go down to 24 and the lowest is 23.5 Core 1180@895mV/Mem 2000-2100, power limit +10% each card running 450-465 H/s and using ~36W with 18.6.1, the best driver for me. My cards needed +5 mV on the memory compared to v7. I tried 18.5.x it hashes a tiny bit more but uses more power ~40W v8 is more hungry for virtual memory, I have it set at 3x total vram. I also recommend using a reasonably low static difficulty with XMR, variable difficulty can get too high and cause stability/pool problems with weaker cards like the 560. Thanks for the reply - you got my last sMerit for it! After making that post I poked around the log file created by SRB and found the intensity it was setting for the cards: all are at 26.0. I was using OverDrivenTool to set all the clocks and voltages for each power state but I found it cumbersome and once MSI AB was able to deal with 3+ AMD cards again (ie - v4.5.0) I switched back to it. Unfortunately, I haven't been able to unlock core voltage adjustment yet, and as I recall that was another reason why I switched from AB to ODT. At any rate, my 4 cards are consistently doing 460, 420, 420, 460 and using an estimated 54W each (based on Kill-A-Watt monitor, minus the amount used by the system when not mining) and 1200 Core / 1900 Mem and -20% on the power limit, so you are totally kicking my ass in power consumption vs. hashrate. Clearly I have some more tweaking to do but right now I am just happy I got it working stably on v8. |
|
|
|
This is a normal practice, but I think the policy against the merit abuse has changed a bit the last few weeks. I got this message deleted /my comment in green/ I know it was for off-topic but I just archived the request for merit. <PM snipped> Yeah, my post in the same thread was deleted as well. I figured it might be for not being strictly on-topic, but if merit-beggars aren't publicly humiliated then they won't stop begging. BTW - After Coin-1 posted that list of people "most generous to newbies" I received a couple of PMs surreptitiously asking for merits. Because they weren't outright asking me for merits I just warned them that if they were any more direct in their requests they could expect to receive red trust from a DT member, but if I received a PM like the OP showed from argio I would definitely report that for spam and try to get a DT member on the case. |
|
|
|
Sorry, I was far from clear. I meant it should have forked away from ASICs.
Can you back that argument up with some evidence? Current value could be the end result of multiple factors. I can provide my single data point: I sold all my ZEN in large part because I was disappointed at the decision to embrace Equihash ASICs. Networks are secured based on the total energy cost to a first order and distribution of the hashpower geographically to a second order; ASICs tend to reduce both factors. Also, I thought the rebrand was stupid and HoriZen seems to be losing its way by trying to be too many things at once. While the goal of being a platform sounds good, it really is a solution in search of a problem right now; maybe in 10+ years when (if) crypto is in widespread use a platform will be more compelling, but right now I am much more intrigued by coins that provide a solution to a niche problem (e.g. - LTHN and its crypto-based VPN) or which are focusing on a single, if more broad, application (e.g. - DERO's private smart contracts or MUSIC's new way of directly compensating musicians per play). |
|
|
|
|
I've been using xmr-stak for about a year now, but I just switched over to SRBMiner on my 4x RX 560 rig because the former program is seriously buggy when set to CNv8. Hashrate is just slightly higher than xmr-stak - 1765H/s vs. 1735H/s (not accounting for lost time due to crashes, stuck cards, etc...) - and power consumption is just slightly lower - 355W vs. 375W - but this is letting SRBMiner pick the intensity (double threads set to true). I much prefer to set intensity myself, however, so if anyone cares to share their settings for the 2GB RX 560 I'd appreciate it.
FYI, I had to downgrade from Adrenalin 18.6.1 to 18.5.1 to get SRBMiner to work; prior to that the driver would crash hard - blue screen reboot hard - as soon as it reported it had logged into the pool (so, presumably, as soon as it tried to generate the first share). I have no idea why 18.5.1 works when 18.6.1 didn't, but that's computers for you.
|
|
|
|
After the dev's lie to community, now this coin turns into a pump and dump coin?
What are you talking about? What did I miss? FUD from about 4-6 months ago that has long since been soundly squashed. |
|
|
|
Today's surprise - er, actually yesterday's... - is this seemingly innocuous and not-at-all-shitposty post that starts off like this: ...
In the past few months, we were waiting for the establishment of the fund which had to invest in our project on a pre-sale stage. That was necessary to start the ICO. Unfortunately, the participants of the fund have decided to suspend all investments in crypto industry due to downfall of the cryptocurrency market. In this regard, we decided to stop waiting and not to do the ICO. All funds we have collected so far will be returned.
...
This post might not seem to qualify for this illustrious thread, but the key here is that it is the 16246th post... in a bounty thread. Yes, kids, that's >16k bounty reports that just got rendered moot. Bam! |
|
|
|
Thanks for clearing that up. So it seems like there's a lot of guys mining in vain right now (including me up to a couple of hours ago^^).
Yes, mining right now might be a waste of electricity, especially on that shady cryptoknight.cc pool. I'm still chugging along on lethean.west-pool.org and my total due is increasing, even if no payouts have been made in the last 8 hours or so. |
|
|
|
Really.
when the answer is already given - which of the chains is correct?
What, do I need to click on the link I just gave and read back the results to you?  |
|
|
|
So what about the pools? it seems like hashvault and cryptoknight have both a lot of comp power, but they are on completely different chains. What do the devs consider the "correct" chain?
You can check which pools are on what block here: blockharbor.net pool health. However, payments have been paused while the devs look into a possible 51% attack which appears to have been launched by the cryptoknight.cc pool operators. |
|
|
|
purify the forum from useless users.
A perfect description of yourself. <plagiarism example snipped> Instead of merit, you'll get a ban now. That is how this is supposed to work! Outstanding!  EDIT - more on topic, a post of mine to the self-moderated Neogame.io thread I mentioned above was deleted by the OP. I think it's time to recommend the entire thread be nuked for using bump-bots. EDIT 2 - my cheeky post with the facebook wall meme was deleted, apparently - hopefully there are no hard feelings, as I was just having a bit of fun with the merit-beggar-turned-plagiarist. |
|
|
|
...
UPDATE: in a fit of pique I deleted the amd.txt file for both rigs and let xmr-stak automatically generate them. Hashrate is depressingly low - 1020-1060H/s for the RX 570 + Ryzen 5 1600 system (previously ~1180H/s), and <1600H/s for the 4x RX 560 system (previously ~1900H/s), but at least it isn't crashing anymore (and I hope I didn't just jinx myself...).
yeah with the upgrade, all the .txt files need to be re-generated (has something to do with formatting and variable fillout for the new variables stored in the file). ... Hashrate seems to be minus 1/4-1/3 or so compared to cnv7 (accounting for my 470 when it was plugged in as well). So far, no issues with the rx560. I'm still trying to dial everything in with respect to stability and hashrate but as of now I have gone back to 2 threads on the RX 560 rig, using all the other auto-generated parameters except reducing the intensity to less than half what was specified for 1 thread operation (e.g. - 768 for 1 thread goes to 376 for 2 threads). Right now the 4x rig is doing a little over 1800H/s so a massive improvement from the <1600H/s I was getting before! However, I just made this change so now I need to see if it remains stable as I was still having problems with the 1 thread/768 hashrate config (e.g. - hashrate dropped from 400 to 300 on one of the cards sometime over the night). I'm still also still running the RX 570 system with a single thread, worksize of 8, and 768 intensity for now, mainly because I want to see how the other rig behaves before wasting more time fiddling with this one, but I suspect I will be doing the same tweak in a few hours. It only made sense that things went the way they did (more power draw, harder on hardware, etc), because its the only way to overwhelm the FPGAs. ... Totally agree - I have slowly but surely come around to the idea that it is the energy cost that determines how secure a network is to the first degree, not the absolute hashrate or cost of the mining hardware, per se. One of the coins I was an early supporter of that remained on the original CN algo (DERO) has a network hashrate in the range of 400-500MH/s which works out to around 2000 ASICs and 1.2MW total power draw. Prior to being ASIC'ed it had a network hashrate of around 4MH/s which works out to ~5300 RX 570 GPUs drawing ~800kW of power; hardly an improvement in network security, really, at the cost of alienating a massive number of previously loyal GPU and CPU miners, but I digress... UPDATE: Hashrate dropped on one of the RX 560 (not the same one) yet again, then the display driver crashed so I decided to DDU 18.6.1 and install 18.5.1, then pixel patch and set all the cards to compute mode. I also stopped using OverDrivenTool and switched over to MSI AB, as v4.5.0 is once again able to handle more than 3 AMD GPUs. I have core set to 1200, mem set to 1900, power limit set to -20%, no change as of yet to core voltage, and total draw is at an unhealthy 375W with hashrate at 1740H/s. So a slight drop in hashrate, a rather higher increase in power draw, but if it's more stable I'll consider that a fair trade overall. UPDATE 2: Well, I finally gave up on xmr-stak on the 4x RX 560 rig because it kept losing hashrate on one card then outright crashing the driver if I ignored that long enough. Even though I had no luck with SRBMiner 1.6.8 before, I decided to give it another go since I downgraded the driver to 18.5.1 and whaddyaknow, it now works. It's only been running about 10 minutes so far, but delivering a fairly consistent 1775H/s at 356W; so, a little better hashrate and a little lower power draw. Neither are enough of an improvement to justify the 0.85% dev fee, but if it can stay up for longer than 4 hours without needing a reboot then that will be worth the fee to me. I'd like to stick with xmr-stak on both my rigs, but v2.5.1 clearly needs some bug-fixes and/or additional tweaking. |
|
|
|
|
For those having issues with the new wallet (v3.0.0.b3) you'll likely need to do the following:
1. Remove blocks from the db until height is below 296482 using this command: lethean-blockchain-import --pop-blocks <number> where <number> is the number of blocks to remove. For example, my db was synced up to around 302000 so I needed to remove >5518 blocks; I entered 6000 just to make sure.
2. Run the lethean daemon with two exclusive nodes specified: letheand --add-exclusive-node 195.201.202.36 --add-exclusive-node 85.86.97.63 Not doing this will result in the daemon trying to add back all those blocks you just removed.
3. Copy the .wallet and .wallet.keys files from your old intensecoin wallet directory into the new lethean wallet directory and run the wallet client (i.e. - lethean-wallet-cli) entering the full name of the wallet you copied over (e.g. - lthn.wallet) then enter the command: rescan_bc to eject any coins received after block 296482 (those are worthless/invalid).
The last command will take awhile to finish and the daemon needs to be running the entire time.
|
|
|
|
...I am seeing your avatar as Stich or whatever it is called. Blue, furry and toothy  I remember that you had something less memorable before but we already established my memory is not to be trusted...... I always thought of suchmoon's previous avatar as a cross between the alchemy symbol for female and the IEC symbol for a power switch... Obvious pun is obvious. |
|
|
|
|
Well, I have to amend my earlier comments about it being painless switching over to 2.5.1... The CN coin I mine - LTHN - just switched to CNv8 and now I am dealing with unrelenting driver and system crashes. I just DDU'ed the 18.5.1 driver and installed/pixel-patched 18.6.1 to no avail. I've also bumped up the core/mem voltages to as high as they were stock (ie - no power saving) and that doesn't seem to help, either.
So I next decided to try SRBMiner and it is crashing the driver, too. I'll keep plugging along for another hour or so, but after that I am just going to stop mining completely.
UPDATE: in a fit of pique I deleted the amd.txt file for both rigs and let xmr-stak automatically generate them. Hashrate is depressingly low - 1020-1060H/s for the RX 570 + Ryzen 5 1600 system (previously ~1180H/s), and <1600H/s for the 4x RX 560 system (previously ~1900H/s), but at least it isn't crashing anymore (and I hope I didn't just jinx myself...).
|
|
|
|
|
While it isn't official, yet, the pool at lethean.west-pool.org:6666 is operating on the correct chain and accepting CNv8 hashes. I am using xmr-stak 2.5.1 (but with some stability issues, as well as noticeably higher power consumption against lower hashrate) but whatever miner you like that does CNv8 should work.
|
|
|
|
... hip hop and away...  359 posts and 2 maritz; that sounds about right. Please come down to the lobby to pick up your consolation prize:  |
|
|
|
...
Dero is on a tear - it's up about 4x over the last month or so, likely due to finally getting some marketing going for it.
Congrats, is the premine locked now? Yep - the premine was locked with releases scheduled over time. So, moving in the right direction, but for risk/portfolio management I sold a chunk of my dero position, anyway, and used the proceeds to buy more XMR and ETH. |
|
|
|
Yeah, I just threw him on ignore months ago but probably should be reporting him.
Hey how did that shitshow turn out on dero?
I completely forgot about that.
Yes, help me out with the reporting! Dero is on a tear - it's up about 4x over the last month or so, likely due to finally getting some marketing going for it. |
|
|
|
|
Show Posts
