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...
hey apologize for the seeming clutter / chaos in the Discord channel, just shows how contentious this can be and how passionate some folks are about their perspectives.
long story short, #1 priority is successful 51% attack mitigation--hands down most important thing to implement immediately--next up is ASIC res issue. all the usual suspects on the table as far as options go--param shift, new algo, or do nothing. Good news is that 51% code is done and looks good under internal review and testing, looking to release to public testnet next Monday. Depending how all that goes, dev resources will rotate to ASIC issue.
hope this provides some clarification, though i know folks are waiting for something firm. sometimes holding real options in reserve while focusing on other priorities ends up being the best strategy.