> 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/7.-hold-times-and-trade-size-analysis.md).

# 7. Hold Times & Trade Size Analysis

## ⏱️ Hold Time:

* Avoid extremely short holds (under 5 mins)
* Fast flipping often reduces profit potential
* Look for strategic holding periods
* Slower-paced trades show better consistency

## 💰 Trade Size:

* Watch for oversized trades vs liquidity
* Large buys can spike token prices
* Poor entry/exit prices affect copying success
* Prefer balanced trade size relative to mcap

## ✅Optimal Trading Patterns:

* Medium hold times (15+ minutes)
* Reasonable position sizes
* Good liquidity matches
* Sustainable trading strategy

📝**Pro Tip:** WalletX analyzes hold times and trade sizes to help you identify the most copyable wallets! 

🧠 **Remember:** Premium members get access to pre-vetted wallets with optimal trading patterns! 🚀


---

# 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/7.-hold-times-and-trade-size-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.