> 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 you may hear in **bloxchain.app**, team discussions, and protocol documentation — with canonical on-chain meanings.

## Operations & transactions

| Term (everyday)   | Protocol meaning                                                    |
| ----------------- | ------------------------------------------------------------------- |
| Proposal / intent | Governed operation **request** → `TxRecord` in `PENDING`            |
| Approval          | Delayed approve, meta approve, or request-and-approve → `EXECUTING` |
| Execution         | Guarded external call in `EXECUTING` → `COMPLETED` or `FAILED`      |
| Cancellation      | `PENDING` → `CANCELLED`                                             |

## Roles

| Term                   | Protocol meaning                                |
| ---------------------- | ----------------------------------------------- |
| Admin / emergency      | `OWNER_ROLE`, `RECOVERY_ROLE` (SecureOwnable)   |
| Gas relayer / executor | `BROADCASTER_ROLE` (meta-transaction submitter) |
| Policy / roles         | RuntimeRBAC + function schemas + action bitmaps |

## Protected roles (SecureOwnable)

| Role            | Typical capabilities                                                |
| --------------- | ------------------------------------------------------------------- |
| **Owner**       | Admin operations, approve time-locks, configure critical parameters |
| **Broadcaster** | Execute meta-transactions (pays gas)                                |
| **Recovery**    | Standard recovery / ownership flows per schema                      |

These are not custom RuntimeRBAC roles.

## Custom roles (RuntimeRBAC)

Administrators define roles (for example `TREASURY`, `COMPLIANCE`) and assign wallets. Permissions are per **function selector** / operation type:

* request
* approve
* cancel
* sign (meta-tx)
* execute

![Roles separation](/files/W9OXvNRp1juVtkzFNwrY)

## Policy & contracts

| Term          | Protocol meaning                                       |
| ------------- | ------------------------------------------------------ |
| Allowlist     | GuardController per-selector **target whitelist**      |
| Smart account | **Account** contract (e.g. AccountBlox) at one address |
| Hooks         | `IOnActionHook.onAction` — **post-action only**        |

## Transaction status (TxStatus)

Canonical lifecycle:

```
UNDEFINED → PENDING → EXECUTING → COMPLETED | FAILED | CANCELLED
```

Optional: `PROCESSING_PAYMENT` when payment-gated execution applies.

### States

| Status      | Meaning                                                              |
| ----------- | -------------------------------------------------------------------- |
| `UNDEFINED` | Initial / unset before a governed record is created                  |
| `PENDING`   | Request submitted; awaiting approval or meta-tx execution per policy |
| `EXECUTING` | Approved path in progress; guarded execution running                 |
| `COMPLETED` | Execution finished successfully                                      |
| `FAILED`    | Execution failed (revert or policy failure)                          |
| `CANCELLED` | Cancelled from `PENDING`                                             |

Timelock delay is enforced at **delayed approval**, not as a separate `TxStatus` value.

### In bloxchain.app

**Workspace → Transactions** has two tabs:

* **Open** — in-progress items (pending approval, signed meta-tx awaiting execute)
* **Completed** — terminal history

See [Transactions](/platform-bloxchain.app/overview/transactions.md) and [Approve and sign](/platform-bloxchain.app/overview/approve-and-sign.md).

## Operation types

A **bytes32** identifier (often `keccak256` of a name) grouping governed functions. Definition libraries in the Protocol repo declare supported types for SecureOwnable, RuntimeRBAC, and GuardController.

### Function schema

Each registered function includes:

* **selector** (`bytes4`)
* **handlers** and execution ports
* Permission requirements
* Time-lock vs meta-tx behavior

### Discovery

* Platform: [Register operations](/platform-bloxchain.app/overview-1/operations.md)
* SDK: snapshot / `getOperationTypesFromSchemas` helpers
* On-chain: `SecureOperationState` supported functions set
* Docs: [Definition contract](/protocol/definition-contract.md) · [Guard controller](/protocol/guard-controller.md)

## Networks

| Network          | Chain ID | bloxchain.app | Notes                                                                                                         |
| ---------------- | -------- | ------------- | ------------------------------------------------------------------------------------------------------------- |
| Hardhat local    | 31337    | —             | `npm run` local scripts                                                                                       |
| Sepolia          | 11155111 | Supported     | Official Protocol deployments today; primary testnet for hosted alpha                                         |
| Ethereum mainnet | 1        | Coming soon   | Official Protocol mainnet deployments coming soon; hosted Console mainnet on [Roadmap](/resources/roadmap.md) |

Canonical deployed addresses: [Protocol README — Deployed addresses](https://github.com/PracticalParticle/Bloxchain-Protocol#deployed-addresses). Always verify on [Etherscan](https://sepolia.etherscan.io/) before use.

When registering an app on bloxchain.app, select the same network as your deployment ([Switch networks](/platform-bloxchain.app/account/networks.md)).

### Using Sepolia (testnet)

1. **Deploy or clone** an Account-style contract using the [Protocol README — Try on Sepolia](https://github.com/PracticalParticle/Bloxchain-Protocol#try-on-sepolia) (for example `npm run create-wallet` on Sepolia).
2. **Operate in the browser:** [Add a contract](/platform-bloxchain.app/contracts/desktop.md) on bloxchain.app with the contract address and Sepolia network.
3. **Operate in code:** use [@bloxchain/sdk](/getting-started/quickstart.md) against the same address and chain.

## Security & production

| Term                       | Meaning                                                                                                                                       |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Audited scope              | Protocol revision covered by the published third-party audit — see [Audit status](/security/audit-status.md)                                  |
| Production readiness       | Mainnet checklist for Protocol, app, and SDK — [Production readiness](/developers/production-readiness.md)                                    |
| Setup checklist            | bloxchain.app workspace verification before treasury use — [Setup checklist](/platform-bloxchain.app/contracts/checklist.md)                  |
| Tagged release             | Immutable Protocol version on [GitHub releases](https://github.com/PracticalParticle/Bloxchain-Protocol/releases); pin SDK/contracts to match |
| Immutable clone            | Official CopyBlox EIP-1167 deployment — logic cannot change at the same address                                                               |
| Upgradeable proxy (custom) | Integrator-owned deploy — not the default official factory path                                                                               |

## Platform (bloxchain.app)

| Term                     | Meaning                                                                                                                 |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| App                      | A registered governed contract in your bloxchain.app workspace                                                          |
| Contract workspace       | Per-tab UI: **Workspace** (Overview, My access, Assets, Transactions), **Deployment**, **Allowlists**, **Help & setup** |
| Open queue               | **Transactions → Open** — pending and signed in-progress items                                                          |
| Signed, awaiting execute | Meta-tx signed in-app; broadcaster must **Execute** (shown in **Open**)                                                 |

## See also

* [Governed operations](/introduction/protocol-basics.md)
* [Transaction lifecycle](/introduction/operational-model.md)
* [Diagrams](/introduction/operational-model.md) · [Core contract graph](/protocol/core-contract-graph.md)
* [Configure roles and members](/platform-bloxchain.app/overview-1/roles-and-members.md)
* [Runtime RBAC](/protocol/runtime-rbac.md) · [SecureOwnable](/protocol/secure-ownable.md)
* [State machine engine](/protocol/state-machine-engine.md)
* [Releases](/resources/releases.md) · [Changelog](/resources/changelog.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=<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.