> For the complete documentation index, see [llms.txt](https://docs.nezohub.com/nezohub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nezohub.com/nezohub/ecosystem/nezo-hub-roadmap.md).

# Roadmap

## Nezo Hub Ecosystem

## Q3 2023

* [x] Market research and analysis 
* [x] Business model research and design
* [x] Product design and market fit analysis

## Q4 2023

* [x] [Vision and mission](/nezohub/overview/nezohub-vision-and-mission.md)
* [x] Technological study
* [x] Bootstrap initial funding
* [x] Core Team assembly

## Q1 2024

* [x] Website UI/UX design and development
* [x] [Nezo Sydra's](/nezohub/overview/what-is-nezo-sydra.md) architectural concept design
* [x] Research into [LayerZero](https://docs.layerzero.network/v2/home/v2-overview) interoperability protocol
* [x] Research into [Polygon zkEVM](https://docs.polygon.technology/zkEVM/architecture/protocol/)
* [x] Research into [EspressoSys](https://docs.espressosys.com/sequencer/espresso-architecture/system-overview)

## Q2 2024

* [x] Ecosystem DevOps implementation
* [x] Established the legal framework
* [x] [Nezo Token](/nezohub/technical-documentation/nezo-token.md) economic design
* [x] Setting the fundraising strategy
* [x] Initial marketing strategy setup
* [x] Business model updates

## Q3 2024

* [x] Research study into EVM architecture for [Nezo Core (L1)](/nezohub/overview/what-is-nezohub.md)
* [x] Research study on [EIP-4337](https://eips.ethereum.org/EIPS/eip-4337) for [NezoPortal](/nezohub/user-guide/nezo-portal-mobile-app.md) mobile app
* [x] [Nezo Portal](/nezohub/user-guide/nezo-portal-mobile-app.md) web & mobile app UI/UX design
* [x] Exploring new infrastructure partnerships
* [x] Develop the brand identity and messaging

## Q4 2024

* [x] [NezoHub](/nezohub/overview/what-is-nezohub.md) Litepaper v1.0 release
* [x] KOL outreach for the upcoming marketing campaigns
* [x] NezoPortal dApp development kickoff
* [ ] Validator Tools & SDKs
* [ ] Liquidity Locker
* [ ] Vesting Creator
* [x] Strategic expansion, marketing, and partnerships

## Q1 2025

* [ ] Nezo Portal dApp launch
* [ ] Deployment of [$NEZO Token](/nezohub/technical-documentation/nezo-token.md) (ERC20/BEP20)
* [ ] Launch Nezo Hub Liquid Staking Phase I
* [ ] Sydra Sequencer 
* [ ] Sydra Testnet & Contracts Audit
* [ ] Testnet Validators marketing campaign
* [ ] Node Licenses Campaign
* [ ] Strategic expansion, marketing, and partnerships

## Q2 2025

* [ ] Sydra Mainnet Live
* [ ] Sydra Bridge Mainnet Live
* [ ] SDKs & Dev Tools
* [ ] Staking Creator (SaaS)
* [ ] Token Creator
* [ ] MemeCoin Creator
* [ ] Strategic Ecosystem Expansion

## Q3 2025

* [ ] Team Expansion
* [ ] P2P Exchange
* [ ] Limit Orders DEX
* [ ] DeFi Contracts Audits
* [ ] Dev Tooling Dashboard
* [ ] AI-DeFi Tools
* [ ] Nezo Hub Hackathon

## Q4 2025

* [ ] Core Testnet
* [ ] AI Contracts Testnet
* [ ] Nezo Index App Dashboard
* [ ] Nezo Index Testnet
* [ ] SDKs & Dev Tools
* [ ] Strategic Expansion

## Q1 2026

* [ ] Strategic Ecosystem Expansion
* [ ] More TBA


---

# 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://docs.nezohub.com/nezohub/ecosystem/nezo-hub-roadmap.md?ask=<question>&goal=<endgoal>
```

`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.