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

# The Problem

For anyone trading memecoins or low-cap launches properly, the workflow usually looks like this:

1. Find a token on a terminal (AXIOM, GMGN, Photon, Padre, Basedbot).
2. Copy the contract address.
3. Paste it into a social search to see who's talking about it.
4. Check KOL and smart-money holdings.
5. Paste it into a yet another tool to read whatever lore or context exists.
6. Optionally, paste it into a fourth tool to check whether the contract is a honeypot.
7. Make a call.

By then,  the chart has already moved. The entry that mattered was at step one.

The information is already out there, but it’s scattered across terminals, wallet trackers, audits, feeds, and social posts. Every token forces the trader to rebuild the same picture from scratch, losing time in the gap between data and decision.

Most tools in this market help with one part of the research process. Thesium brings the whole picture into one panel.

## Why the assembly is hard

Each of the data classes above lives in a different shape, has a different update cadence, and has a different access model:

* **Holder analytics** require an on-chain indexer per chain, plus a maintained map of which addresses belong to whom.
* **KOL positions** require both an indexer and a named-wallet graph - neither of which is useful without the other.
* **Social signal** requires social-platform ingestion, deduplication, and filtering against the wallet graph to avoid drowning in mention-spam.
* **Lore and context** require human-readable interpretation of what a token actually is, which is not a database lookup.
* **Contract risk** requires running a buy/sell/transfer simulation against the actual on-chain bytecode plus a holder-distribution check.

Building any one of these is non-trivial. Building all five, keeping them current, and putting them side-by-side on the page where trading decisions are made - that's what Thesium does.

## Why the existing market fails the trader

The existing research market splits into two failure modes:

* **Single-purpose tools** (chart aggregators, holder dashboards, KOL trackers, honeypot scanners) solve one slice well and require the trader to combine them manually. Friction is high, time-to-decision is bad.
* **All-in-one terminals** (the trading platforms themselves) embed light versions of the same data - but the data is shallow, the layouts are designed for execution rather than research, and the trader is locked to one terminal per chain.

Thesium occupies the gap. It works with the terminal the trader already uses, adding a consistent research layer across every supported platform.


---

# 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://thesium.gitbook.io/thesium-docs/the-problem.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.