DAO Governance Hub

A governance server for a DAO: a proposal pipeline, working groups, treasury transparency and a decision archive.

5 categories
23 channels
8 roles
Medium

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

START HERE

governance-rules
How proposals work, and what this server is not for.
no-price-talk
Why price and financial advice are out of scope here, and where they belong instead.
general
Everything that is not a proposal.
join-a-group
Self-Roles panel.
announcements
Votes opening, results, anything time-critical.

PROPOSALS

ideas
Anything, however rough.
temperature-check
Is the DAO broadly willing? An hour, before anyone drafts.
draft-proposals
What changes, what it costs, who executes, and how we know it worked.
active-votes
Only what is live right now.
proposal-archive
Every past proposal and its outcome.

WORKING GROUPS

group-one
Rename to the group. State its remit in the topic.
group-two
Rename to the second group.
group-three
Rename to the third group.
group-four
Rename to the fourth group.
group-reports
One written update per group per month. Non-negotiable.

TREASURY

treasury-address
The address. Verify it yourself rather than taking our word.
spending-log
One line per outflow, with the proposal it came from.
budget-requests
Ask for funding. Costs and deliverables in the post.

CONTRIBUTORS

contributor-intros
What you can do and how much time you have.
bounties
Open work, with the reward stated.
contributions-log
What was delivered, by whom.
Governance Call
Working Group Room

Roles

StewardAdministrator
ModeratorModerator
Group LeadModerator
Contributor
Member
Governance Ping
Muted

Overview

A DAO's server is its parliament, and most of them are a single chat where a proposal is announced the day voting opens. This layout is the pipeline instead. Proposals move through four channels in order: #ideas takes anything, #temperature-check is where an idea is tested informally before anyone drafts, #draft-proposals is for the written version with the required shape stated in the topic — what changes, what it costs, who executes it, and how we will know it worked — and #active-votes carries only what is live. #proposal-archive is read-only and holds every past proposal with its outcome, which is what stops the same argument being had twice a year. Working Groups is where a DAO actually gets things done: four group channels plus #group-reports, a monthly written update from each, because groups that report survive and groups that do not quietly stop. Treasury is read-only and deliberately plain: #treasury-address so anyone can verify on-chain, #spending-log with one line per outflow, and #budget-requests. Contributors covers the people doing the work: #contributor-intros, #bounties and #contributions-log. The one hard rule, stated in #governance-rules, is that this server discusses governance and does not give financial advice or price commentary, and #no-price-talk explains why that boundary exists.

When to use it

Governance in one chat channel means proposals appear fully formed with no chance to shape them, past decisions are unfindable, and working groups drift because nobody reports. This layout runs proposals through temperature check and draft before a vote, keeps a read-only archive of outcomes, requires monthly written updates from each working group, and makes the treasury verifiable rather than described.

What makes it different

Proposals move through ideas, temperature check, draft and vote, in that order.
A read-only archive of past outcomes, which stops the same argument recurring yearly.
Working groups file a monthly written report, because groups that report are the ones that survive.
Governance only: a stated rule that this is not the place for price talk or financial advice.

Recommended Vetox setup

Suggestions
Run Suggestions on #ideas so a temperature check produces a real count rather than the impression of one.
Self-Roles
Post a Self-Roles panel in #join-a-group so contributors pick working groups and pings stay inside them.
Reminders
Set monthly Reminders in #group-reports, since an unreported working group is how a DAO loses track of its own work.
Auto-Mod
Run Auto-Mod across the public channels, because a governance server is a standing target for impersonation and scam links.

Questions

Why separate temperature check from the draft stage?

Because writing a full proposal is expensive and most ideas should die before that. A temperature check costs an hour and tells an author whether the DAO is broadly willing, which saves them drafting something that was never going to pass and saves everyone else reading it. It also means the proposals that do reach draft arrive already shaped by the objections raised early.

Is keeping price talk out realistic?

It is if the rule is written and there is somewhere else to go. The reason to enforce it is not squeamishness: a governance channel where price is discussed starts evaluating proposals by their likely effect on price rather than on the organisation, and the people with the largest positions become the loudest voices. Most DAOs that keep governance usable have this boundary and state it plainly.

How many working groups should there be?

Fewer than you think, and each with a named lead who files the monthly report. Four is a sensible starting point. Groups multiply easily because creating one feels like progress, but a DAO with nine groups and three active ones looks abandoned. Merge or close a group that misses two reports rather than leaving its channel as evidence of a thing that stopped.

Common mistakes

Publishing a proposal the day voting opens, which turns governance into ratification.
Describing the treasury instead of publishing the address anyone can verify for themselves.
Letting price conversation into a governance server, after which proposals are argued on price.

Consider instead

Token Holder Community The server is for holders generally rather than for the people writing and voting on proposals.
Open-Source Web3 Project The organisation is a codebase with contributors rather than a treasury with voters.

Do you have any doubts?

Our team is there for you

0.0k

Servers

Commands

Users

Languages