-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new roles #16
Comments
I like |
I like it a lot. everyone will want to have them |
@cheo0202 I share your desire for new roles that better work within our community. Specifically, the collabland bot we use in the discord server has gone untouched for months. We could use tokenized roles to better align the DAO and bring like minded people together. I'm curious to explore this further. However, this proposal is missing some key topics and what is actually being proposed. Some questions I have.
Can you answer some of these in the proposal? |
What are the role names you are suggesting? How many tokens should be required for "hold PRTCLE" and LP? Will you be in charge of collabland bot and creating the roles Why would people seek to obtain the roles, is there anything we can do to make these roles more valuable? I hope there clarified your doubts and thank you for taking the time to contribute to my idea. |
l like |
Are there any airdrops you think the community would want? |
---
SHEiP:
title: < new roles>
author: <jose coronado (@cheo0202)>
discussions-to: <URL of the Github issue for this SHEiP (if this is a PR)>
status: < Idea>
category: < Standards>
type: < Community>
created: <2022-02-18>
edited: <date created on, in ISO 8601 (yyyy-mm-dd) format>
requires: <N/A>
replaces: <N/A>
---
Simple Summary
< create new roles for discord community>
Abstract
< Currently there are no roles to encourage the community in discord to keep project coins
Creating roles that identify you to perform these additions is likely that more people participate>
Motivation
< The reason why I am making this proposal today is because I see many projects carrying out this action to give merit to their community over the hold or the creation of LP>
Specification
< This proposal is made to create the following roles...
hold prtcle
hold pants
pants burning
LP builder
Rationale
< I think that seeing these roles the community will seek to obtain them and contribute more to the growth of the project>
Implementation
< !--The implementations must be completed before any SHEiP is given status "Final", but it need not be completed before the SHEiP is accepted.-->
Implementation goes here.
Security Considerations
< !--All SHEiPs must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks and can be used throughout the life cycle of the proposal. E.g. include security-relevant design decisions, concerns, important discussions, implementation-specific guidance and pitfalls, an outline of threats and risks and how they are being addressed. SHEiP submissions missing the "Security Considerations" section will be rejected. An SHEiP cannot proceed to status "Final" without a Security Considerations discussion deemed sufficient by the reviewers.-->
Security considerations go here.
Copyright
Copyright and related rights waived via CC0.
The text was updated successfully, but these errors were encountered: