> 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/xnet-token/governance/xnet-improvement-proposals.md). # XNET Improvement Proposals ### **Types of Proposals** Emissions and Tokenomics changes, technical upgrades, community projects or partnerships. **Who Can Submit?**\ All community stakeholder members are encouraged to participate in the advancement and growth of the XNET ecosystem via gevernance. **XIP Format**\ **Title**: Short, descriptive name.\ **Author(s)**: List the primary contributors.\ **Summary (100–200 words)**: High-level overview of the proposal.**Rationale**: Why this proposal is needed and the problem it solves.\ **Proposal Details**: Key steps, timelines, and resources.\ **Impact Assessment**: Potential effects on the network and community. ### Proposal Review Process **Preliminary Review:** WG council and community review the proposal for completeness and alignment with XNET’s goals and guidelines.\ **Feedback Period:** Allow a set period for the community to provide feedback or request clarification. The proposal may be updated based on community feedback. ### Voting Process **Step 1:** Voting Eligibility\ TBD with staking and governance tokens.\ **Step 2:** Voting Period\ Set a clear start and end date for the voting period (e.g., 7 days).\ Include details about how to cast a vote and the voting options available (Yes, No, Abstain).\ **Step 3:** Voting Outcome\ If the proposal passes a pre-determined quorum, it moves to the implementation phase.\ If the quorum is not met, the proposal is either rejected or sent back for further discussion and refinement. #### Implementation If the proposal is approved, outline the steps for implementation, including any budget allocations, development teams, timelines, or milestones.\ Regular updates should be posted to ensure transparency throughout the process. ### Monitoring and Reporting After implementation, the community should have access to regular progress reports.\ Establish a process for evaluating the success or failure of the proposal and its impact on the ecosystem. ### Appeal or Amendment Process If a proposal is rejected, outline how it can be appealed or amended for resubmission.\ Clear guidelines for how a failed or partially implemented XIP can be revisited.\ This outline ensures that the WG follows a transparent and structured process for submitting and approving community-driven proposals. You can further adapt this depending on the specific tools and governance structures XNET is using. ## XIPs

XIP	Title	Status
1	SLA (Cellular Radio Uptime) Based Token Bonus	Passed
2	Cellular Paid Data Buy and Burn Rate	Passed
3	Reduce $XNET total supply by 99%	Passed
4	End of Phase X (Registration & Staking)	Passed
5	Implementation of Price Oracle Algorithm	Passed
6	Wi-Fi Data Payout Modification	Passed
7	Chain Migration/XNET Foundation	Passed
8	Token Realignment on move to Solana	Passed
9	Restore 1:1 Converter	Passed
10	Unemitted Supply Burn Mechanism	Passed
11	Enhanced Tokenomics: Fibonacci‐Based Reduction, Proportional Usage Rewards, and Data Thresholds	Passed

--- # 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/xnet-token/governance/xnet-improvement-proposals.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.