# Roadmap

HeraFinance is being built in three deliberate phases — each one building on the last to take the protocol from foundational infrastructure to a fully realized, cross-chain leveraged yield ecosystem.

***

## Phase 1 — Foundation

The Foundation phase is focused on building the core protocol, establishing community presence, and preparing for a secure and credible launch.

* Platform development and smart contract architecture
* Seed sales round for early strategic supporters
* Community building across Twitter/X and Telegram
* Security audit planning and vendor selection
* Brand identity, website launch, and public communications

***

## Phase 2 — Growth

The Growth phase brings the protocol live on BNB Chain and activates the full suite of yield farming products.

* Mainnet launch on BNB Chain
* Farming pools go live with initial whitelisted liquidity pairs
* Lending markets activation and lender onboarding
* Strategic partnerships with key BSC DEXes and liquidity hubs
* Yield optimization features including auto-compounding upgrades and position dashboards

***

## Phase 3 — Expansion

The Expansion phase scales HeraFinance beyond BNB Chain and puts governance into the hands of the community.

* Cross-chain deployment to additional EVM-compatible networks
* Advanced leverage strategies for experienced farmers
* Community governance rollout with token-based voting
* Ecosystem grants program to fund community-built integrations and tools
* Mobile-optimized experience for on-the-go position management

***

Each phase is designed with clear milestones and will be tracked transparently through public updates across HeraFinance community channels.


---

# Agent Instructions: 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://heraxfinance.gitbook.io/hera-docs/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.
