Goals:
- Unity amongst all Threshold contributors.
- Accurately reflecting our decentralized nature.
- Avoiding any regulatory issues based on language.
Communication Guidelines:
- T is a “work token” with additional utility around participation in DAO governance
- Threshold is a DAO and we are all contributors (NuCypher, Keep, Guilds etc.)
- We shouldn’t refer to the NuCypher and Keep Teams as the “core team”. “Contributor” better captures our decentralized nature. NuCypher and Keep are contributors to Threshold.
- We shouldn’t use “convert” when talking about NU/KEEP tokens going to T - it is an “upgrade”, and when going the other direction (T -> NU/KEEP) it is a “downgrade”
- Try not to use “vote” with respect to DAO governance. Alternatives include:
- “proposal voted on by the DAO” → “proposal validated by the DAO”
- “the DAO vote has passed” → “the DAO proposal has passed”
- “the community votes on governance proposals” → “the community participates in governance proposals”
- “the process requires a DAO proposal and subsequent DAO vote” → “the process requires a DAO proposal and subsequent DAO approval”.
- “An onchain Token Holder DAO vote to mint the required T…” → “An onchain Token Holder DAO proposal to mint the required T…”
- “In preparation for the first onchain DAO vote we created a proposal to standardize…” → “In preparation for the first onchain DAO decision…”
This is not a comprehensive list, and the overall goal here is basically to avoid the use of “vote”
- Don’t emphasize anything about a potential investment, potential revenue, price appreciation, or ROI. Instead, focus on the utility or function of the token in the platform i.e. T is staked to secure the Threshold Network, and for governance
- Nothing about guaranteed fees/rewards
Threshold Communication Guidelines
Communications Guideline Jun23