The brand expansion sounds great and all.
What about ASIC Resistance?
The Discord ASIC Resistance Channel is spammed to a point of making it inconvenient for a developer to respond to my questions. I ask for an update and if they have used PROG Proof of Work on a Test Net but NO response; NO update; nothing!
I honestly don't want to interrupt developers and let them do their job rather than spend their time responding to guys like myself who's asking for an update regarding their work on ASIC Resistance. If a developer wanted to even find my question to them about ASIC Resistance, they would have to comb through at least one hundred posts in the ASIC Resistance forum on Discord. That takes valuable time away from developers to actually work on ASIC Resistance.
Bottom Line: The ASIC Resistance forum on Discord is full of spam from Pro ASIC and Anti ASIC rhetoric that allows no convenient communication with developers in a meaningful and profitable way for all of those involved in the discussion.
MedaR,
It certainly would be helpful if you could find out some kind of update for us, please. It would be nice if you could keep us updated on ASIC Resistance WHILE allowing developers to do their work on ASIC Resistance; if they are actually doing any work in that regard.
Is there a team devoted solely to development on ASIC Resistance? If so, where are they at this point? If no team appointed, then why not?
Can you please ask the creator of the Discord server for ZEN to create a forum ONLY FOR CONFIRMED DEVELOPERS? This way they can post updates on ASIC Resistance WHILE BLOCKING others who are not developers from spamming the forum.
Updates PLEASE...
If you piece together the clues from the official announcement and the talk on the ASIC Resistance discord channel, you will know that the devs and moderators have weighed in on this subject. Here's what I have gleaned...
- Switching parameters on Equihash will only slow down ASIC adoption. Innosilicon indicated that they could adapt to new parameters like BTG had... could be done relatively quickly... my best guess is that this would be in the fall of 2018 as the ZEN team only wants to do major hardfork activities once a quarter
- Switching to a new POW algorithm will take a lot of work, and nothing public has been mentioned about this. This would take many months of preparation... my best guess would be 2019 before it could happen
- There is currently no DEV team working on "ASIC resistance"... my best guess is because the issue is not settled
- IF ZEC did do something to slow down ASIC adoption, or implement a new POW algorithm then it would be much easier for the ZEN team to port in that codebase. One can see a lot of wisdom here, where the ZEN developers can focus on features and let the ZEC team come up with a algorithm change... the risk here is that ZEC decides to do nothing and my best guess would be that this would also be 2019
So... at best something could be done in the Fall of 2018. The middle road is to do their own POW which would be 2019. The best scenario for ZEN is that ZEC saves the day... again in 2019. Worst case is that nothing changes, and the ZEN team realizes that ASIC resistance is futile, and embraces the benefits that ASICs bring to your algorithm like better security against 51% attacks.