> 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 Short answers to the questions people ask most about the Bloxchain Platform and the Bloxchain Protocol. Each answer links to the page with the full detail. ## Getting started ### What is Bloxchain? Bloxchain is a platform for governed blockchain operations. You can operate with the Bloxchain Platform (bloxchain.app) or build with the open-source Bloxchain Protocol (smart contracts plus a TypeScript SDK). Both enforce the same on-chain policy: the Platform orchestrates, the chain enforces. See [What is Bloxchain](/introduction/what-is-bloxchain.md). ### Do I have to sign in? No. Signed out is a full mode, not a trial. Connect a wallet, deploy or import accounts, operate them, sign and submit transactions. Sign-in adds hosted extras (notifications, watched addresses, organization invites). Sign in if you have early access; otherwise join the waitlist from the same dialog, which offers **Join waitlist**. See [Free, sign-in and organizations](/introduction/free-sign-in-organizations.md). ### What do I need to start? A browser wallet and test ETH on Sepolia. Open bloxchain.app, click **Connect wallet**, then go to **Accounts** and choose **Deploy account** or **Import**. See [Quickstart](/get-started/quickstart.md). ### Where is my data? Your account list and any custom networks are stored in this browser only (the **This device** badge). Bloxchain keeps no copy. Export a backup from **Settings → Backup**; the exported file is the only way to move the list to another browser or to get it back after clearing site data. Your on-chain accounts are never affected. See [Backup](/platform-guide/settings/backup.md). ### Can I use my own tools? Yes. Every account is a Protocol contract at an address you own. You can operate it from the Platform, from the SDK, or from any tool that can call the contract. The rules are enforced on-chain, not by the Platform. See [Integration surfaces](/developers/integration-surfaces.md). ## Accounts ### What is a smart account? An on-chain contract you own. It holds assets and executes actions only through governed requests. Every account has three protected roles set at deploy (**Owner**, **Broadcaster**, **Recovery**) and a time lock. See [Accounts](/platform-guide/accounts.md). ### What is a Vault? A freshly deployed account with no spending capability yet. It holds assets, has an owner, recovery and time lock, but no action can move funds until you register actions, assign roles, grant gates and fill the allowlists. A Vault is a finished, locked state, not an error. Today every Discover preset lands as a Vault; capabilities are added afterwards. See [Deploy an account](/platform-guide/accounts/deploy.md). ### Can someone open my account without signing in? Yes, read-only. An account link looks like `https://bloxchain.app/workspace/11155111/0x…`. Anyone with the link can view it. Acting requires a connected wallet that holds a role on that account. See [Open and share](/platform-guide/accounts/open-and-share.md). ## Requests and approvals ### Why is my request Blocked? **Blocked** in the Approvals **State** column means the time lock has not elapsed. Every delayed request must wait the account's time lock before an approver can approve it. The chip shows the remaining time and changes to **Ready** when the wait is over. See [Approvals](/platform-guide/operate/approvals.md). ### Why does an action say "Flow incomplete"? The action is denied by default until its permissions and allowlist are configured. Open **Policies → Actions**, pick the action, and use **Manage permissions** to assign a role to each step (Request, Approval, Execute). Then grant the gates the roles need under **Policies → Gates** and add destinations to the relevant allowlist. See [Manage permissions](/platform-guide/policies/manage-permissions.md) and [Gates](/platform-guide/policies/gates.md). ### Can I approve from another device? Yes, with a signed file. Sign the approval on one device and export it as a `.bloxmeta.json` file from the **Share signed request** dialog. On the other device, open **Approvals → Import signed file**, review the preview and **Add to Approved**. A wallet that is authorised to submit (a broadcaster) then executes it. No sign-in and no relay are needed. See [Signed files](/platform-guide/operate/signed-files.md) and [Cross-device approval](/guides/cross-device-approval.md). ### Who pays gas? The wallet that submits the transaction. For **Wallet** (delayed) requests that is the requester or approver. For **Sign** (meta-transaction) requests the signer pays nothing; the broadcaster who submits the signed payload pays. Gas is always paid from a user wallet in the connected network's native currency (Sepolia test ETH today). ### Is there a relay? An optional **Bloxchain broadcaster** checkbox appears in the compose panel when you are signed in and the environment offers it. It is optional per environment and not promised for every user. Without it, a wallet holding the Broadcaster role submits signed payloads from Approvals. See [New request](/platform-guide/operate/new-request.md). ## Roles and policies ### What is the difference between protected roles and custom roles? **Owner**, **Broadcaster** and **Recovery** are protected roles set at deploy and managed under **Policies → Security**. Custom roles are created by the owner under **On-chain access → Roles**; signers are addresses that hold one or more roles. See [Roles](/platform-guide/access/roles.md). ### What are gates, and why can I not turn one off? Gates are role-scoped on-chain authorizations that let a granted action run. A gate is permanent for that role. Deleting a custom role clears its gates; system-role gates stay on. See [Gates](/platform-guide/policies/gates.md). ## Sign-in and organizations ### What does signing in add? Notifications (in-app bell and email), watched addresses with alerts (Ethereum and Arbitrum One mainnet only, capped), profile and privacy settings, and organization invites. Your account list stays on this device. Sign in if you have early access; otherwise join the waitlist from the same dialog. See [Free, sign-in and organizations](/introduction/free-sign-in-organizations.md). ### What is an organization? A paid shared cloud workspace for a team (**Pro**, **Team** or **Enterprise**; pricing is shown at checkout or on request, and Enterprise is contact us). It gives a shared account list (**Cloud** residency), **Member addresses**, members and roles, organization networks, billing and invoices. Until checkout completes the organization shows **Checkout required** and **Cloud off**. See [Organizations and billing](/platform-guide/settings/organizations-and-billing.md). ## Networks and security ### Is mainnet supported? The Platform runs on Sepolia today (chain 11155111), which is where the official Protocol deployments live. Ethereum mainnet is coming soon. You can add custom EVM networks under **Settings → Networks**, but no official addresses are published for them. See [Supported networks](/introduction/supported-networks.md). ### Is this audited? The Protocol core is audited by Nethermind (NM\_0828), core framework scope. Custom extensions and your own configuration are not covered by that audit. The hosted Platform is not covered either. See [Audit status](/security/audit-status.md). ### Can I use this in production? The Protocol core is audited by Nethermind (NM\_0828), core framework scope, and you can deploy it with the SDK on the networks you control. Custom extensions and your own configuration are not covered by that audit. The Platform is **Alpha · Testnet · Local-first**: it runs on Sepolia today, and Ethereum mainnet is coming soon. Treat it as a way to learn the model and rehearse your policy, not as a place for material value today. See [Production readiness](/developers/deployment/production-readiness.md) and [Security disclaimers](/security/audit-status/security-disclaimers.md). ### Does Bloxchain hold my keys? No. The architecture is non-custodial: you hold the keys, and Bloxchain never holds a key. The Platform builds and displays transactions; your wallet signs them. See [Security model](/security/security-model.md). ## Developers ### When should I use the SDK instead of the Platform? Use the Platform for people operating accounts in a browser. Use `@bloxchain/sdk` for backends, automation and AI agents. Both act on the same contracts and the same rules. See [Integration surfaces](/developers/integration-surfaces.md) and [SDK setup](/developers/sdk-setup.md). ### How do I pin versions? Install `@bloxchain/sdk` and `@bloxchain/contracts` at the same release as the contracts you deploy or import. See [Releases and compatibility](/resources/releases.md). ## Related * [Glossary](/resources/glossary.md) * [Limits and defaults](/resources/limits-and-defaults.md) * [Troubleshooting](/resources/troubleshooting.md) * [Support and community](/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=&goal= ``` `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.