> 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/glossary.md). # Glossary Terms used in the Bloxchain Platform, in this documentation and in the Bloxchain Protocol, grouped by topic. Bold labels match what you see in the app. ## Products | Term | Meaning | | --------------------------------- | ------------------------------------------------------------------------------------------------------------ | | **Bloxchain Platform** | The hosted app at bloxchain.app where you deploy, operate and configure smart accounts. Also "the Platform". | | **Bloxchain Protocol** | The open-source foundation: smart contracts plus the TypeScript SDK. Also "the Protocol". | | **SDK** | `@bloxchain/sdk`, the TypeScript client library. Part of the Protocol, not a separate product. | | **Particle CS** | The company behind Bloxchain (Particle Crypto Security Ltd). | | **Alpha · Testnet · Local-first** | The maturity badge on the Platform: alpha software, testnet only, inventory stored on your device. | ## Accounts and spaces | Term | Meaning | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Smart account** | An on-chain contract you own. It holds assets and executes actions only through governed requests. "Account" for short; "governed account" in explanatory prose. | | **Accounts** | The list page of tracked and opened accounts on this device. | | **Discover** | The page that lists presets. Filters: **Personal Security** and **Team Operations**. | | **Preset** | A job-oriented entry on Discover (Personal security, Treasury, Asset Issuance, Payments). Today every preset deploys the same governed account. | | **Capability** | The same idea on the Marketplace product page: a feature set applied to an account after deploy. | | **Marketplace** | The `/marketplace` page listing official products. One product today: **Bloxchain Account**. | | **Vault** | A freshly deployed account with no spending capability. The transfer actions are already registered, but no role is permitted to use them and every allowlist is empty, so nothing can move. A finished, locked state, not an error. | | **Base** (shell) | Governed smart account with time-locked ownership, roles and recovery. The default shell. | | **Web3** (shell) | Everything in Base plus EIP-1271, so external apps can verify signatures from the account. Minimum time lock 1 day. | | **Deploy factory** | The contract that creates a new account clone in one transaction. Shown under **Advanced** in the deploy dialog. | | **Template** (account template) | The reference account contract that clones point to. | | **CopyBlox** | The Protocol's deploy factory. It creates immutable clones (EIP-1167): the logic behind an address cannot change. | | **AccountBlox** | The Protocol's reference account template. | | **EngineBlox** | The shared Protocol engine contract that account clones use. | | **Account details** | Drawer with the account mark, display name and identity. Names and marks are stored on this device, not on-chain. | | **Personal** (space) | Your own space: the Free path on this device, signed in or not. There is no Personal plan. | | **Organization** (space) | A paid, shared cloud workspace for a team. | | **Member addresses** | An organization's address book, used for access control and audit. Non-custodial. | | **This device** | Residency badge: the inventory lives in this browser only. | | **Cloud** | Residency badge: the inventory belongs to an active organization and is shared. | | **Cloud off** | Residency badge: the organization exists but is inactive (checkout not completed or plan lapsed). | | **Checkout required** | Organization status before checkout completes. Never the same as Free. | | **Free** | The signed-out path. Everything on this device, no sign-in. | | **Account** (sign-in) | An optional signed-in account that adds hosted extras. Sign in if you have early access; otherwise join the waitlist from the same dialog. | | **Pro**, **Team**, **Enterprise** | Paid organization plans. Pricing is shown at checkout or on request; Enterprise is contact us. | | **Backup** | Export or import of your inventory as JSON in **Settings → Backup**. Modes: **Merge** and **Replace**. | ## Roles and access | Term | Meaning | | ---------------------------------- | ------------------------------------------------------------------------------------------------------------- | | **Owner** | Protected role. Controls the account and approves delayed requests. Ownership transfer is time-locked. | | **Broadcaster** | Protected role (1 to 3 addresses). May submit signed meta-transactions and pays the gas. | | **Recovery** | Protected role. A fallback address that can take ownership in an emergency. | | **Protected roles** / system roles | Owner, Broadcaster and Recovery. Set at deploy, managed under **Policies → Security**. | | **Custom role** | A role the owner defines under **On-chain access → Roles** (name plus maximum wallets). | | **Signer** | An address holding one or more roles. Managed under **On-chain access → Signers**. | | **On-chain access** | Rail section containing **Signers** and **Roles**. | | **My access** | Page showing your roles on this account and which operations you can act on at each phase. | | **Time lock** | The minimum wait before a delayed request can be approved. Must be greater than zero. Adjective: time-locked. | ![Roles separation](https://2633730519-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GcVTQuj6X0G3RZ3YY7r%2Fuploads%2Fgit-blob-78b5f5d5237dc41134861952c7c6d91ac7fcb246%2Froles-separation.svg?alt=media) ## Policies | Term | Meaning | | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Policies** | Rail nest containing **Security**, **Actions**, **Gates** and the allowlists. | | **Security** | Owner, recovery, time lock and broadcasters for the account. | | **Action** | A registered function the account can perform under policy. The **Actions** page lists each one by its on-chain operation name in upper case, with the function signature underneath, for example `NATIVE_TRANSFER` / `__bloxchain_native_transfer__()`. | | **Operation name** | The upper-case name shown in the **Action** column, for example `NATIVE_TRANSFER`, `ERC20_TRANSFER`, `CONTROLLER_CONFIG_BATCH`. Several functions can share one operation name. | | **Administration** (action type) | Actions that change the account's own configuration, such as `CONTROLLER_CONFIG_BATCH`. | | **Custom** (action type) | The type shown for operations that move value or run your own functions, including `NATIVE_TRANSFER` and `ERC20_TRANSFER`. | | **Phases** | The three steps of an action: **Request → Approval → Execute**. Each has its own permissions. | | **Manage permissions** | The per-action editor where you assign a role to each step of each execution path. | | **Gate** | A role-scoped on-chain authorization that lets a granted action run. Permanent for that role. | | **Gates mismatch** | Flow status: a role has access on Actions but its gate is not granted. | | **Flow incomplete** | Flow status: denied by default until permissions and allowlist are configured. | | **Permanent grant** | A grant on a non-revocable action. It cannot be taken back. | | **Allowlists** | Collective name for the lists that restrict destinations. An empty list means nothing is allowed. | | **Allowed recipients** (Recipients) | Addresses allowed to receive native transfers. | | **Allowed payees** (Payees) | Addresses allowed as payout destinations for attached payments. | | **Allowed contracts** | Contract destinations governed operations may call, with their assigned functions. | ### Operation names, signatures and selectors These are installed on every account at deploy. You do not register them yourself. The five below govern transfers and the guard controller, and they are what the **Actions** page is for. Five more install alongside them and are managed on their own pages: `OWNERSHIP_TRANSFER`, `BROADCASTER_UPDATE`, `RECOVERY_UPDATE` and `TIMELOCK_UPDATE` on [Security](/platform-guide/policies/security.md), and `ROLE_CONFIG_BATCH` on [Roles](/platform-guide/access/roles.md). | Operation name | Function signature | What it is | | ---------------------------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `NATIVE_TRANSFER` | `__bloxchain_native_transfer__()` | Native transfer: sending the network's native coin to an allowlisted recipient. The reserved signature identifies the operation; the amount and recipient travel in the request, not in the signature. | | `ERC20_TRANSFER` | `transfer(address,uint256)` | ERC-20 transfer: sending a token the account holds. | | `ATTACHED_PAYMENT_RECIPIENT` | `__bloxchain_attached_payment_recipient__()` | Payout destination for an action that carries an attached payment. | | `CONTROLLER_OPERATION` | `executeWithTimeLock(address,uint256,bytes4,bytes,uint256,bytes32)` and six related functions | Governed execution through the controller, used for calls to allowlisted contract targets. | | `CONTROLLER_CONFIG_BATCH` | `executeGuardConfigBatch((uint8,bytes)[])` and one signed variant | The signed batch that applies a configuration change. Grants on it cannot be revoked. | Thirty function schemas in total, grouped under ten operation names: twelve under the five above, sixteen under the four Security operations, and two under `ROLE_CONFIG_BATCH`. Several functions share one operation name, which is why there are far fewer names than schemas. See [Actions](/platform-guide/policies/actions.md) and [Limits and defaults](/resources/limits-and-defaults.md). A **function selector** is the first four bytes of the keccak-256 hash of the signature, so it is the same on every network and can always be derived from the signature above. The app shows you the signature and never asks for a selector, so this documentation does not print selector values that a future contract release could change. ## Requests and statuses | Term | Meaning | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Governed lifecycle** | Request → Wait → Review & approve → Execute → Record. Rules apply from request through settlement. | | **New request** | The primary button that opens the compose dialog. | | **Execution path** | How an action is carried out. Three paths exist; an action may enable one or more. | | **Delayed release** (tab **Delayed**) | Request posted on-chain, time lock runs, an approver approves or cancels on-chain, then it executes. | | **Signed approval** (tab **Signed**) | Request posted on-chain, approver signs an approval or cancellation off-chain, a broadcaster submits it. | | **One signature** (tab **One sign**) | Requester signs request and approval in one signature; a broadcaster submits and executes. | | **Wallet** (compose) | Post the request on-chain now: the delayed path. | | **Sign** (compose) | Sign a meta-transaction that you or a permitted role or broadcaster submits before it expires. | | **Meta-transaction** | A signed payload (EIP-712) that someone else submits on-chain. The compose panel shows its expiry, for example "Meta-tx expires in 1h". | | **Bloxchain broadcaster** | Optional relay that submits signed payloads automatically. Sign-in required; available per environment. | | **Signed file** | A `.bloxmeta.json` export of a signed request or approval for another device to import and submit. An authorize → broadcast handoff. Treat it like a signed check. | | **Approvals** | The open queue: on-chain pending requests plus stored signed transactions. Tabs **All**, **Pending**, **Approved**. | | **History** | Settled operations. Filters **Executed**, **Cancelled**, **Failed**. | | **Needs attention** | Overview card listing open requests and setup gaps. | ### Status labels in the Platform | Label | Meaning | | -------------------------------- | ----------------------------------------------------------- | | **New** | Request just created. | | **Awaiting Approval** | Waiting for an approver. | | **Awaiting Your Approval** | Waiting for an approver, and your wallet can approve. | | **Approved** | Approval recorded; not yet executed. | | **Cancelled** | Request cancelled before execution. | | **Expired** | A signed payload passed its expiry before it was submitted. | | **Ready to Execute** | All conditions met; a permitted wallet can execute. | | **Ready to Submit Cancellation** | A signed cancellation is stored and can be submitted. | | **Executing** | Execution transaction in flight. | | **Executed** | Finished successfully. | | **Submitting** | A signed payload is being broadcast. | | **Pending Confirmation** | Transaction sent, waiting for the chain. | | **Confirmed** | Transaction confirmed on-chain. | | **Failed** | Execution reverted or a policy check failed. | ### Approvals State chips | Chip | Meaning | | ----------------------- | ------------------------------------------------------------------- | | **Blocked** (with time) | Time lock still running; shows the remaining wait. | | **… left** / **Ready** | Countdown to approval eligibility, then ready. | | **Cancel · … left** | A cancellation is possible for the shown time. | | **Expired** | The stored signed transaction can no longer be executed. Delete it. | Row status text includes **Waiting Period**, **Awaiting Approval** and **Execution Ready**. ## Networks and data | Term | Meaning | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Sepolia** | Ethereum test network, chain 11155111. The only network with official Protocol deployments today. | | **Ethereum mainnet** | Coming soon on the Platform. | | **Custom network** | An EVM network you add under **Settings → Networks** (name, chain ID, RPC URL, explorer URL, currency, Testnet and Default flags). Stored on this device. | | **Wrong network** | Top-bar state when the connected wallet is on an unsupported chain. | | **RPC** | The endpoint used for reads. The Platform reads over its own HTTPS endpoint for the network, or the saved RPC URL on a custom network; your wallet's provider is used only to send a transaction. | | **Value** (Assets) | Indicative reference price. Resolves on Ethereum and Arbitrum One only; everywhere else, Sepolia included, the column shows a dash. | | **Explorer** | A block explorer such as Etherscan for Sepolia. Linked from **Share → View on explorer**. | | **Open link** | The account URL, `https://bloxchain.app/workspace//
`. Read-only for anyone; acting requires a role. | ## Protocol terms | Term | Meaning | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **TxRecord** | The on-chain record of one governed operation. | | **TxStatus** | The protocol status enum: `UNDEFINED`, `PENDING`, `EXECUTING`, `COMPLETED`, `FAILED`, `CANCELLED`, plus `PROCESSING_PAYMENT` when payment-gated execution applies. | | **Operation type** | A `bytes32` identifier grouping governed functions. | | **Function schema** | The on-chain registration of a function: signature, selector, operation name, handlers, permissions and path behaviour. Twelve are installed at deploy. | | **SecureOwnable** | The Protocol module behind Owner, Broadcaster, Recovery and the time lock. See [SecureOwnable](/protocol-reference/api-reference/secure-ownable.md). | | **RuntimeRBAC** | The module behind custom roles and per-step permissions. See [Runtime RBAC](/protocol-reference/api-reference/runtime-rbac.md). | | **GuardController** | The module behind allowlists and guarded external calls. See [Guard controller](/protocol-reference/api-reference/guard-controller.md). | | **EIP-712** | The typed-data signing standard used for meta-transactions. | | **EIP-1167** | The minimal proxy (clone) standard used by the deploy factory. | | **EIP-1271** | The contract signature standard enabled by the Web3 shell. | ### The nine action steps | Step | Phase | | ------------------------- | -------- | | Pending Request | Request | | Approve | Approval | | Cancel | Approval | | Sign and approve request | Request | | Sign approval | Approval | | Sign cancellation | Approval | | Finalize approved request | Execute | | Finalize approval | Execute | | Finalize cancellation | Execute | Protocol lifecycle in one line: ``` UNDEFINED → PENDING → EXECUTING → COMPLETED | FAILED | CANCELLED ``` ## Related * [How it works](/introduction/how-it-works.md) * [Platform guide](/platform-guide/platform.md) * [State machine engine](/protocol-reference/bloxchain-architecture/state-machine-engine.md) * [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/resources/glossary.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.