> For the complete documentation index, see [llms.txt](https://equinoxai.gitbook.io/equinox-ai-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://equinoxai.gitbook.io/equinox-ai-whitepaper/overview/problem-statement.md).

# Problem Statement

<figure><img src="/files/iGEOQzvU6yM2Fh7TPDmW" alt=""><figcaption></figcaption></figure>

**On-chain** activity lacks context. Wallets move capital, deploy contracts, and receive tokens, but they do so without identifiable patterns unless those patterns are manually traced. Without linking behavioural metadata to those actions, meaningful insight is limited.

**Social activity,** while public, is disconnected from blockchain behaviour. Influencers make calls. Projects coordinate announcements. Groups operate in cycles. Yet there is no systematic way to align those signals with corresponding on-chain movements.

**Analysts, traders, and builders** are left to rely on fragmented tools—portfolio trackers, Telegram group monitoring, manual searches, and block explorers—to stitch together narratives retroactively.

Coordinated behaviour often goes undetected. Mixer usage, bridge routes, anonymised wallets, and social coordination all contribute to an environment where pattern visibility is low and data is siloed.

This gap between on-chain movement and off-chain influence is one of the most under-analysed areas in crypto. **Equinox AI** is designed to close that gap.


---

# 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://equinoxai.gitbook.io/equinox-ai-whitepaper/overview/problem-statement.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.