> 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/license.md).

# License and terms

Bloxchain has two legal layers: the open-source Bloxchain Protocol, which is licensed code, and the hosted Bloxchain Platform, which is a service with its own terms. This page says which applies where.

## Bloxchain Protocol (open source)

The Protocol smart contracts, the TypeScript SDK (`@bloxchain/sdk`) and the upstream documentation in [Bloxchain-Protocol](https://github.com/PracticalParticle/Bloxchain-Protocol/tree/99beac2d6e6d7567c23b25cecaf6f4053f31c987) are released under the **Mozilla Public License 2.0 (MPL-2.0)** unless a subdirectory states otherwise.

* [LICENSE](https://github.com/PracticalParticle/Bloxchain-Protocol/blob/99beac2d6e6d7567c23b25cecaf6f4053f31c987/LICENSE) at the pinned commit
* Example contracts under `contracts/examples/` may carry per-folder licenses; check each folder.

Deploying, forking or embedding Protocol code is governed by MPL-2.0. Using the Platform does not change that license, and the Platform does not relicense the Protocol.

## Bloxchain Platform (hosted service)

The Platform at bloxchain.app is a separate hosted product operated by Particle Crypto Security Ltd. It is not covered by the Protocol's MPL-2.0 license. Using it means accepting the product terms shown in the app:

| Document         | Link                                                                     |
| ---------------- | ------------------------------------------------------------------------ |
| Terms of service | [bloxchain.app/legal/terms](https://bloxchain.app/legal/terms)           |
| Privacy policy   | [bloxchain.app/legal/privacy](https://bloxchain.app/legal/privacy)       |
| Disclaimer       | [bloxchain.app/legal/disclaimer](https://bloxchain.app/legal/disclaimer) |

The alpha banner in the app links to the disclaimer. Read it before moving value through any account.

### Current alpha scope

| Topic                 | Today                                                                                                                                                                                                                         |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Maturity**          | Alpha · Local-first. Official deployments are live on the 15 supported networks, in the Platform and in the Protocol.                                                                                                         |
| **Free**              | Open to everyone, no sign-in. Inventory stored on this device; Bloxchain keeps no copy.                                                                                                                                       |
| **Sign-in (Account)** | Optional identity: profile, privacy export and organization invites. Hosted services, including alerts, come with an organization on Pro. Sign in if you have early access; otherwise join the waitlist from the same dialog. |
| **Organizations**     | Paid **Pro**, **Team** and **Enterprise** plans billed to an organization. Pricing is shown at checkout or on request; Enterprise is contact us. An organization that has not completed checkout is **Checkout required**.    |
| **Custody**           | Non-custodial by architecture. You hold the keys; Bloxchain never holds a key.                                                                                                                                                |

For what each level includes see [Free, sign-in and organizations](/introduction/free-sign-in-organizations.md). For the maturity and risk statement see [Security disclaimers](/security/audit-status/security-disclaimers.md).

### What the Platform is not

* A custodian of private keys or funds.
* A replacement for the on-chain policy. The chain enforces; the Platform displays and orchestrates.
* Legal, tax or investment advice.

## This documentation site

The pages in [bloxchain-docs](https://github.com/PracticalParticle/bloxchain-docs) describe how to use the Platform and the Protocol. The Protocol section is vendored from the Protocol repository at a [pinned commit](/resources/releases.md#protocol-documentation-pin) and keeps its MPL-2.0 license. Documentation prose is informational and is not a substitute for the product terms or the Protocol license.

## Related

* [Audit status](/security/audit-status.md)
* [Limits and defaults](/resources/limits-and-defaults.md)
* [FAQ](/resources/faq.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/resources/license.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.
