A signal proposal is a non-binding governance proposal used to measure community sentiment before any on-chain action is taken. Think of it as a temperature check — it asks "does the community want this?" without committing resources or executing code. Signal proposals are the first step in most mature DAO governance processes, filtering ideas before they reach formal, binding votes.
How Signal Proposals Work
The Governance Pipeline
Discussion: Idea is shared in Discord, forums, or social channels
Signal proposal: Formal poll to gauge community sentiment (off-chain)
Feedback incorporation: Proposer refines the idea based on community response
Formal proposal: If sentiment is positive, a binding on-chain proposal is submitted
Execution: If the formal proposal passes, the action is executed on-chain
Testing controversial ideas before committing to a formal vote
Gathering feedback on parameter changes (fees, emissions, allocations)
Proposing new directions that need community alignment first
Complex proposals that benefit from iterative refinement
gauging interest before investing time in a detailed implementation plan
When You Can Skip Them
Routine operational decisions already covered by existing policies
Emergency actions that require immediate response
Minor parameter adjustments with clear community consensus
Decisions that have already been extensively discussed
Signal Proposal Formats
Temperature Check Poll
Title: [Signal] Should we increase protocol fees by 0.5%?
Options: Yes / No / Abstain
Duration: 3 days
Threshold: Simple majority
Copy link
Multiple Choice Alignment
Title: [Signal] Which L2 should we deploy to next?
Options: Arbitrum / Optimism / Base / zkSync / None
Duration: 5 days
Threshold: Plurality wins
Copy link
RFC (Request for Comments)
Title: [RFC] Draft proposal for new tokenomics model
Content: Full description + open comment period
Duration: 7 days
Outcome: Incorporate feedback into formal proposal
Copy link
Best Practices
For Proposers
Mark the proposal clearly as [Signal] to set expectations
Keep it focused — one question per signal proposal
Provide context but don't overwhelm — link to detailed discussions
Commit to acting on the result — don't signal if you'll ignore it
Set a reasonable voting window (3–7 days)
For Voters
Treat signal votes seriously — they shape what becomes binding
Use comments to explain your position, not just vote yes/no
Consider long-term implications, not just immediate reactions
Participate early — signal proposals with low turnout lack legitimacy
Why It Matters
Signal proposals are the DAO equivalent of "measure twice, cut once." For proposers, they're a low-risk way to validate ideas before investing in detailed implementation plans. For voters, they provide early input on decisions that will eventually become binding. For governance designers, they're a quality filter that prevents the voting system from being clogged with half-baked ideas. The DAOs with the best governance outcomes are the ones that treat signal proposals as a genuine feedback loop — not a rubber stamp on the way to a predetermined conclusion. In governance, legitimacy comes from process, and signal proposals are where that process begins.