> 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/introduction/why-bloxchain.md).

# Why Bloxchain?

Bloxchain exists because **critical on-chain operations should not depend on a single hot key**. Treasury moves, role changes, and contract calls need **governed, auditable policy** enforced by smart contracts — not informal process or off-chain promises.

## What you get

| Need                      | Bloxchain answer                                                                                       |
| ------------------------- | ------------------------------------------------------------------------------------------------------ |
| Separation of duties      | Multi-phase operations with distinct request, approve, sign, and execute roles                         |
| Policy you can verify     | RBAC, schemas, allowlists, and timelocks **on-chain**                                                  |
| Operator-friendly surface | [bloxchain.app](/platform-bloxchain.app/start.md) for day-to-day treasury and policy work              |
| Developer integration     | [@bloxchain/sdk](https://www.npmjs.com/package/@bloxchain/sdk) aligned with protocol releases          |
| Open, auditable core      | [MPL-2.0 Protocol](https://github.com/PracticalParticle/Bloxchain-Protocol) with published audit scope |

## Problems it addresses

| Failure mode           | How Bloxchain helps                                                                                |
| ---------------------- | -------------------------------------------------------------------------------------------------- |
| Single-key risk        | Owner, Broadcaster, Recovery, and custom RBAC roles split capabilities                             |
| Off-chain policy       | Schemas, allowlists, and permissions enforced in contract state                                    |
| Unclear tx state       | EngineBlox `TxRecord` lifecycle — [Workflows](/introduction/operational-model.md)                  |
| Meta-tx coordination   | Sign vs execute roles and Broadcaster limits — [Meta-transactions](/protocol/meta-transactions.md) |
| Reinventing governance | [Account pattern](/protocol/account-pattern.md) composes core modules                              |

## Who it is for

* **Developers** integrating governed smart accounts — [Developers](/developers/developers.md)
* **Operators** running treasury in the browser — [Console](/platform-bloxchain.app/start.md)
* **Security reviewers** assessing on-chain policy — [Security](/security/security.md)

## Next steps

* [Core principles](/introduction/core-principles.md)
* [Choose your path](/getting-started/getting-started.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/introduction/why-bloxchain.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.