> 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/developers/production-readiness.md).

# Production readiness

This page is the **single checklist** for using Bloxchain Protocol, **bloxchain.app**, and **@bloxchain/sdk** with real assets on mainnet. Enforcement is always **on-chain**; the app and SDK are interfaces only.

## Assurance summary

| Item                     | Status                                                                                                                               |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Third-party audit**    | Completed for the published audited scope — see [Audit status](/security/audit-status.md)                                            |
| **Public audit reports** | Linked on [Audit status](/security/audit-status.md) when published                                                                   |
| **Open source**          | Protocol under MPL-2.0 — [Open source](/resources/license.md)                                                                        |
| **Operational risk**     | Audits do not replace your governance, key management, or legal review — [Security & disclaimers](/security/security-disclaimers.md) |

Pin npm packages and deployed bytecode to the **same tagged** [**Protocol release**](https://github.com/PracticalParticle/Bloxchain-Protocol/releases). Do not run unaudited forks in production without your own review.

## Choose your path

| Role                               | Read first                                                                                                      | Complete before mainnet                                                                        |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| **Operator** (requests, approvals) | [How this works](/introduction/operational-model.md) → [Platform get started](/platform-bloxchain.app/start.md) | [Setup checklist](/platform-bloxchain.app/contracts/checklist.md)                              |
| **Administrator** (policy, roles)  | [Configure policy](/platform-bloxchain.app/overview-1.md)                                                       | Setup checklist + [Security settings](/platform-bloxchain.app/overview-1/security-settings.md) |
| **SDK integrator**                 | [SDK quickstart](/getting-started/quickstart.md) → [Installation](/getting-started/installation.md)             | Testnet validation; pin versions per [Releases](/resources/releases.md)                        |
| **Contract deployer**              | [Protocol deploy get started](/developers/deployment.md)                                                        | Tagged release deploy; review [Security model](/security/security-model.md) for custom code    |
| **Security reviewer**              | [Audit status](/security/audit-status.md) → [Security review guide](/security/security-review-guide.md)         | Run tests on the exact git revision you deploy                                                 |

## Master checklist (mainnet with material value)

### 1. Versions and deployment

* [ ] Deploy or import contracts from a **tagged Protocol release**, not an unreviewed fork
* [ ] Pin `@bloxchain/sdk` and `@bloxchain/contracts` to that same release ([Installation](/getting-started/installation.md))
* [ ] Verify contract address and chain on a block explorer

### 2. Policy and governance (on-chain)

* [ ] Register **operations** for every function your team will use ([Register operations](/platform-bloxchain.app/overview-1/operations.md))
* [ ] Define **roles**, assign **members**, set **permissions** ([Roles and members](/platform-bloxchain.app/overview-1/roles-and-members.md), [Permissions](/platform-bloxchain.app/overview-1/permissions.md))
* [ ] Configure **allowlists** and **execution ports** where required ([Allowlists](/platform-bloxchain.app/overview-1/allowlists.md), [Execution ports](/platform-bloxchain.app/overview-1/execution-ports.md))
* [ ] Review **owner**, **timelock**, **broadcasters**, and **recovery** ([Security settings](/platform-bloxchain.app/overview-1/security-settings.md))
* [ ] Confirm **separation of duties** — no single wallet should request and approve treasury-critical flows unless policy explicitly allows it

### 3. bloxchain.app workspace

* [ ] Complete the full [Setup checklist](/platform-bloxchain.app/contracts/checklist.md)
* [ ] Wallet on the **same network** as the contract ([Connect wallet](/platform-bloxchain.app/account/connect-wallet.md), [Networks](/platform-bloxchain.app/account/networks.md))
* [ ] Operators trained on [New request](/platform-bloxchain.app/overview/submit-request.md), [Transactions](/platform-bloxchain.app/overview/transactions.md), and [Approve and sign](/platform-bloxchain.app/overview/approve-and-sign.md) for meta-tx paths

### 4. Validate on testnet first

* [ ] Exercise request → approve → execute (or meta-tx path) on Sepolia or your staging network ([Networks](/resources/glossary.md#networks))
* [ ] Confirm revert reasons and timelocks behave as expected before mainnet

### 5. Security and legal

* [ ] Read [Security & disclaimers](/security/security-disclaimers.md)
* [ ] Review [Security model](/security/security-model.md) and any **custom contract extensions** separately
* [ ] Complete legal/compliance review for your jurisdiction and use case
* [ ] Know how to [report vulnerabilities](/security/report-vulnerabilities.md) (not public GitHub issues)

## What is in scope for production

| In scope (documented)                                               | Out of scope or not in this release                                                                   |
| ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Account-style governed contracts on Ethereum L1/L2 you deploy       | Post-action hooks — see [Architecture patterns](/protocol/architecture-patterns.md) and Protocol repo |
| bloxchain.app personal workspace, import/deploy, contract workspace | Team orgs, billing, hosted auto-relay — [Roadmap](/resources/roadmap.md)                              |
| SDK read/write against deployed contracts                           | Custody or key storage by Particle                                                                    |

Current product scope: [Platform overview — product scope](/platform-bloxchain.app/start.md#product-scope-current-release).

## Compatibility and updates

* **Versions:** [Releases and compatibility](/resources/releases.md)
* **Doc/product changes:** [Changelog](/resources/changelog.md)
* **Terminology:** [Glossary](/resources/glossary.md)

## When something goes wrong

* **Operators:** [Troubleshooting](/resources/troubleshooting.md) (wallet/network, stuck pending, meta-tx)
* **Security issues:** [Report vulnerabilities](/security/report-vulnerabilities.md) — <security@particlecs.com>
* **Product help:** [Support](/resources/support.md)

## Next steps

* [Getting started](/getting-started/getting-started.md) — all audience paths
* [Audit status](/security/audit-status.md) — audit scope and published reports
* [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 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/developers/production-readiness.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.