Submit a governance proposal
- Confirm the proposal has one canonical discussion thread on the official Governance Forum.
- Confirm the proposal problem, change, and affected users or systems are stated clearly.
- Link the public references readers need, such as Trading Safeties and Guards, Margin Requirements, or Smart Contract Addresses and Core Contract Reference.
- If the proposal has reached formal-spec stage, link or open the corresponding entry in the public DIPs repository.
- Check Governance Mechanics and Voting Threshold Reference so proposer-threshold, action-count, and queue/execute constraints are in view before submission.
- Link any implementation branch, merge request, or execution notes that readers need to evaluate the proposal.
- Open the public proposal surface linked from the canonical forum thread or DIP, then submit the proposal action there.
- Save the canonical forum URL, DIP URL, proposal ID, and submission transaction hash or receipt after the action succeeds.
Verify before you treat it as canonical
- one forum thread is the primary public discussion surface
- any DIP or formal specification link matches the same proposal scope
- the public proposal surface exposes the same proposal text or scope as the forum and DIP materials
- the recorded proposal ID matches the intended governance item
- linked public references describe the current mechanism rather than historical behavior
- readers can tell whether the proposal is draft, active, queued, or already executed
Before you submit
- verify the proposal scope is stable enough that the public references will not be immediately contradicted
- verify the implementation links, if any, map to the same change described in the forum and DIP materials
- verify readers can tell what is already approved versus what is only proposed
Common mistakes
| Mistake | Safer action |
|---|---|
| treating a discussion thread as already-canonical proposal text | make the canonical proposal artifact explicit |
| linking stale or historical mechanism docs | re-check the current public references before publishing |
| assuming an unclear submission path | stop and use Community Resources or Support Channels instead of guessing |