> 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/audit-status/known-limitations.md). # Known limitations Honest boundaries of the Protocol, the Bloxchain Platform and this documentation as they stand today. ## Protocol | Limitation | Detail | | ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Audit scope** | The Nethermind NM\_0828 audit covers the core framework library at one commit, named in the report. It does not track later releases on its own, so compare that commit against the version you are running. Templates, examples, the SDK, your extensions and unaudited forks are outside it. See [Audit status](/security/audit-status.md). | | **Official accounts are not upgradeable** | The official factory, BasicFactory (and the Platform's **Deploy account**), creates EIP-1167 clones fixed to the BasicAccount template. Logic cannot be changed in place. | | **Owner is the deploying wallet** | The official factory mints an account only for the wallet that sends the deploy. You cannot mint an account for another owner. Broadcaster and recovery are separate addresses you choose. | | **Deploy from a regular wallet** | A deploy uses about 16.16M gas. Networks that apply EIP-7825 cap one transaction at 16,777,216 gas, so only a direct call from a regular wallet (EOA) fits. A Safe, an ERC-4337 smart account, a forwarder or a multicall cannot be relied on to reach the factory. Glamsterdam increases the gas cost of a deploy. See [Official mint rules](/developers/deployment.md#official-mint-rules). | | **Custom upgradeable deploys** | Initializer-based contracts can sit behind a UUPS or transparent proxy if you build your own factory. Proxy admin and storage layout are your responsibility. See [Immutable vs upgradeable](/developers/deployment.md#immutable-vs-upgradeable). | | **Migration instead of upgrade** | New logic means a new account, a policy rebuild, governed asset moves and updated allowlists. See [Recovery and incidents](/platform-guide/recovery.md#limits). | | **Signed paths skip the time lock** | Signed approval and One signature execute as soon as a broadcaster submits them; the signature is the authorisation. Only Delayed release waits. | | **No global signature revocation** | A signed but unsubmitted payload stays valid until its deadline or until the signer's nonce is consumed. See [Meta-transactions](/protocol-reference/api-reference/meta-transactions.md). | | **Gas** | Governed flows cost more gas than a plain wallet transfer; users pay it from their own wallet. | | **Composability** | Contracts you allowlist bring their own risk surface. | ## Bloxchain Platform | Limitation | Detail | | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Alpha** | **Alpha · Local-first.** Official deployments are live on the 15 supported networks. Alpha is not a certification that an operation is safe for material value. | | **No custody, no key recovery** | Bloxchain never holds a key and cannot recover one you lose. The **Recovery** role is your fallback; set it. See [Recovery and incidents](/platform-guide/recovery.md). | | **Local-first data lives on this device** | Your account list, names, custom networks and stored signed payloads are in this browser only. Clearing site data removes them. Bloxchain keeps no copy; the export from **Settings → Backup** is the only copy. See [Backup and restore](/platform-guide/settings/backup.md). | | **Sign-in needs early access** | Sign in if you have early access. Otherwise join the waitlist from the same dialog. The Free path needs no account and is open to everyone, so nothing on this device depends on signing in. | | **Organizations are paid** | Shared account lists, member addresses, members and roles and billing exist only in a Pro, Team or Enterprise organization. An organization that has not completed checkout is **Checkout required** and shows no accounts. See [Organizations and billing](/platform-guide/settings/organizations-and-billing.md). | | **Relay is optional** | The **Bloxchain broadcaster** needs sign-in and is not promised in every environment. Without it, a wallet holding the Broadcaster role submits signed payloads from **Approvals**. | | **Signed files are bearer instruments** | Anyone who receives a `.bloxmeta.json` and can submit may broadcast it until it expires or is used. Share it like a signed cheque. See [Signed files](/platform-guide/operate/signed-files.md). | | **Presets do not pre-configure policy** | Every preset on **Discover** deploys the same governed account, which lands as a **Vault**. Actions, roles, gates and allowlists are configured afterwards. | | **Gates are permanent** | Once granted to a role, a gate cannot be turned off. Delete the custom role to clear its gates; system-role gates stay on. | | **Reference prices are indicative** | The Value column in **Assets** comes from a third-party price feed and resolves on Ethereum and Arbitrum One only. Everywhere else, Sepolia included, it is blank. | | **Watched addresses** | Watched addresses and alerts need an organization on Pro. They cover Ethereum and Arbitrum One mainnet only, with a cap per organization shared by its members. | | **Mobile** | Sharing signed files from a phone is not documented as supported. | ## Documentation * Protocol pages under [Protocol](/protocol-reference/protocol.md) describe the pinned commit listed on [Releases and compatibility](/resources/releases.md#protocol-documentation-pin). Newer tags may add behaviour before the pin advances. * The Platform ships continuously; a screen may change before its page does. The [Changelog](/resources/releases.md#changelog) records documentation updates. ## Related * [Security model](/security/security-model.md) * [Disclaimers](/security/audit-status/security-disclaimers.md) * [Limits and defaults](/resources/limits-and-defaults.md) * [Roadmap](/resources/roadmap.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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bloxchain.app/security/audit-status/known-limitations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.