> For the complete documentation index, see [llms.txt](https://docs.outlight.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.outlight.ai/solution/product-overview/tutorials-and-use-cases/interesting-use-cases/how-outlight-sniped-usddawg-before-the-pump.md).

# How Outlight sniped $dawg before the pump

(Contract Address of the described coin) CA: 3rdCUNNgj52frYdp3cJLwQ6xzJibjyjsPCtNMRUDpump

Here's a real example of how the Outlight bot turned simple Twitter "follow" into a 388% gain in just 2 hours.

<figure><img src="/files/sslAdLTTGSTt46En06qW" alt="" width="510"><figcaption></figcaption></figure>

### Catching the early signal

At 13:49, Outlight detected that [@TeTheGamer](https://x.com/TeTheGamer) (known crypto influencer) **followed** the [$dawg](https://x.com/search?q=%24dawg\&src=cashtag_click) project on Twitter. No tweets yet, no hype, just a quiet follow. This was likely when he started accumulating his bag.

### Automated entry

Without any human intervention, the bot instantly bought [$dawg](https://x.com/search?q=%24dawg\&src=cashtag_click) for 0.05 SOL at $0.000122. The bot was already in the position before anyone else even noticed the move.

<figure><img src="/files/aCoGE0MNGdCHcZnULhbD" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="/files/xcTsBrx9eJSZb2aS7HbT" alt="" width="563"><figcaption></figcaption></figure>

### The Tweet drops

32 minutes later (14:21), [@TeTheGamer](https://x.com/TeTheGamer) finally tweeted: "Higher for the dawg". No contract address (CA) was shared, so the market took some time to react while people scrambled to find the token. But our bot had already locked in a prime entry.

### The Pump

Within 2 hours, [$dawg](https://x.com/search?q=%24dawg\&src=cashtag_click) skyrocketed to $0.0005963 - massive 388% gain from our entry price! The bot sold at the top, securing profits while others were still trying to buy in.&#x20;

On-chain proof: [https://solscan.io/tx/WQkAAu1sa9zRctFL5nC3cAM9wS1h3CQ8T85TaA3aVbVvRqco5sfVxyjuRMKEVwon2iPt7fgFkFKaKTbD49LkGrd](https://t.co/tuKQykhnsU)

<figure><img src="/files/gTzKMdcUwyHTMvg11caY" alt=""><figcaption></figcaption></figure>

### That's the power of being first

* 388% profit in 2 hours&#x20;
* Entry before any public signals
* Completely automated trading&#x20;

In crypto, being seconds ahead can mean the difference between life-changing gains and missing out completely.


---

# 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.outlight.ai/solution/product-overview/tutorials-and-use-cases/interesting-use-cases/how-outlight-sniped-usddawg-before-the-pump.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.
