Any USUAL holder can propose a UIP (Usual Improvement Proposal). This article walks you through the full process, from idea to on-chain execution.
What kinds of changes need a UIP
You need a UIP for any change that affects the protocol's state, contracts, or economics:
New products or collateral types
Parameter changes (fees, rates, lock weights, emission splits)
Treasury allocation (how the DAO deploys its assets)
Partnerships and integrations with external protocols
Emergency actions
Governance process changes
You do not need a UIP for simple front-end fixes, marketing decisions, or service-level operational changes — those are handled directly by Usual Labs.
Minimum requirements
To propose a UIP on-chain, you typically need:
A minimum amount of USUAL or USUALx voting power (threshold set by the governance contract)
A well-written forum post that survives community discussion
A draft of the UIP with a clear specification of what changes
If you do not meet the voting power threshold, you can collaborate with a delegate or larger holder who does.
The proposal lifecycle
```
Step 1 — Forum post
└─ Post your idea on gov.usual.money for discussion
Step 2 — Community feedback
└─ 1-2 weeks of discussion, iteration, and refinement
Step 3 — UIP draft
└─ Format your proposal as a formal UIP with spec and rationale
Step 4 — Temperature check
└─ Informal Snapshot vote (3-5 days)
Step 5 — On-chain vote
└─ Binding on-chain vote (5-7 days)
Step 6 — Execution
└─ If passed, the change is implemented
```
Step-by-step
1. Write a forum post
Go to gov.usual.money and create a new topic in the Proposals category. Your post should include:
Title — clear and specific
Summary — one paragraph on what the proposal does
Motivation — why this change matters and who benefits
Specification — the exact change (parameters, contracts, amounts)
Rationale — why this approach is the right one
Risks — what could go wrong
Alternatives — other approaches you considered
Keep the post focused. Long, unstructured posts are hard to discuss.
2. Engage with feedback
For 1–2 weeks, participate actively in the discussion. Respond to questions. Revise your proposal based on constructive feedback. The goal is not to win every argument — it is to produce a proposal that the community understands and supports.
3. Format as a UIP
Once the forum discussion converges, draft the formal UIP. A UIP has a standard structure:
UIP number (assigned by a governance facilitator)
Title, author, date
Abstract
Specification (including exact on-chain parameters)
Motivation
Impact analysis
Security considerations
Implementation plan
Look at past UIPs for examples of the format.
4. Submit to temperature check
Create a Snapshot poll to get an informal signal. This is not binding, but it tells you whether the on-chain vote is likely to pass. If the temperature check fails, you have the option to revise and retry before committing to the on-chain vote.
5. Submit the on-chain vote
If the temperature check passes, submit the proposal on-chain. This is the binding vote. It lasts 5–7 days and requires the quorum and approval thresholds described in How voting works.
6. Implementation
If the vote passes, the DAO executes the proposal. This may involve:
A multisig transaction
A governance contract call
Usual Labs updating the front-end or back-end as needed
Monitoring and reporting post-implementation
Most UIPs are fully implemented within days. Complex changes (new products, new collateral) may take weeks.
Tips for a successful UIP
Start with the forum — do not skip to Snapshot or on-chain. The forum is where proposals get shaped.
Listen to feedback — the community often raises points the author did not consider. Engage seriously.
Be specific — vague proposals fail. Spell out every parameter.
Include risks — hiding risks makes the proposal look dishonest. Listing them transparently builds trust.
Plan implementation — think about how the change will be executed, who implements it, and how it is monitored.
What happens if your UIP fails
UIPs can fail at any stage: forum, temperature check, or on-chain vote. Failure is not final. You can:
Revise and resubmit
Split the proposal into smaller pieces that are easier to approve
Use the feedback to refine your next proposal
Note: Proposing a UIP is a meaningful act. Take time to draft, discuss, and refine. Rushing a proposal rarely leads to a good outcome.
Technical note (for DeFi users): On-chain UIP submission requires interacting with the governance contract. The exact interface (Snapshot, Tally, or a custom contract) is listed on gov.usual.money. Proposal thresholds and quorum requirements are defined in the governance contract and can be queried on-chain. Past UIPs are available in the governance forum archive and the docs.
Related articles