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

# Product Roadmap

Our roadmap is a guide to what we will be working on and researching in each quarter.

> :bulb: **Note:** Please note that these are not exact delivery or deployment dates.

## Our Future Plans 🗺️

**Q3 '24 (July - September)**

* **Launch Marketing Campaign**: Creating awareness about Lends Protocol.
* **THORNames Functionality**: Simplifying and humanizing wallet addresses across multiple blockchains.

**Q4 '24 (October - December)**

* **Markets Overview**: Offering a quick glance at all available offerings.
* **Dashboard Feature**: Enabling users to check all their positions in one place
* **Perform Smart Contract Audit and Security Review**: Ensuring the safety of our users.
* **P2P Lending Introduction:** Expanding services to include peer-to-peer lending.

**Post-Q4 '24**

* **Establish Strategic Partnerships**: Broadening our reach with leading lending institutions.
* **Future Tooling**: Continuously improving and adding new features..


---

# 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.lends.so/tokenomics/product-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.
