NEM Naming Convention recap
There has been a useful discussion about this topic on the thread, with much input. This post is a collation of the discussion and some of the suggestions, with the aim of outlining possible options for a way forward.
NEM is a very deep rooted brand and one we are committed to building. Today, NEM has two primary protocols: Symbol and NIS1. Additional products will be available in the future.
It appears that the most pragmatic solution presented thus far, is to implement change to the NEM NIS1 name and to add a NEM prefix to both protocol brands.
Whichever option is adopted, the feedback is clear that the focus going forward must be on simplicity and clarity, enabling easy navigation for everyone in our community to find what they need within the NEM ecosystem and for the two blockchains to thrive both independently and as part of the NEM ecosystem.
The Challenge
We have three brand components in our ecosystem, two of which use the same name.
NEM (the ecosystem), NEM (the NIS1 blockchain), and Symbol. There is a need to create brand clarity between ecosystem parts and protocols.
A quick recap of the problem we are trying to solve.
People outside the community see NEM as a blockchain, not an ecosystem. For many new people NEM = XEM.
People searching for NEM need to understand that both Symbol and NIS1 exist within the NEM ecosystem.
Using NEM more clearly as part of the 2 protocol names would help support and build the NEM brand and provide clarity on the fact that NEM has 2 blockchains.
There is clearly a need and desire to find the most straightforward approach and come to a timely decision.
It is clear that we must focus on building the Symbol brand as a priority.
Some of the practical suggested ideas include
NEM is the ecosystem brand and therefore the priority long term for brand building. We therefore should use NEM as a prefix wherever possible to bring coherence and brand awareness.
Symbol and NIS1 are protocol brands. A solution to the naming convention challenge is to prefix both protocol brands with NEM. This would bring coherence and alignment.
In this case, the Symbol name would evolve to NEM Symbol. For the V1 chain this would be called NEM NIS1. The difference with NIS1 is what to call the protocol.
Suggestions include No change (NIS1), Classic, NIS, V1, Original, XEM and a ‘new name’.
Consolidating and putting these options to a vote appears to be the appropriate next step, noting there is a minor challenge that voting only exists on NEM NIS1 right now, we will have a look at how to solve that shortly.
Websites - the official website names would align to fit.
Official social media platforms For Twitter, Instagram, Linkedin, Facebook, Reddit we should continue with NEM official to enable all aspects of content and communication for the ecosystem. (for clarity these will include both Symbol and NIS1 content).
For Community Telegram the Symbol and NEM (English) channels are being consolidated with redefined purpose, as recommended by the admin groups and supported by NEM Group.
Upon clarity of branding, separate community channels that are token specific can be explored.
In summary, what the above NEM naming convention could look like;
Ecosystem Brand; NEM
NEM Protocol brands; NEM Symbol & NEM (name*) (*subject to vote)
Tickers; XYM & XEM
Website addresses; NEM - nem.io
NEM Symbol - nemsymbol.io
NEM (name) - nem(name).io
Social channels;
NEMofficial (twitter)
Nem.io (instagram)
NEM(Facebook)
NEM (linkedin)
NEM (Reddit)
NEM Forum
NEMHub
CommunityTg Groups;
NEM Official (Symbol & NIS1) - @nemred
NEM Casual (Symbol & NIS1) - @nemberia
NEM Trading (Symbol & NIS1) - @nemtraders
This approach could provide clarity and simplicity for the ecosystem. If something like this approach was decided on, we would then work through all internal and external applications to apply this approach. For clarity, external applications include exchanges, hardware wallets and relevant pages on their sites etc.
The discussion thread is open until EOP today. After this we will consolidate and agree a way forward. It would be interesting to hear further comments and input on the above to help resolve the name challenge. A community vote will then be organised to make the final decision.
JAPANESE