-
Notifications
You must be signed in to change notification settings - Fork 90
Description
- Background
We are a community research group that has conducted comprehensive technical and investment analysis on the CESS Network. We highly recognize CESS’s technological direction, architecture, and long-term ecosystem value. We also believe CESS is currently undervalued and has strong potential for broader ecosystem growth.
We would like to participate more deeply in the community-driven development of CESS and contribute to its decentralized data infrastructure vision.
- Purpose of This Issue
Before submitting a formal collaboration proposal, we would like to confirm the official guidelines and preferred format for submitting community-driven ecosystem proposals to CESS.
Our goal is to ensure that our upcoming proposal is aligned with CESS’s governance expectations, technical roadmap, and DAO principles.
-
Questions for Guidance
We would appreciate clarification on the following: -
Which repository is recommended for submitting collaboration proposals?
-
Is there a preferred proposal structure/template?
-
Should community proposals be categorized as CIP (CESS Improvement Proposal), or as a general collaboration proposal?
-
What is the expected review workflow?
- Who will review?
- How long is the typical discussion period?
- How does the approval/feedback process work?
-
Is there a requirement to tag specific maintainers or committees for visibility?
-
Our Intention
We aim to submit a well-structured, high-quality collaboration proposal that could contribute positively to the CESS ecosystem, especially in areas such as:
- Community expansion
- Ecosystem growth & partnerships
- Developer onboarding
- Research & analytics
- Web3 education / content / tooling
(We can adjust based on official guidance)
- Closing
We appreciate the CESS team’s openness to community contribution and DAO-style collaboration.
We look forward to your guidance so we can prepare our formal proposal accordingly.
Thank you.