> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/reference-and-support/39-support-and-safety.md).

# 39. Get help and protect your wallet

Use official channels and prepare a useful support report without exposing credentials.

## Official destinations

| Destination        | Link                                                          |
| ------------------ | ------------------------------------------------------------- |
| Platform           | [spawnmeme.com](https://spawnmeme.com)                        |
| Help               | [SPAWN Help](https://spawnmeme.com/help)                      |
| Telegram community | [SPAWN community](https://t.me/spawnmemetg)                   |
| Telegram bot       | [@spawnmeme\_bot](https://t.me/spawnmeme_bot)                 |
| Trending channel   | [SPAWN Trending](https://t.me/spawntrending)                  |
| X                  | [@SpawnMemeX](https://x.com/SpawnMemeX)                       |
| All links          | [Linktree](https://linktr.ee/spawnmeme)                       |
| News               | [News & Updates](https://spawnmeme.com/updates)               |
| GitHub             | [spawnmeme/spawnmeme](https://github.com/spawnmeme/spawnmeme) |
| Documentation      | [SPAWN Docs](https://spawnmeme.gitbook.io/spawnmeme-docs)     |
| Medium             | [@spawnmeme](https://medium.com/@spawnmeme)                   |

Use the site's current official-token link or context-appropriate `/ca` response, then compare the full mint. Tickers, display names and profile images can be copied. In a connected project group, `/ca` refers to that group's token, not necessarily the platform token.

## Prepare a support report

Copy this and fill in only the relevant fields:

```
Feature and exact page URL:
What I expected:
What happened instead:
Exact error text:
Date/time and timezone:
Device and operating system:
Browser/wallet name and version:
Public wallet address (if needed):
Token mint / collection / project URL:
Order ID (if any):
Transaction signature (if any):
Was the transaction confirmed, failed, or still unknown?
Steps already tried:
Screenshot with private information removed:
```

A wallet address and transaction signature are public chain identifiers, but they can reveal activity associated with you. Share only what is needed through the appropriate official support context. Hide account emails, unrelated balances and private chat information in screenshots.

## Never share

* Seed phrase, recovery phrase or private key.
* Wallet backup file or password.
* Email/login verification code or session token.
* A signed transaction or approval you do not understand just because someone calls it a support step.

SPAWN support does not need your seed phrase to inspect a public transaction. Someone who contacts you privately after a public help request is not automatically an official representative. Navigate to the official channels yourself and verify whom you are speaking with.

## Before a paid or permanent action

Check the site domain, full mint/recipient and wallet account. Read the quote and wallet instructions. Burning, minting, sending assets and publishing permanent NFT files have consequences that a support conversation cannot simply undo. Use the appropriate guide's recovery action if submission already happened.

## What a good resolution looks like

You can match the support explanation to a visible status, confirmed chain receipt or verified account/project change. No support promise should require handing over wallet credentials or paying an unexplained “unlock” transfer.

## Content reports and private security reports

Use [Report](/spawnmeme-docs/feature-guides/reference-and-support/46-report.md) on a token, NFT collection or project for scams, impersonation, stolen content and other moderation concerns. SPAWN can hide hosted listings and bot visibility, but cannot erase Solana records.

Use [Responsible disclosure](/spawnmeme-docs/feature-guides/reference-and-support/49-responsible-disclosure.md) for security problems. Follow its testing rules and send reproduction details privately. **SPAWN does not run a paid bug bounty.**

***

[Guide home](/spawnmeme-docs/feature-guides.md) · [Troubleshooting](/spawnmeme-docs/feature-guides/reference-and-support/38-troubleshooting.md) · [Get help](/spawnmeme-docs/feature-guides/reference-and-support/39-support-and-safety.md)


---

# 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://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/reference-and-support/39-support-and-safety.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.