Start a governance forum post
- Confirm the topic belongs in governance rather than in trading support or API troubleshooting.
- Search the official Governance Forum and the public DIPs repository for an existing thread or draft before opening a new one.
- Write a short summary that states the problem, proposed change, expected outcome, and affected users or systems.
- Link the exact public references readers need, such as Trading Safeties and Guards, Margin Requirements, or Smart Contract Addresses and Core Contract Reference.
- State whether the thread is discussion only, formal DIP drafting, or commentary on an already active proposal or election.
- Ask for feedback on risk, governance process, and execution path in one place rather than splitting the discussion across multiple threads.
Publish one canonical artifact chain
Keep the public governance chain explicit from the first post:- forum thread URL for discussion
- DIP URL when the thread graduates into a formal design artifact
- proposal ID or election identifier only when a public voting surface actually exists
- implementation merge request or execution notes only when they match the same scope
Include these fields
- proposal title
- problem statement
- proposed change
- affected products, contracts, or governance surfaces
- linked forum or DIP references
Before you publish
- make sure one thread will remain the canonical discussion surface
- remove implementation details that belong in linked references rather than in the summary itself
- state clearly whether you want feedback, formalization, execution planning, or review of an already active proposal
Common mistakes
| Mistake | Safer action |
|---|---|
| opening a governance thread for a pure support issue | route the issue to Support Channels instead |
| posting without linking the governing public references | include the exact routes that define the affected mechanism |
| splitting one idea across multiple threads | keep one canonical discussion URL and cross-link instead of duplicating |