> For the complete documentation index, see [llms.txt](https://thirdfi.gitbook.io/thirdfi.org-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thirdfi.gitbook.io/thirdfi.org-1/product/roadmap.md).
# Roadmap
ThirdFi's Roadmap
### Last year + 2024
* Integrated with 10+ L1 / L2 blockchain network & multiple DeFi Protocols
* 170,000 signup users
* Processed more than $46m transaction
* Joined Chainlink #BUIDL program
### Second Quarter 2024
* Developing ThirdFi ID
* Data Collection for AI agents
* Integration with DeFi protocols and blockchain
* Smart Contract deployement
### Third Quarter 2024 \[ 📍 We are HERE ]
* Data-to-Earn Program
* Smart contract and token audit
* Extending the ecosystem of ThirdFi protocol
* Nodes design
* Empower Proof of Trading
### Forth Quarter 2024
* AI Marketplace for builders
* GPUs and TPUS developing for AI training
* Developing Modular AI layer
* Extending use case for Onchain & DeFi users
### First Quarter 2025
* Integration Zero-Knowledge Proof
* AI agents activation
* Constructing scalable core blockchain layer
* Launching AI builders program
---
# 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://thirdfi.gitbook.io/thirdfi.org-1/product/roadmap.md?ask=&goal=
```
`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.