> For the complete documentation index, see [llms.txt](https://prosoftchain.gitbook.io/document/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosoftchain.gitbook.io/document/roadmap.md).
# ROADMAP
## OUR 2023 ROADMAP in details
There are several significant developments that we’ll be integrating into the Prosoft Chain over the next months, beginning with the much-anticipated launch of the Prosoft chain mainnet.
Basic Roadmap on Q1 - Q2
Major Roadmap on Q3
Basic Roadmap :
Q1 - Website Live, Utility Creation, Community, Contract Creation, Launch, Staking Platform, Marketing, Audit, KYC, Bridge, DexSwap, Partnership, BscScan Update, Launhpad, Adding features.
While we, unfortunately, had to delay our mainnet launch from the initially planned date — a decision we did not take lightly — this has allowed us to ensure the network will be robust and feature-rich when it does launch. The first 30 network validators will also go live before the end of the year, helping to ensure the network is secure and stable.
We will also be taking various steps to maximise the utility and value of the native PROSOFT token. As well as continuing to support BEP-20 token migration, we’ll be announcing new exchange listings for the native PROSOFT token, as well as staking and delegation options and a multi-send DApp. Alongside extended functionality for our native token, we’ll be offering native NFT account-based support as we look to establish Prosoft as the leading chain for NFTs in the Cosmos ecosystem.
Further, we will be implementing numerous features to help make the Prosoft chain a flexible and user-friendly platform for developers, including Turing-complete smart contract support and the bespoke Prosoft “Blast” developer SDK. We’ll also be launching a grants programme to support further development within the Prosoft ecosystem.
As we’ve discussed elsewhere, we’re committed to putting interoperability at the core of our network. That’s why we’ll also be supporting transfers between Binance and the Prosoft Chain using Gravity Bridge and integrating the Cosmos IBC bridge to Osmosis DEX, allowing for easy interaction between tokens within the Cosmos ecosystem.
Q3 2023
As you can see, our short-term goals for the Prosoft roadmap are far-reaching. Foremost among them will be the beta launch of our distributed compute platform Pro Compute in Q3. We aim to provide a fully decentralised, scalable, and sustainable source of cloud computing for Web3, and this will be a significant step toward making that a reality.
We’ll also be implementing a range of other feature enhancements to support the broadest possible range of use-cases for the Prosoft chain. For example, various native PROSOFT vesting tools will be offered, alongside a muti-signature wallet that will make it easier to manage your tokens. We’ll also extend and deepen our NFT offerings, with native NFT collections supported from Q3.
Finally, we’ll further our commitment to decentralisation within the crypto space by offering interchain IBC account support and working toward fully decentralising our validator network. The Prosoft Launchpad will also go live in Q3, helping developers build the broadest and most profound range of DApps possible on the Prosoft blockchain.
---
# 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://prosoftchain.gitbook.io/document/roadmap.md?ask=
```
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.