> For the complete documentation index, see [llms.txt](https://lens-project.gitbook.io/lens-project-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lens-project.gitbook.io/lens-project-docs/documentation/get-started/interactive-blocks.md).

# Roadmap

<figure><img src="/files/6nx65r48tsY8pfC3KpO4" alt=""><figcaption></figcaption></figure>

### Phase 1 - Core Product (Live)

The foundation of Lens is already in place.

This includes:

* smart wallet tracking
* real-time alert detection
* enriched alert data (MC, liquidity, buy size, etc.)
* wallet behaviour profiling
* signal scoring and reasoning
* clean Telegram-native delivery
* performance milestone tracking (2x, 3x, etc.)

This phase proves the core idea:\
**fast, readable, and actionable on-chain alerts.**

***

### Phase 2 - Product Expansion

The next phase focuses on improving quality, control, and execution.

Planned improvements include:

* more advanced filtering and customisation
* improved signal scoring and accuracy
* better wallet behaviour analysis
* enhanced performance tracking and statistics
* expanded token-gated features
* smoother user experience and interface upgrades

#### Sniper Bot Integration

A key addition in this phase is the introduction of a **Telegram-native sniper system**.

This will allow users to:

* act instantly on Lens alerts
* execute buys directly from Telegram
* reduce friction between detection and execution
* move faster in early-stage opportunities

The goal is to bridge the gap between **seeing the signal and acting on it** - all within the same environment.

***

### Phase 3 - Ecosystem Growth

Long-term, Lens expands into a broader intelligence and execution system.

This includes:

* deeper analytics and insight tools
* wider tracking capabilities
* stronger infrastructure for scale
* continued feature rollout based on real usage
* tighter integration between alerts, tracking, and execution

#### Expanded Execution Layer

Building on the sniper system, Lens aims to evolve into a more complete trading layer:

* smarter execution tools
* improved speed and reliability
* tighter integration with alert logic
* more control for users

The vision is to combine **intelligence + execution** into one seamless system.


---

# 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://lens-project.gitbook.io/lens-project-docs/documentation/get-started/interactive-blocks.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.