> For the complete documentation index, see [llms.txt](https://omen-protocol.gitbook.io/omen-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omen-protocol.gitbook.io/omen-protocol-docs/social-media/community-guidelines.md).

# Community Guidelines

Guidelines for maintaining a respectful, secure, and constructive OMEN Protocol community. Learn how to participate responsibly, protect your assets, and avoid scams and misleading information.

The OMEN Protocol community is built around crypto intelligence, onchain research, and ecosystem development. These guidelines help maintain a respectful, constructive, and secure environment for everyone.

### 1. Respect the Community

1. Treat other community members with respect.
2. Keep discussions constructive and relevant to OMEN Protocol, blockchain technology, and the broader ecosystem.
3. Do not engage in harassment, threats, hate speech, or personal attacks.
4. Avoid spam, repetitive messages, and unsolicited promotions.

### 2. Protect Yourself From Scams

1. Use only the official OMEN Protocol links listed in the Official Channels section.
2. Never share your wallet private keys, seed phrase, or recovery credentials.
3. Do not trust unsolicited messages offering guaranteed profits, exclusive rewards, or urgent investment opportunities.
4. Verify token contracts, transaction details, and website URLs before taking action.
5. Be cautious of accounts impersonating the OMEN Protocol team or community members.

### 3. Share Accurate Information

1. Distinguish confirmed announcements from speculation and personal opinions.
2. Do not spread fabricated announcements, misleading claims, or false information about OMEN Protocol.
3. Refer to official channels when verifying project updates.
4. Do not present potential features, future integrations, or planned developments as currently available unless officially confirmed.

### 4. Discuss Crypto Responsibly

1. Conduct your own research before making financial decisions.
2. Do not present personal trading opinions as guaranteed outcomes.
3. Understand the risks associated with digital assets, smart contracts, and onchain transactions.
4. Never pressure other community members into buying, selling, or transferring assets.

### 5. Keep Discussions Constructive

Members are encouraged to share feedback, report issues, ask questions, and contribute ideas that support the development of OMEN Protocol.

Constructive criticism is welcome when communicated respectfully and supported by relevant information.

### 6. Report Suspicious Activity

If you encounter suspicious links, impersonator accounts, misleading claims, or potential scams, report them through the available official community channels.

Avoid engaging with suspicious accounts or sharing potentially harmful links with other members.

### 7. Final Reminder

Participation in the OMEN Protocol community should be respectful, informed, and security-conscious.

These guidelines are intended to support a safer and more constructive community. Always verify official information and remain responsible for your own interactions and onchain transactions.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://omen-protocol.gitbook.io/omen-protocol-docs/social-media/community-guidelines.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
