> For the complete documentation index, see [llms.txt](https://rage-guy.gitbook.io/usdrage-lore-book/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rage-guy.gitbook.io/usdrage-lore-book/culture/memers-vs-coiners.md).

# MEMERS VS COINERS

<h2 align="center"><strong>Memers vs Coiners → The Core of $RAGE</strong></h2>

<p align="center">In the world of crypto, two tribes emerged.</p>

<p align="center"><strong>The Coiners</strong> and <strong>The Memers.</strong></p>

<figure><img src="/files/8HBFdtkn9cjOvNoCL9TZ" alt=""><figcaption></figcaption></figure>

<p align="center">Coiners stare at charts. They chase green candles and panic at red ones. They refresh their portfolios every five minutes, hoping the next pump will save them. To them, a project’s worth is measured only by the price and not the people, not the purpose. Their loyalty shifts with every wick.</p>

<p align="center">Then came <strong>The Memers.</strong></p>

<p align="center">They don’t follow charts, they <strong>make culture.</strong></p>

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

<p align="center">Memers use creativity, humor, and energy to spread the word, to bring people together, to turn a ticker into a movement. They don’t ask “When moon?”, they ask, “What’s the next meme?”</p>

<p align="center">Because memes are more than jokes. They’re <strong>weapons of connection</strong>, the purest form of community energy. Every viral post, every creative rage comic, every inside joke strengthens the cause.</p>

<p align="center">That’s where <strong>$RAGE</strong> comes in.</p>

<figure><img src="/files/419VC61bIvUKMTIALEFH" alt=""><figcaption></figcaption></figure>

<p align="center">$RAGE was never about chasing quick profits or pleasing the coiners that controls the markets. It was built to <strong>fight back,</strong> to bring back what coins were supposed to be:</p>

<p align="center">A symbol of community.</p>

<p align="center">A reason to laugh, to build, to create together.</p>

<p align="center">Coiners trade charts.</p>

<p align="center">Memers trade <strong>energy.</strong></p>

<p align="center">One fades when the market dumps.</p>

<p align="center">The other grows louder when times get tough.</p>

<p align="center">$RAGE belongs to the memers, the ones who see beyond the candles, who turn frustration into fuel, and who understand that the true value of a coin is the <strong>community behind it.</strong></p>

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

<p align="center">So, meme harder.</p>

<p align="center">Fight the coiners.</p>

<p align="center">And remember</p>

<p align="center"><strong>in $RAGE we trust.</strong></p>

<p align="center">FUUUUUUUUUUUUUUUUUUUUUUUUUU</p>

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


---

# 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://rage-guy.gitbook.io/usdrage-lore-book/culture/memers-vs-coiners.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.
