> For the complete documentation index, see [llms.txt](https://xnet-mobile.gitbook.io/xnet-mobile-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xnet-mobile.gitbook.io/xnet-mobile-docs/xnet-foundation/foundation/working-group-council.md).
# Working Group Council
### Mission
The XNET Foundation Working Group exists to steward the long-term sustainability and growth of the XNET ecosystem. Acting on behalf of the XNET community, the group formalizes and advocates for collective goals, ensuring that all governance decisions reflect the community’s shared vision of decentralization, transparency, and innovation.
***
### Objectives
The Working Group's mandate includes, but is not limited to:
• Promoting decentralized participation and community-led governance\
• Evaluating and implementing strategies to enhance network security and prevent potential vulnerabilities\
• Collaborating with the community to shape balanced and sustainable tokenomics supporting long-term ecosystem health\
• Facilitating communication between the XNET community, Foundation stakeholders, and external partners\
• Conducting research and analysis to identify areas for improvement and innovation across the XNET ecosystem
***
### Scope of Work
During this charter iteration, the Working Group Council shall receive community feedback and propose XNET Improvement Proposals (XIPs) for community review and formal Council vote in the following areas:
• Token emission structures\
• Inflation and deflation mechanisms\
• Staking system designs\
• Governance mechanisms
Community input is collected during scheduled weekly voice calls in Discord.\
Summaries of these sessions are published in the GitBook to maintain transparency and continuity between community discussion and governance outcomes.
***
### Group Composition and Terms
**Composition**\
The Working Group Council is composed of volunteer members representing different major stakeholder segments of the XNET ecosystem:
* XNET Foundation
* XNET Mobile
* MSP/ISP Partners
* Token Holders
* Independent Deployers
This composition balances oversight, operational expertise, and community representation.
**Terms and Rotation**\
\- Initial term: six months, beginning with a two-month trial to confirm participation and commitment\
\- Members not meeting expectations or attendance requirements may be replaced\
\- At term end, members seeking renewal must receive majority approval from the current Council\
\- Vacant or new seats may be filled through open nominations or Foundation appointment
***
### Roles and Responsibilities
**Chair** – Directs group activities, sets agenda and moderates weekly meetings.\
**Scribe** – Summarizes weekly Discord calls, assists with XIP documentation and DAO Realm management.\
**Advisors** – Experienced deployers or large stakeholders offering insight, feedback and assistance with DAO operations.
***
### Operational Details
**Time Commitment**\
Members are expected to contribute 5-10 hours per month, including weekly meetings and asynchronous tasks.\
A minimum 2/4 weekly meeting attendance rate per month is required for continued participation.
**Reporting and Documentation**\
• Maintain a weekly agenda for discussion topics\
• Publish summaries highlighting key discussion points, council takeaways, and next steps\
• Record any actionable items or XIPs progressing to formal review
### Governance Process
1. **Proposal Intake** – Community suggestions are discussed during weekly calls or submitted in Discord. The Council reviews and shapes these into formal XNET Improvement Proposals (XIPs).
2. **Community Feedback** – Before formal voting, proposals undergo multiple revisions and sentiment checks via Discord reactions or discussion threads to ensure alignment between community input and Council interpretation.
3. **Council Vote** – Each XIP is executed upon **3 of 5 Council member signatures** (3/5 super-majority). Signatures occur on-chain via [DAO Realm](https://v2.realms.today/dao/GzymLNkdkUruf7FAzYtALjCwJJQiv2gv9ZCC8eUX1EwF/proposals). This ensures no single entity or subgroup can unilaterally pass or block proposals.
4. **Execution and Publication** – Once approved, the decision and rationale are published in GitBook under “XIPs,” with a cross-reference to related summaries. Major proposals may be escalated to community-wide vote if required by scope or impact.
***
#### Transparency and Accountability
• Council member names, categories, and term dates are listed publicly in the GitBook\
• Voting outcomes are on-chain for all XNET Improvement Proposals (XIP) \
• Summary posts serve as a transparent bridge between Discord discussions and formal governance actions via council votes
***
#### Disclaimer
The XNET Foundation Working Group operates independently of XNET Mobile Inc.\
Members serve in an advisory and governance capacity for the XNET ecosystem only and are not responsible for corporate or operational actions taken by XNET Mobile Inc.
***
*Last updated: October 2025*
***
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://xnet-mobile.gitbook.io/xnet-mobile-docs/xnet-foundation/foundation/working-group-council.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.