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

# FAQ

## What is bloxchain.app?

A hosted, **non-custodial** workspace to operate **Bloxchain Protocol** account contracts: roles, requests, approvals, meta-transactions, and policy configuration. We never hold your private keys.

## Do I need the Protocol repo to use the app?

No for day-to-day operations. You need a deployed contract address (import) or you deploy a clone from the App Explorer. Developers extend contracts via the [Protocol on GitHub](https://github.com/PracticalParticle/Bloxchain-Protocol).

## Is the software audited?

Yes. The Bloxchain Protocol has completed a **third-party security audit** for the published audited scope. Public reports are linked on [Audit status](/security/audit-status.md) as they are published. An audit does not remove operational risk—see [Security & disclaimers](/security/security-disclaimers.md).

## Can I use this in production?

**Today:**

* **Protocol (official deployments):** use **Ethereum Sepolia** with [published addresses](https://github.com/PracticalParticle/Bloxchain-Protocol#deployed-addresses) and tagged releases.
* **bloxchain.app:** **alpha**, **testnet-first** (Sepolia).

**Coming soon:**

* **Official Ethereum mainnet Protocol deployments** (Particle-published addresses).
* **Hosted Ethereum mainnet** on bloxchain.app (roadmap — separate announcement).

The Protocol core is **audited** (Nethermind NM\_0828); an audit does not remove operational or smart-contract risk. See [Production readiness](/developers/production-readiness.md) and [Audit status](/security/audit-status.md).

Checklists:

* **All audiences:** [Production readiness](/developers/production-readiness.md)
* **Operators on bloxchain.app:** [Setup checklist](/platform-bloxchain.app/contracts/checklist.md)
* **Integrators:** Pin SDK and contracts to the same [Protocol release](https://github.com/PracticalParticle/Bloxchain-Protocol/releases); validate on testnet first ([Installation](/getting-started/installation.md))
* **Deployers:** Use a tagged audited release ([Deploy get started](/developers/deployment.md))

## What is in the current release?

See [Platform overview — product scope](/platform-bloxchain.app/start.md#product-scope-current-release). Planned features: [Product roadmap](/resources/roadmap.md).

## How do I use testnet?

Deploy on Sepolia via the [Protocol README](https://github.com/PracticalParticle/Bloxchain-Protocol#deployed-addresses), import the contract on bloxchain.app, and [switch networks](/platform-bloxchain.app/account/networks.md). Or use the [SDK](/getting-started/quickstart.md). Details: [Networks](/resources/glossary.md#networks).

## When should I use the SDK vs the Console?

Use **bloxchain.app** for human operators in a browser. Use the [SDK](/getting-started/quickstart.md) for custom backends and automation. Both talk to the same on-chain rules. See [Integration surfaces](/developers/integration-surfaces.md).

## Can I run entirely on my own infrastructure?

Yes. Deploy Protocol contracts and integrate via [@bloxchain/sdk](/getting-started/quickstart.md). You may still use the Console optionally. See [Integration surfaces](/developers/integration-surfaces.md).

## How do I pin versions for production?

Use matching **Protocol release tags**, **npm SDK versions**, and documented deploy artifacts. See [Versioning strategy](/resources/releases.md) and [Releases](/resources/releases.md).

## How do meta-transactions work in the app?

Authorized wallets **sign** EIP-712 data in the browser. Items stay in **Transactions → Open** until executed. Some environments offer optional **Sign and broadcast** after sign; otherwise a **Broadcaster** wallet must **Execute** on-chain. Fully managed relay for all users is on the [Roadmap](/resources/roadmap.md). Details: [Approve and sign](/platform-bloxchain.app/overview/approve-and-sign.md).

## Wallet or network errors?

See [Troubleshooting — wallet or network mismatch](/resources/troubleshooting.md#wallet-or-network-mismatch).

## Where is terminology defined?

[Glossary](/resources/glossary.md) (includes statuses, roles, operation types, networks).

## Get more help

* [Production readiness](/developers/production-readiness.md)
* [Audit status](/security/audit-status.md)
* [Troubleshooting](/resources/troubleshooting.md)
* [Get support](/resources/support.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/resources/faq.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.