# RuSpamMonitor

<mark style="color:yellow;">🔗 Current Available Chains: ETH</mark>

With the recent increase in *'***bundled**' launches, traders are now '**spamming**' tokens to be the first buyers in block 1. We unwrap failed transactions and display details for tokens they are targeting.

<mark style="color:orange;">**Re-Fresh Tech:**</mark> on the subject of spamming, like our [<mark style="color:orange;">SniperHunter</mark>](/rupro/rupro-channels/rusniperhunter.md) and [<mark style="color:orange;">**RuFresh**</mark>](/rupro/rupro-channels/rufresh.md) channels, we have also added re-fresh tech, to this channel, as more spam wallets target a token and also failed transaction numbers increase, the post will automatically refresh - neatly avoiding an unpleasantry like 12 message notifications and prints for the same token.&#x20;

### Data Breakdown 👇

<figure><img src="/files/fAePIbLdKXTL5wFtyoYf" alt=""><figcaption><p>Spammers; lnner circles, team or kols? How else would they know a token is about to potentially be bundled?</p></figcaption></figure>

#### Have a read of our dedicated RuDMs page for more info on our personal command intelligent bot 👇

{% content-ref url="/pages/BJb2nC9NT5udCni9oAxD" %}
[RuDMs](/rupro/rudms.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.rubots.xyz/rupro/rupro-channels/ruspammonitor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.