> For the complete documentation index, see [llms.txt](https://docs.walletx.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.walletx.bot/faq/frequently-asked-questions/why-does-walletx-recommend-skipping-wallets-with-too-many-transactions.md).

# Why does WalletX recommend skipping wallets with too many transactions?

Currently, our analyzer processes up to 2,000 transactions per wallet. When a wallet has more transactions than this limit:

* Analysis results may be incomplete
* PnL calculations might not reflect full trading history
* Performance metrics could be inconsistent

📊 For the most accurate analysis, we recommend:

* Analyzing wallets with fewer than 2,000 transactions
* Checking newer or more focused trading wallets
* Using our verified alpha wallet drops (we pre-screen these)

We're constantly working on increasing this limit to handle larger transaction volumes. For now, this helps ensure you get the most accurate and reliable analysis possible! 

📝Note: Quality of trades matters more than quantity.


---

# 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://docs.walletx.bot/faq/frequently-asked-questions/why-does-walletx-recommend-skipping-wallets-with-too-many-transactions.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.