Proposals are the foundation of governance within SHIB DAO, enabling community members to suggest changes, improvements, or new initiatives for the ecosystem. This guide covers the complete proposal lifecycle from creation to execution.

Proposal Types and Categories

SHIB DAO supports various proposal types to accommodate different governance needs:
System-wide changes and improvements
  • Protocol upgrades and modifications
  • Network parameter adjustments
  • Security implementations
  • Major ecosystem partnerships
  • Foundation-level decisions
Financial and resource allocation
  • Project funding requests
  • Development grants
  • Community initiatives
  • Marketing campaigns
  • Infrastructure investments
Community-driven initiatives
  • Community events and meetups
  • Educational programs
  • Social initiatives
  • Local community support
  • Cultural projects
Development and technical improvements
  • Smart contract upgrades
  • DApp improvements
  • Integration proposals
  • Technical standards
  • Development roadmap changes

Doggy DAO Proposals

Eligibility Requirements

To submit proposals in Doggy DAOs, you must meet specific criteria:
  • BONE DAO
  • TREAT DAO
  • SHIB DAO
  • LEASH DAO
Highest Requirements
  • Minimum BONE token holdings (varies by proposal type)
  • Karma Level 3+ for major proposals
  • Active participation history
  • Community reputation verification

Proposal Creation Process

1

Verify Eligibility

Check your token holdings and Karma level to ensure you meet the proposal requirements.
You can verify your eligibility in the SHIB DAO portal under “My Profile” section.
2

Choose Proposal Strategy

Select the appropriate voting strategy for your proposal:
  • Token-weighted voting: Standard governance decisions
  • Quadratic voting: Community-focused initiatives
  • Time-locked voting: Long-term strategic decisions
  • Custom strategies: Specialized governance mechanisms
The voting strategy affects how votes are calculated and can significantly impact proposal outcomes.
3

Draft Your Proposal

Create a comprehensive proposal document including:Required Sections:
  • Executive summary
  • Problem statement
  • Proposed solution
  • Implementation timeline
  • Resource requirements
  • Success metrics
  • Risk assessment
Optional Sections:
  • Technical specifications
  • Community impact analysis
  • Alternative solutions considered
  • Supporting documentation
4

Submit for Review

Submit your proposal through the official SHIB DAO portal for community review.
Ensure all required information is complete before submission. Incomplete proposals may be rejected.
5

Community Feedback

Your proposal enters a feedback period where community members can:
  • Ask questions and request clarifications
  • Suggest improvements
  • Express concerns
  • Provide support
Use community feedback to refine your proposal before the voting period begins.
6

Voting Period

Once approved for voting, your proposal enters the voting phase where eligible members cast their votes.
Voting periods typically last 3-7 days depending on the proposal type and complexity.

Community DAO Proposals

Creation Requirements

Community DAO proposals have more flexible requirements but still maintain governance standards:
  • SNS Domain: Required for proposal submission
  • DAO Membership: Must be a member of the specific Community DAO
  • Community Reputation: Good standing within the DAO community
  • Proposal Quality: Meets the DAO’s content and format standards

Proposal Structure

Community DAO proposals should include:
  • Title: Clear, descriptive proposal name
  • Description: Detailed explanation of the proposal
  • Objectives: Specific goals and outcomes
  • Timeline: Implementation schedule
  • Resources: Required funding or support
  • Background: Context and reasoning
  • Impact: Expected community benefits
  • Risks: Potential challenges and mitigation
  • Alternatives: Other approaches considered
  • References: Supporting documentation

Proposal Best Practices

Content Guidelines

Follow these best practices to increase your proposal’s chances of success:

Clear Communication

Use simple, jargon-free language that all community members can understand.

Concrete Benefits

Clearly articulate the specific benefits and value your proposal will deliver.

Realistic Timeline

Provide achievable timelines with clear milestones and deliverables.

Resource Planning

Include detailed cost estimates and resource requirements.

Technical Requirements

For proposals involving smart contract changes:
  • Code Review: Include comprehensive code documentation
  • Security Audit: Reference security considerations
  • Testing Plan: Outline testing procedures and validation
  • Rollback Strategy: Plan for potential issues or failures
For proposals involving ecosystem integrations:
  • API Documentation: Provide technical specifications
  • Compatibility: Address interoperability concerns
  • Performance Impact: Assess system performance implications
  • Maintenance Plan: Outline ongoing support requirements

Proposal Lifecycle

Timeline Overview

1

Drafting Phase (1-7 days)

Research, write, and refine your proposal with community input.
Use community feedback to improve your proposal before submission.
2

Review Phase (3-5 days)

Community review and feedback collection period.
This phase allows for proposal refinement based on community input.
3

Voting Phase (3-7 days)

Active voting period where eligible members cast their votes.
Voting is final - ensure your proposal is complete before entering this phase.
4

Execution Phase (Variable)

Implementation of approved proposals by relevant teams or contributors.
Track implementation progress through the SHIB DAO portal.

Voting Mechanisms

Different proposal types use various voting mechanisms:
  • Token-Weighted Voting
  • Quadratic Voting
  • Time-Locked Voting
Standard Governance
  • Voting power based on token holdings
  • Simple majority or supermajority requirements
  • Used for most ecosystem decisions
  • Transparent and predictable outcomes

Proposal Tracking and Management

Status Monitoring

Track your proposal’s progress through various statuses:
  • Draft: Initial creation and editing phase
  • Under Review: Community feedback period
  • Approved for Voting: Ready for community voting
  • Active Voting: Currently being voted on
  • Passed/Failed: Final voting outcome
  • In Implementation: Being executed by teams
  • Completed: Successfully implemented

Success Metrics

Measure proposal success through:
  • Number of voters
  • Voting participation rate
  • Community engagement levels
  • Feedback quality and quantity
  • Proposal approval rate
  • Implementation success rate
  • Community satisfaction scores
  • Long-term impact assessment

Troubleshooting Common Issues

Common reasons and solutions:
  • Incomplete information: Ensure all required sections are filled
  • Insufficient token holdings: Verify your eligibility requirements
  • Poor formatting: Follow the proposal template guidelines
  • Community concerns: Address feedback before resubmission
Strategies to increase engagement:
  • Community outreach: Promote your proposal through official channels
  • Clear communication: Simplify complex technical concepts
  • Compelling narrative: Focus on community benefits and value
  • Active engagement: Respond promptly to questions and concerns
Managing execution challenges:
  • Clear timelines: Set realistic implementation schedules
  • Resource planning: Ensure adequate funding and support
  • Team coordination: Work closely with implementation teams
  • Progress tracking: Regular updates and milestone monitoring

Next Steps

Remember that successful proposals require careful planning, community engagement, and clear communication. Take time to understand the ecosystem and build relationships before submitting major proposals.
I