• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
NFTXNFTXby0x951160D731822d141509c7C899Dc5A9C9237d4cf0x9511…d4cf

Adopt Code of Conduct

Voting ended about 5 years agoSucceeded

Authors

  • Finesseboi

Glossary

  • DAO
  • NFTX

Summary

Adopt a Code of Conduct for contributors of the NFTX DAO to follow.

Rationale

It is my belief that having different predefined standards will allow the DAO to grow more efficiently. Making sure that respect remains mutual throughout the growth of the NFTX community will contribute to avoiding internal conflicts as much as possible. I believe respect is a framework upon which a DAO should be built. If this can improve workflow, the earlier it is implemented the better it is for the DAO.

Effect

Improves brand value as people know what to expect when interacting with the DAO. Members are not afraid to become contributors and behavior is optimized as less time is lost to arguments.

Censorship is always a risk. I doubt this will occur but should always remain a concern moving forward.

Specifications

  • Demonstrating empathy and kindness toward other individuals
  • Being respectful of differing opinions and perspectives.
  • Giving and accepting constructive feedback kindly.
  • Accountability for ones mistakes
  • Focusing on what is best for the DAO and not on individuals.
  • Act towards having an engaged, inclusive and diverse community of users/contributors/builders
  • Publishing private information pertaining to anything without explicit permission. This includes physical and digital addresses.
  • Follow discord rules
  • APPLIES EVERYWHERE when using an NFTX hosted medium of communication (discourse, discord, twitter, etc.)

Contact

  • https://forum.nftx.org/t/adopt-code-of-conduct/33
  • https://discord.com/invite/5ygF8rxdYR

Poll

  • Yes : Implement Code of Conduct
  • No : Disregard Code of Conduct

Off-Chain Vote

Yes : Implement Code of Conduct
39.01K 100%
No : Disregard Code of Conduct
0 0%
Download mobile app to vote

Timeline

Jan 09, 2021Proposal created
Jan 09, 2021Proposal vote started
Jan 11, 2021Proposal vote ended
Oct 26, 2023Proposal updated