> 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/editor.md).
# How it Works
Lens is designed to take raw on-chain activity and turn it into fast, readable, and actionable alerts — all inside Telegram.
***
### 1. Track Wallets
Users select and add wallets they want Lens to monitor.
This creates a personalised tracking layer, allowing each user to follow wallets that match their own strategy - whether that’s high-performing traders, early entrants, or specific behavioural patterns.
Lens is not a shared feed.\
It’s tailored to what *you* care about.
***
### 2. Lens Monitors Activity in Real-Time
Once a wallet is tracked, Lens continuously watches for on-chain activity.
When a tracked wallet enters a position, Lens detects the transaction as it happens - focusing on speed to ensure users are seeing activity as early as possible.
In fast-moving markets, timing is everything.\
Detection speed is a core priority.
***
### 3. Alerts Are Enriched With Context
Raw transactions don’t mean much on their own.
Each detected buy is processed and enriched with key data points to provide immediate context, including:
* market cap
* liquidity
* buy size
* wallet behaviour profile
* recent wallet performance
* signal strength and scoring
* reasoning behind the signal
This transforms a simple wallet buy into a structured, readable signal.
The goal is simple:\
**understand what’s happening instantly.**
***
### 4. Delivered Instantly in Telegram
Once processed, the alert is delivered directly inside Telegram.
Alerts are designed to be:
* fast to read
* visually clean
* easy to act on
No dashboards. No switching platforms.\
Everything happens where users already trade and communicate.
***
### 5. Performance Tracking & Milestones
Lens doesn’t stop at detection.
After an alert is triggered, Lens can continue tracking the token’s performance and surface key milestones such as:
* 2x
* 3x
* 5x
* 10x
This allows users to:
* review how alerts perform
* understand signal quality over time
* see real examples of outcomes
Not every alert is a buy.\
But every alert becomes data.
---
# 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/editor.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.