# Roadmap

The roadmap provides an overview of the features the Chainlens team are currently working on and plan to work on in the coming months.

The list isn't exhaustive, nor final, but it provides perspective on where the product is headed.

If you'd like to contribute to or discuss any of the items, feel free to [jump on our Discord](https://discord.gg/pNP5cnpjFZ) to connect with the team.

### Q1 2024

* [x] NFT collection previews (small and large) on NFT home page
* [x] Placeholder images for NFTs without valid metadata
* [x] Proactive ingestion of all NFT metadata and images
* [ ] All new Chainlens UI 🚀🚀🚀
* [ ] Performance improvements on instances with very large datasets
* [ ] Network/protocol About page with community focussed links
* [ ] Fully Sourcify integration for partial and full matches against the entire contract history on network.

### 2024 Q2

* [ ] Dynamic sitemap generation to enhance SEO ranking
* [ ] Filtering in NFT views for specific NFT attributes
* [ ] Advanced search page
* [ ] Burned token stats
* [ ] New dashboard metrics

### Q3 2024

* [ ] ZK-EVM specific data views&#x20;
* [ ] Creator-specific views (view NFT assets associated with specific creator accounts)

## Completed milestones

### Q2 2023

* [x] Internal transaction support
* [x] Implementation of detailed NFT views in Chainlens including support for metadata-defined images and attributes
* [x] Node sync status

### Q3 2023

* [x] Public Sourciy Support
* [x] Substrate Frontier Pallet Support
* [x] Optimism Support

### Q4 2023

* [x] Polygon CDK support
* [x] Polygon ZK-EVM support
* [x] Accounts view
* [x] NFT, token and account-based navigation


---

# 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://docs.chainlens.com/help-and-faqs/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.
