BXOOperators

Coordinate every accountable role without losing the record.

BlockXOne gives issuer, compliance, finance, transfer, and tokenisation teams focused work queues connected to the same instrument, investor, subscription, and chain lifecycle.

Institutional operators reviewing legal records and a structured asset model — Shared truth. Separate authority.

Operating model

Specialist work, coordinated as one lifecycle.

Offering Manager and Issuer Fund Manager

Structure and approve

Create the instrument, prepare typed terms, record a separate approval, define offering economics, and activate the financial profile before subscriptions open.

Instrument terms version
Terms digest and approval
Financial profile and readiness

Compliance Officer

Qualify and admit

Review submitted KYC cases and pending wallets. Wallet approval remains separate from same-chain whitelist execution, preserving a visible control boundary.

KYC decision
Wallet address and chain
Wallet approval state

Transfer Agent, Treasury Operator, and Financial Controller

Allocate and reconcile

Approve subscriptions, reserve exact units, issue payment instructions, run evidence reconciliation, and record an independent reconciliation approval.

Allocation range
Payment instruction
Provider, statement, and ledger digests

Tokenisation Agent and authorised checker

Whitelist and issue

Execute whitelist work, prepare controlled chain operations, obtain required approvals, coordinate signing, and project finalized receipt evidence into the ownership record.

Operation payload digest
Approval policy and signer
Receipt, finality, event, and register evidence

Role directory

Clear ownership for each control point.

A role defines the available work, while organisation membership keeps that authority in the relevant issuer or platform context.

Offering Manager: Instrument preparation, offering creation, financial profile preparation, and offering publication.
Issuer Fund Manager: Issuer-side offering control, subscription approval, cap-table visibility, and issuer actions.
Compliance Officer: KYC case decisions, wallet approvals, compliance review, and compliance-module authority.
Transfer Agent: Subscription approval, cap-table visibility, identity operations, and controlled transfer functions.
Treasury Operator: Runs provider, statement, and ledger reconciliation work for configured consideration rails.
Financial Controller: Approves financial profiles and independently reviews reconciliation results.
Tokenisation Agent: Deployment, whitelist, mint, burn, identity registration, and token compliance operations.

Operational controls

Controls are part of the workflow, not a report added later.

Separate preparation and approval

Instrument terms, financial profiles, subscriptions, reconciliations, and governed chain actions carry explicit maker and checker evidence where required.

Permission-backed queues

Operator work is discovered through permission-aware queues for offerings, KYC, wallets, subscriptions, settlement, whitelist, mint, and chain approvals.

Exact-value economics

Asset units, consideration amounts, price inputs, allocation capacity, and balances use canonical decimal or base-unit representations.

Retry-safe operations

Controlled subscriptions and chain writes bind retries to idempotency keys so a repeated request can be recognized rather than silently duplicated.

State model

A shared language for progress.

01
Draft instrument
02
Active approved terms
03
Offering ready
04
Subscription requested
05
Funding pending
06
Reconciled
07
Chain operation finalized
08
Position registered

Role-separated access

Each team sees the work it is authorised to perform.

Authenticated organisation context, permission-aware navigation, and scoped queues keep preparation, approval, compliance, reconciliation, and execution responsibilities distinct.