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.
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 an identity (profile, privacy export, organization invites); alerts and watched addresses come with an organization on Pro. 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.
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.
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.
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.
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.
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.
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.
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.
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 and Gates.
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 and Cross-device approval.
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.
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.
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.
Sign-in and organizations
What does signing in add?
Profile and security settings, privacy settings with a personal data export, and organization invites. Signing in on its own adds no hosted service: notifications and watched addresses with alerts (Ethereum and Arbitrum One mainnet only, capped per organization) belong to an organization on Pro. Start free on your device, with no account. Add Pro when you need hosted service. Your account list stays on this device, and paying does not copy it into the organization. Sign in if you have early access; otherwise join the waitlist from the same dialog. See Free, sign-in and organizations.
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.
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.
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.
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 and Security disclaimers.
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.
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 and SDK setup.
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.
Related
Last updated
Was this helpful?