> For the complete documentation index, see [llms.txt](https://docs.raybot.app/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raybot.app/start/telegram/interface-navigation/signals/unusual-behavior.md). # Unusual Behavior Get alerted when a tracked wallet does something out of the ordinary — buying outside their usual trading hours or trading a position much larger than normal. {% hint style="warning" icon="light-emergency" %} **Important:** These settings apply to the **Solana** network only. {% endhint %} *** ### **⏰ Time Buy Alert** Get notified when a wallet buys at an unusual hour. RayBot builds a **2-week activity profile** for each wallet and flags purchases that happen outside their normal schedule. {% hint style="info" %} 💡 **Example:** A wallet that only trades during US hours suddenly buys at 5 AM — you get an alert. {% endhint %} **📲 Alert example:** ``` ⏰ Unusual Buy $Elongate 🔹 Wallet_Name 🔹 Wallet_Name swapped 3.42 SOL (+fee 0.03 SOL) for 33,897,173.21 ($308) Elongate @$0.00000908 at 22:00 UTC Statistics (290 buys, 2 weeks) 🔄 Pattern: Most purchases happen at 15:00, 13:00, 16:00 UTC ⚠️ Bought at 22:00 UTC. Previously, there were no purchases at this time. ▁▁▁▄▂▃▃▂▁▃▁▃▆▃█▆▆▁▃▁ ░ 0 6 12 18 💊 #Elongate | MC: $9.09K | Seen: 45s: GMGN | AXI 3JxGmwUE5ssNgQEstZB3cwnFTrtNSkg7BRQ7k21Vpump ``` *** ### **📊 Position Size Alert** Get notified when a wallet buys at an unusual size. RayBot tracks the typical position sizes for each wallet and alerts you when a buy falls outside their normal range. 💡 **Example:** A wallet that usually buys 0.5–1 SOL suddenly buys 25 SOL — you get an alert. **📲 Alert example:** ``` 📊 Unusual Position Size $MCV 🔹 Wallet_Name 🔹 Wallet_Name swapped 50 SOL for 1,206,839,412.46 ($4,462.54) MCV @$0.00000369 Statistics (105 buys, 2 weeks) 🔄 Pattern: Most purchases are standard (1–3), large (3–10) SOL ⚠️ This buy (mega: ≥ 50 SOL) is outside the usual range. Only 2 of 105 buys were this size. ▂ █ ░ .05 .2 .5 1 3 10 50 50+ 🔗 #MCV | MC: $3.69M | Seen: 4mo: GMGN | AXI 7dd7kiwbPmwh7KuJNKyc2mshpVP42XQ4GXYWbmBGK8DK ``` **📊 Position Size Bins** RayBot classifies all purchases using the following scale: | Bin | Label | SOL Range | | --- | -------- | --------- | | 0 | dust | < 0.05 | | 1 | micro | 0.05–0.2 | | 2 | small | 0.2–0.5 | | 3 | medium | 0.5–1 | | 4 | standard | 1–3 | | 5 | large | 3–10 | | 6 | whale | 10–50 | | 7 | mega | ≥ 50 | Each alert includes a compact bar chart showing the wallet's historical distribution across size categories. The height of each bar reflects how frequently the wallet bought at that size, so unusual buys stand out. ### **⚙️ How it works** Both alerts are powered by the same anomaly detection engine: RayBot collects wallet activity data over a **14-day window**. The wallet must complete **\~50 or more trades** during this period to build a reliable behavioral profile. Once the profile is established, every new trade is compared against the wallet's historical pattern. An alert is only triggered when the behavior **genuinely deviates** from the norm — if no anomaly is detected, no notification is sent. {% hint style="info" %} 💡 **Note:** If a wallet is active but all trades fall within its usual pattern — no alert will be sent. The system responds only to real behavioral shifts. {% endhint %} {% hint style="warning" icon="shield-exclamation" %} **Filter override:** When these features are enabled, all other filters are ignored. Alerts will be delivered regardless of your settings — even if you've set MC limits, disabled swaps, or have Multi Wallet active with other transaction types turned off. The notification will always reach the chat where these features are enabled. {% endhint %} --- # 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.raybot.app/start/telegram/interface-navigation/signals/unusual-behavior.md?ask=&goal= ``` `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.