to cessproject
- 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.
Hello zeng-hero, thank you for your interest in contributing to the CESS ecosystem!
We truly appreciate your initiative in engaging with the project and your willingness to participate in community-driven ecosystem development. CESS has always valued open collaboration under DAO principles, and community-led proposals are an important part of our long-term roadmap.
Here is how you can submit your collaboration proposal:
1. Recommended Repository
Depending on the type of proposal, please submit to one of the following repositories:
-
CIPS (CESS Improvement Proposals) Repository For formal, structured, or technical proposals. Repository: GitHub - CESSProject/CIPs: The CESS Improvement Proposal repository
-
Main cess Repository (Issues) For general collaboration ideas, community initiatives, and ecosystem proposals.
If you are unsure which category your idea fits, feel free to open an Issue first and we will help direct it to the correct location.
2. Recommended Proposal Structure
To help maintain clarity and consistency, we suggest using the following structure:
- Background & Motivation
- Problem / Opportunity Identified
- Proposed Collaboration or Initiative
- Expected Value to the CESS Ecosystem
- Resources You Can Provide
- Milestones / Deliverables
- Contact Information (optional)
You may refer to the CIP template here: 👉 GitHub - CESSProject/CIPs: The CESS Improvement Proposal repository
This structure ensures that maintainers and the community can transparently evaluate and provide feedback.
3. Review Workflow
Once your proposal is submitted:
- CESS maintainers and relevant working groups will review the content
- Discussion and feedback will occur directly under the Issue or PR thread
- Feedback will typically be provided within 2–3 working days
- Additional information or refinements may be requested
- Once consensus is reached, the proposal moves into planning and execution stages
Please include your contact information so that our team can reach out directly after receiving your proposal
Thank you once again for your proactive engagement and for recognizing CESS’s long-term potential. We welcome community contributors, and we look forward to reviewing your proposal.
If you need any help preparing your document, feel free to reach out — we’re happy to support.