# Avoiding Scams

Scams are unfortunately common in the crypto space, but you can protect yourself. Here are some tips on how to stay safe:

***

**1️⃣ Never Share Your Private Key or Seed Phrase**

99.9% of scams can be avoided by NEVER sharing your **Private Key** or **Seed Phrase** with anyone. Scammers will try to get these from you to steal your funds.

**Remember:**

* **Your Private Key and Seed Phrase are for your eyes only.**
* **No one should ever ask you for them.**

***

**2️⃣ Watch Out for Impersonators**

Scammers often impersonate official accounts. They may pose as **Sorosbot Moderators**, **Support Accounts**, or even **Official Channels**. To stay safe:

* Ensure you're interacting with **Sorosbot** through official channels.
* You can always click the official link: <https://t.me/sorosbot\\_bot> to ensure you're talking to the right bot.

Be cautious of fake bots asking you to deposit **SOL** or asking for sensitive information—they are NOT official!

***

**3️⃣ Scammers May DM You First**

**Important:**

* Official **Sorosbot Admins** will **never DM you first**.
* They will **never ask** you for your **Private Key** or **Seed Phrase**.

If you receive unsolicited messages, always double-check the source and do not share any sensitive information.

***

By following these simple steps, you can avoid most scams and keep your funds secure. Stay vigilant and trade safely! 🚀


---

# 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://soros-bot.gitbook.io/sorosbot-docs/safety-and-security/publish-your-docs.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.
