# Team

Our team consists of hardcore and experienced crypto degens, born in the 80s and shaped by the culture of that time. We grew up playing classic arcade games like *Contra*, *Double Dragon*, and other gems on the good old NES. These games taught us resilience, endurance, and how to face challenges head-on — qualities that perfectly reflect the essence of our project.

We are the ones who grew up idolizing tough action heroes from the golden era of cinema, where protagonists fought against all odds with an unbreakable will to win. Movies like *Die Hard*, *Commando*, and the iconic roles of Arnold Schwarzenegger, Stallone, and Van Damme still shape our worldview. These heroes embody strength, bravery, and unwavering confidence — qualities we have infused into the development of BeerBear.

Our team is a tight-knit group of millennials who don’t see crypto as just a way to make money, but a real battleground. We have zero tolerance for scammers, fraudsters, and fake projects. BeerBear reflects our desire to fight back against anyone who exploits the crypto industry for deception and profit. Like our bear, we love good beer, epic battles, and are ready to defend the community from any threat.

Each member of the team is a true connoisseur of memes and crypto, with extensive experience in blockchain, development, and marketing. We are not just token creators — we live and breathe the spirit of decentralized finance, ready to lead BeerBear to victory in the memecoin world.


---

# 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.beerbear.io/team.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.
