Scope: This Code of Conduct applies to all active delegates, DAO Pass holders, and grant recipients. This Code of Conduct applies within all community spaces and when an individual is representing the community in public, either online or offline.
The Rules of Engagement apply to anyone using the Forum (Discourse), Discord, and other community spaces.
Colablers should actively discourage others from breaking this Code of Conduct. Colablers should report serious or repeat offenses, as outlined below. Violations that are reported using any other process will not be addressed.
The updated Code of Conduct will go into effect immediately. Policies in the Code of Conduct go into effect at the time they are included in the Code of Conduct and do not apply retroactively.
The Code of Conduct will not cover all possible scenarios and edge cases. We ask that Colablers please act in accordance with the spirit of the Code of Conduct and report rather than exploit loopholes that are discovered.
- Mandatory (Violation 1): The following behaviors are severe violations and will not be tolerated:
- 1a. Discrimination against any person based on geographical, ethnic, sexual, religious, or other identifying features
- 1b. Public or private harassment (as defined here)
- 1c. The use of sexualized language or imagery and unwelcome sexual attention or advances
- 1d. Intentionally doxxing (as defined here)
- Recommended: Colablers should be respectful of differing viewpoints and experiences and show empathy towards community members.
- Recommended: Delegate communications relating to their role in the Co-op should be transparent and public. Communication in public is favored over DMs/private communication, whenever possible.
- Mandatory (Violation 2): Colablers must not make personal attacks on the opinions or merits of proposal authors or any other party engaging in governance activity. Colablers must not make unsubstantiated claims to advocate for or against any proposal or proposal author. Delegates may make inquiries to proposal authors to validate or collect information.
- Recommended: Colablers should provide constructive feedback supported by high quality and well researched arguments.
- Mandatory (Violation 3): Colablers must act with honesty, integrity, and transparency, at all times.
- Recommended: Colablers should operate in a way and vote in accordance with what they believe is in the best interests of the Collab.Land Co-op.
- Recommended: Delegates should maintain a working knowledge of developments at Collab.Land and in the wider cryptocurrency space.
- Recommended: Delegates should make a professional and unbiased review of each proposal prior to voting. Delegates that are unable to review proposals should abstain from voting.
- Recommended: Delegates are encouraged to maximize their voting participation rate, to the best of their ability.
- Recommended: Delegates are encouraged to shape the development of Collab.Land’s governance structure by providing feedback between Seasons.
- Mandatory (Violation 4): Delegates must uphold all Delegate Commitments.
- Mandatory (Violation 7): Must execute the grant in accordance with what is outlined in the approved grant proposal. Grant recipients that wish to change the use of the grant from what is outlined in the proposal must submit a new proposal requesting approval for the change. To do so, they must follow the grants process in place at the time. If the change is not approved, the recipient must execute the grant as outlined in the original proposal or return the portion of grant funding affected by the unapproved change.
- Mandatory (Violation 8): Must distribute growth experiment or other user incentive grants within six months of the grant being made unless they give public notice to the community explaining any delay.
- Mandatory (Violation 9): Must not self-delegate token grants for use in governance.
- Mandatory (Violation 10): Colablers must avoid conflicts of interest where possible and mitigate their impact when not possible. We recommend over-communicating and disclosing potential conflicts of interest even when they do not warrant abstaining from a vote.
- 10a. Any actual or reasonably anticipated conflicts of interest must be disclosed in writing and prominently displayed ahead of any voting (i.e. when submitting delegate commitments, when running for an elected position, when making public recommendations, etc.).
- 10b. Any offer for external compensation relating to delegation or external compensation relating to Collab.Land must be promptly disclosed.
- 10c. Delegates are prohibited from approving and voting on their own proposals. Delegates may not vote for their own candidacy in an election. In the case of approval/ranked choice votes, delegates may vote for themselves, so long as they also cast votes for the remaining elected positions.
- Example: I can vote for my own candidacy on the Growth Experiments committee, so long as I also cast 4 additional votes (a total of 5 votes, as there are 5 open positions on the sub-committee.)
All Colablers are expected to abide by this Code of Conduct. Any Colabler that is found to be in breach of this Code of Conduct will be subject to the below enforcement procedures.
Type of violation:
Standard: To report a standard Code of Conduct violation, use this [reporting form.)
Grant misusage: To report grant misusage, use this [reporting form).
- For both types of violations, please cite the specific violation number (and letter, if applicable).
The Co-op Board will review the submissions. The identity of a submission author will not be publicly disclosed by the Foundation without the author’s consent.
Submission authors and/or the individual(s) or project(s) in question may be contacted by the Co-op Board for additional information, if necessary.
Individuals or projects accused of a Code of Conduct Violation may choose to admit to the violation and forego a vote. To do so, they must post a comment indicating they are admitting to the violation in the relevant forum post before the end of the relevant review period. The suspension will begin on the last day of the Voting Cycle in which the vote would have occurred.
At this time, the Board will operate as a neutral administrator of this Code of Conduct, without adjudicating whether violations have occurred. The Board will only move forward with a submission if there is: (1) indication of a specific violation of the Code of Conduct; and (2) sufficient evidence to prove a plausible violation. If a submission moves forward, it will follow the enforcement process below.
In future Seasons, the Board expects to reduce its role in this process.
There are a variety of possible enforcement actions, depending on the severity and type of the offense. The token holders will vote on: (1) standard violation suspensions; and
|Type of Violation
|First instance of inappropriate language or other behavior deemed unprofessional or unwelcome in the community, which is not already flagged by moderators on Discord or Discourse.
|In Season 1, the Team will process and issue reported warnings.
|A private, written warning from the Team, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may also be requested.
|A serious violation of community standards, including sustained inappropriate behavior.
|In Season 1, the Team will process and issue temporary suspensions.
|A temporary ban, lasting the length of 1 month, from Discord, Discourse, and other spaces. Guilty parties may not have public or private interaction with the community members involved, including unsolicited interaction with those enforcing the Collab.Land Code of Conduct. Violating these terms may lead to longer term suspension.
|Repeated violation of community standards, including sustained inappropriate behavior, or severe violation.
|Token holders must vote to suspend delegates that are reported to have committed severe violations, using the Code of Conduct Violation proposal type.
|If a vote for suspension is approved by token holders, the delegate will be suspended from Discord and Discourse and any sort of interaction within the community for a period of one year.
The Code of Conduct, the Rules of Engagement, and any other associated documents must only be updated between Seasons or following extraordinary circumstances that require immediate updates. In all cases, a change log will be published for delegates.