> 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/security/report-vulnerabilities.md).

# Report a vulnerability

How to tell us privately about a security problem in the Bloxchain Protocol or the Bloxchain Platform.

{% hint style="danger" %}
Do not open public GitHub issues or public posts for security vulnerabilities. Email us first.
{% endhint %}

## Contact

* **Email:** <security@particlecs.com>
* **Subject:** `[SECURITY] Bloxchain vulnerability report`
* **Website:** [particlecs.com/contact](https://particlecs.com/contact), mentioning Bloxchain

## What to include

1. A description of the vulnerability and which surface it affects (Protocol contracts, SDK, bloxchain.app).
2. Steps to reproduce, with network, addresses and transaction hashes where relevant (Sepolia is fine).
3. The impact you believe it has.
4. A suggested fix, if you have one.
5. How we can reach you for follow-up.

## Supported versions

| Version                                                                                                       | Supported                               |
| ------------------------------------------------------------------------------------------------------------- | --------------------------------------- |
| Current tagged release on [GitHub releases](https://github.com/PracticalParticle/Bloxchain-Protocol/releases) | Yes                                     |
| Older tags                                                                                                    | Best effort                             |
| bloxchain.app                                                                                                 | The live Platform (Alpha · Local-first) |

Full policy at the pinned commit: [SECURITY.md](https://github.com/PracticalParticle/Bloxchain-Protocol/blob/99beac2d6e6d7567c23b25cecaf6f4053f31c987/SECURITY.md).

## Bug bounty

**In scope:** smart contracts and Protocol behaviour in published releases, and Platform issues that lead to unauthorised on-chain outcomes or key exposure.

**Out of scope:** Platform issues with no security impact, social engineering, third-party wallets and RPC providers, and issues in your own custom extensions.

We support good-faith research consistent with our disclosure policy. Eligible reports may receive acknowledgement and bounty consideration under terms communicated privately.

## Related

* [Security](/security/security.md)
* [Audit status](/security/audit-status.md)
* [Security model](/security/security-model.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://docs.bloxchain.app/security/report-vulnerabilities.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.