> For the complete documentation index, see [llms.txt](https://injective-name-service.gitbook.io/injective-name-service/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://injective-name-service.gitbook.io/injective-name-service/roadmap.md).

# Roadmap

1. Refactoring and MVP Mainnet Release Preparation

* We recently redesigned the prototype app’s UI and created the injective.domains landing page. We would further optimize and improve the UI in order to provide an easy-to-use interface for the users.
*  Perform a thorough code review and refactor the existing contracts to ensure they are optimized, secure, and ready for mainnet release.
*  The refactor will enable the resolving and inverse resolving of multiple names to support a scalable name service.
*  Conduct rigorous testing and security audits to identify and fix any vulnerabilities or bugs.
*  Set up a testnet environment for the MVP and invite users and developers to provide feedback and report issues.

2. Staking to Named Validators and Address Bridging

* Integrate the staking to named validators feature to enable users to bypass the complicated validator address scheme. 
* Integrate the bridges such that they enable users to bridge their assets to named addresses, facilitating seamless interoperability.

3. Name Expiry, Marketplace and Auction Bidding System

* Design and implement a name expiration process to ensure that unused or abandoned names are released back into the pool. 
* Define the rules and criteria for name expiration, including the duration of inactivity required for a name to expire, making them available for registration by other users. 
* Develop a marketplace where users can buy, sell, and auction registered domains. 
* Implement an auction bidding system that allows users to bid on high-demand domain names. 
* Integrate a bidding mechanism that handles auction time extensions, bid increments, and winner determination.

4. SDK Development and Ecosystem Integration

* Develop an Ins-SDK (Injective Name Service Software Development Kit) that provides easy-to-use tools and libraries for integrating the Injective Name Service into other dApps and projects.
* Document the SDK and provide comprehensive examples and guides to facilitate integration by developers.
* Collaborate with ecosystem partners and actively encourage the integration of the Injective Name Service into their platforms and applications.

5. Open-Source Release, DAO Launch, and Token Distribution

* Open-source the entire project, including the contracts, SDK, and relevant documentation.
* Establish a decentralized autonomous organization (DAO) to govern the future development and decision-making of the name service.
* Conduct a token launch to distribute the protocol fees collected by the name service and provide governance power for the DAO.
* Launch a community-driven governance process to allow token holders to participate in voting and decision-making regarding protocol upgrades, fee distribution, and other DAO actions.

6. Beyond the Cosmos

* After the designated roadmap, we are eager to push the boundaries and let the whole Cosmos ecosystem use the Injective Name Service with IBC and CosmWasm.


---

# 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:

```
GET https://injective-name-service.gitbook.io/injective-name-service/roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.