This is a forum for project self-reflection identification of weaknesses and formation of solutions to drive positive change for the protocol. Concerns raised may focus on:
* Protocol design or technicals
* Areas requiring further research
* Economics or market infrastructure
* Marketing or community development
This initiative is a valuable culture to identify and manage the risks, challenges and uncertainties faced by the Decred project. Changing the world is hard, doing it well even more so.
[The Decred Falcon escaping chaos due to regular and constructive self-reflection \(circa. 2142\)](https://preview.redd.it/yye2zqwe6wm51.png?width=1394&format=png&auto=webp&s=5e9d317e28b2ea6b87f3657edff37b7ff0f3987d)
# Ground Rules
1. Building Decred is Hard. Please do not forget we are at the cutting edge of technology and social change and it takes immense time, skill, money and effort to deliver this project. Please comment accordingly.
2. Solutions or Considered Options should be presented alongside commentary of areas for improvement. Complaints are easy, solutions are hard. If you are not sure of a solution, that is ok, bring up the discussion and make an effort to seek an answer. Unproductive complaints without solutions are discouraged.
3. Be Respectful of readers, comments and critiques. Decred is an open source protocol where no one person is in charge. The primary objective of this initiative is to identify concerns and address them constructively. All holders of DCR are responsible for project outcomes and we get out what we put in.
4. Review past editions and don't hammer on repeated issues. Many issues take time to solve and concerns raised repeatedly have likely been heard. It is ok to return if progress does not appear to have be made
5. Utilise Up/Downvotes to Identify priority concerns. The biggest issues should rise to the top to ensure maximum attention.
# Suggested Format
Challenge or Concern: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\...
Getting excited here! #decred version 1.6 getting closer and closer to a release. Yesterday 12 issues; this morning 10; right now 5 issues. 4 of these issues already have code and are under review be...