> For the complete documentation index, see [llms.txt](https://docs.stargaze.zone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stargaze.zone/help/community-and-support.md).

# Community & Support

Connect with Stargaze and get help when you need it.

## Official Channels

### Discord

The main community hub for Stargaze.

**Join:** [discord.gg/stargaze](https://discord.gg/stargaze)

**Channels:**

* `#general` - Community chat
* `#support` - Get help with issues
* `#announcements` - Official updates
* `#creator-chat` - For NFT creators

### Twitter

Follow for updates and announcements.

**Follow:** [@StargazeZone](https://twitter.com/StargazeZone)

### Telegram

Alternative chat community.

**Join:** [t.me/stargazezone](https://t.me/stargazezone)

## Getting Support

### Self-Service

Many questions are answered in:

* This documentation
* [FAQ](/help/faq.md)
* [Troubleshooting](/help/troubleshooting.md)

### Community Help & Official Support

For general questions:

1. Search Discord to see if it's been answered
2. Create a ticket in `#support` with clear details (wallet address and transaction)
3. Stargaze team will reply

## Reporting Issues

### Bugs

Found a bug? Report it:

1. Go to Discord `#support`
2. Describe what happened
3. Include screenshots if possible
4. Share transaction hashes if relevant

### Scams

Report suspicious activity:

* Fake collections
* Phishing attempts
* Impersonation

Use Discord `#support` .

### Stolen Art

If you see your art being used without permission:

1. Use the "Report" button on the collection
2. Open a ticket on Discord
3. We investigate all reports

## Safety Tips

### Stargaze will never:

* Ask for your seed phrase
* DM you first about "support"
* Ask you to connect to unknown sites
* Request payment for support

### Protect yourself:

* Verify all links before clicking
* Don't share your seed phrase with anyone
* Be skeptical of DMs offering help
* Check official announcements for real info

## Contributing

### Feedback

Have suggestions? We listen:

* Discord `#suggestions` channel
* Twitter replies
* Direct feedback to team members

### Community Calls

Occasional community calls happen on:

* Twitter Spaces
* Discord voice channels

Follow announcements for schedules.

### Creator Support

For creators launching collections:

* Discord `#creator-chat`
* Studio documentation
* One-on-one support for featured launches

## Links

| Resource      | URL                                                  |
| ------------- | ---------------------------------------------------- |
| Website       | [stargaze.zone](https://stargaze.zone)               |
| Studio        | [studio.stargaze.zone](https://studio.stargaze.zone) |
| Discord       | [discord.gg/stargaze](https://discord.gg/stargaze)   |
| Twitter       | [@StargazeZone](https://twitter.com/StargazeZone)    |
| Documentation | [docs.stargaze.zone](https://docs.stargaze.zone)     |

## Stay Updated

* Follow Twitter for announcements
* Enable Discord notifications for `#announcements`
* Check the blog for detailed updates
* Join community calls for deep dives


---

# 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://docs.stargaze.zone/help/community-and-support.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.