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

# Security model

Assumptions, trust boundaries, threats, and what this documentation does **not** cover.

> **Production** — Third-party security audit completed for the published scope. See [Production readiness](/developers/production-readiness.md) and [Audit status](/security/audit-status.md).

## Design assumptions

* **On-chain enforcement** — Policy in smart contracts is the source of truth; UIs and SDKs are not trusted for authorization.
* **Separation of duties** — Owner, Broadcaster, and Recovery are distinct protected roles; custom roles further split day-to-day work.
* **Initializer-based implementations** — Core Solidity uses OpenZeppelin `Initializable` patterns. **Official** CopyBlox / App Explorer deployments are **non-upgradeable EIP-1167 clones**.
* **Audited releases** — Deployers use tagged releases from [Bloxchain-Protocol](https://github.com/PracticalParticle/Bloxchain-Protocol/releases); initializers run once at clone time for official CopyBlox paths.
* **Custom proxy deploys** — Integrators may deploy upgradeable proxy stacks with their own factories — see [Deployment](/developers/deployment.md#immutable-vs-upgradeable).
* **Explicit operations** — Only registered function schemas and allowlisted targets may execute through the guard.
* **Operator hygiene** — Keys stored securely (HSM/hardware wallet); operators know which wallet they use ([My access](/platform-bloxchain.app/overview/my-access.md)).
* **Non-custodial product** — bloxchain.app stores workspace metadata only; notifications are informational, not policy.

We do **not** assume legal/tax treatment, RPC availability, or protection against social engineering.

## Trust boundaries

![Trust boundaries](/files/aiB5Uhi9Ny1UNI8EyaLd)

| Trusted for authorization         | Not trusted for authorization       |
| --------------------------------- | ----------------------------------- |
| Governed smart contracts          | bloxchain.app backend (config only) |
| Wallet signatures (incl. EIP-712) | SDK client code                     |
| On-chain RBAC state               | Off-chain indexes and notifications |

## Threat model

### Assets

| Asset                  | Impact if compromised                                                                                        |
| ---------------------- | ------------------------------------------------------------------------------------------------------------ |
| Owner keys             | Policy and ownership changes                                                                                 |
| Broadcaster keys       | Unauthorized meta-tx submission (within RBAC)                                                                |
| Recovery keys          | Emergency paths invoked                                                                                      |
| Custom role wallets    | Operations permitted to those roles                                                                          |
| Contract upgrade admin | Malicious implementation swap (**custom upgradeable proxies only** — not official immutable CopyBlox clones) |

### Threat actors

External attackers, malicious insiders, compromised operators, faulty integrators.

### Mitigations (on-chain)

| Threat           | Mitigation                                                                                                   |
| ---------------- | ------------------------------------------------------------------------------------------------------------ |
| Reentrancy       | CEI patterns, guarded execution                                                                              |
| RBAC bypass      | Protected roles, permission bitmaps                                                                          |
| Replay (meta-tx) | EIP-712 domain, nonces                                                                                       |
| Timelock bypass  | `releaseTime` enforcement                                                                                    |
| Allowlist bypass | GuardController target checks                                                                                |
| Upgrade hijack   | N/A for official immutable clones; for custom upgradeable deploys: proxy admin controls and audited releases |

Organizational security (phishing, SOC programs) is your responsibility — out of protocol scope.

## Threat areas reviewers should examine

* **Reentrancy and CEI** — Guarded execution and external calls
* **RBAC bypass** — Role assignment, protected roles, function permissions
* **Meta-transaction replay** — Nonces, domain separation, signer authorization
* **Timelock bypass** — `releaseTime` enforcement on approval paths
* **Allowlist gaps** — Execution targets and operation registration
* **Upgrade safety** — Only for **custom upgradeable** proxy deploys. Official CopyBlox clones are immutable — plan [migration](/platform-bloxchain.app/recovery.md#migrating-to-a-new-contract) instead

Reading order for auditors: [Security review guide](/security/security-review-guide.md).

## What we do not cover here

* **Operational security** of your organization (key management programs, etc.)
* **Smart contract audits** of your custom extensions beyond the Protocol baseline
* **Legal or regulatory** classification of your use case
* **Economic / MEV** risks on public networks

## Incident response (high level)

![Incident response](/files/SxTIwrXv6mtWGZ7RXjic)

Report vulnerabilities: [Report vulnerabilities](/security/report-vulnerabilities.md).

## Product disclaimers

bloxchain.app is **non-custodial**. See [Security & disclaimers](/security/security-disclaimers.md).

## Next steps

* [Audit status](/security/audit-status.md)
* [TECHNICAL\_OVERVIEW.md](https://github.com/PracticalParticle/Bloxchain-Protocol/blob/99beac2d6e6d7567c23b25cecaf6f4053f31c987/TECHNICAL_OVERVIEW.md)
* [SECURITY.md](https://github.com/PracticalParticle/Bloxchain-Protocol/blob/99beac2d6e6d7567c23b25cecaf6f4053f31c987/SECURITY.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/security/security-model.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.