> 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/copy-trading-academy/copytrading-dos-and-donts/10.-trade-size-impact-analysis.md).

# 10. Trade Size Impact Analysis

Make sure the trader doesn't have a trade size more than 5 SOL per trade.  The larger the buy amount the bigger the dip when they sell.

## 💰 Optimal Trade Sizing:

* Focus on wallets trading under 5 SOL per position
* Larger trades cause deeper price impacts
* Smaller trades allow easier entry/exit
* Better prices mean higher actual profits

## ⚠️ Risk Factors:

* Big trades create major price swings
* Large sells often trigger panic selling
* Higher slippage on larger positions
* Harder to copy exact entry/exit points

## 📊 Impact Assessment:

* Monitor price impact of sells
* Check typical trade size patterns
* Verify consistent position sizing
* Avoid wallets with oversized trades


---

# 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/copy-trading-academy/copytrading-dos-and-donts/10.-trade-size-impact-analysis.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.