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

# Support and community

Where to get help with the Bloxchain Platform, the Bloxchain Protocol and this documentation, and what to include so the first reply can solve your problem.

## Before you write

* Inside an account, open the **Help** page (More menu → **Help**). It shows wallet, network, your roles, open items and the setup checklist, and answers the most common questions in place.
* Check [Troubleshooting](/resources/troubleshooting.md) and the [FAQ](/resources/faq.md).

## Contact

| Need                                             | Where                                                                                             |
| ------------------------------------------------ | ------------------------------------------------------------------------------------------------- |
| Product support for the Platform                 | **<support@particlecs.com>**                                                                      |
| Bugs or feature requests for the Protocol or SDK | [Protocol issues](https://github.com/PracticalParticle/Bloxchain-Protocol/issues)                 |
| Design questions, integrations, show and tell    | [Protocol discussions](https://github.com/PracticalParticle/Bloxchain-Protocol/discussions)       |
| Mistakes or gaps in this documentation           | [Documentation issues](https://github.com/PracticalParticle/bloxchain-docs/issues)                |
| A security vulnerability                         | Do not open a public issue. Follow [Report vulnerabilities](/security/report-vulnerabilities.md). |

## What to include in a report

The more of this you include, the faster the answer:

1. **Network**: the chain name and ID shown in the top bar (for example Sepolia, 11155111).
2. **Account address**: the smart account's contract address, or its open link (`https://bloxchain.app/workspace/<chainId>/<address>`).
3. **Request id** or transaction hash, if the problem is about a specific request in Approvals or History.
4. **Screenshot of the Help page** for that account. It captures wallet, network, roles and setup state in one image.
5. **What you did and what you expected**, including the exact button or message text.
6. Whether you were **signed in** or using the Free path, and the residency badge (**This device**, **Cloud**, **Cloud off**).

{% hint style="warning" %}
Never share private keys, seed phrases or the contents of a signed file (`.bloxmeta.json`) in a support request. Anyone holding a signed file can submit it until it expires.
{% endhint %}

## Open source and community

| Project                                       | Link                                                                                                       |
| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| Bloxchain Protocol (contracts, SDK, examples) | [github.com/PracticalParticle/Bloxchain-Protocol](https://github.com/PracticalParticle/Bloxchain-Protocol) |
| This documentation                            | [github.com/PracticalParticle/bloxchain-docs](https://github.com/PracticalParticle/bloxchain-docs)         |
| Particle CS                                   | [particlecs.com](https://particlecs.com/)                                                                  |

Pull requests to the documentation are welcome. Protocol pages under [Protocol](/protocol-reference/protocol.md) are vendored from the Protocol repository, so propose changes to them upstream.

## Related

* [Limits and defaults](/resources/limits-and-defaults.md)
* [Security disclaimers](/security/audit-status/security-disclaimers.md)
* [Platform guide](/platform-guide/platform.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bloxchain.app/resources/support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.