Skip to main content
BXOHow it works

One controlled path from legal terms to recorded ownership.

BlockXOne coordinates the primary issuance lifecycle as a sequence of accountable decisions. The platform keeps the instrument, approvals, investor access, settlement evidence, network execution, and ownership record connected throughout the process.

An editorial still life of documents, approval materials, structured glass forms, and a bound register representing the controlled issuance sequence
The control pathEach material decision leaves evidence for the next role. Issuance is the final result of the sequence, not the starting point.

Operating integrity

Control is part of the sequence.

  • 01Every material action is attributed to an authenticated role.
  • 02Preparation, approval, financial control, and execution remain distinct decisions.
  • 03Business records and network evidence stay connected to the same issuance journey.

Issuance sequence

Eight stages. One accountable record.

Each stage answers three practical questions: what enters the control, who decides whether it can continue, and what evidence remains when that decision is complete.

  1. 01

    Stage 01

    Model the instrument

    Translate the legal and economic structure into the operating record that every later action references.

    Input
    Legal entity, asset structure, rights, economics, supply controls, target network, and role policy.
    Decision
    The preparation team confirms that the instrument record is complete enough to enter approval.
    Evidence output
    A versioned instrument record with a defined owner, terms, controls, and requested network.
  2. 02

    Stage 02

    Approve terms and hash

    Fix the approved terms to a specific document version so an altered file cannot silently continue through the workflow.

    Input
    The prepared instrument record, supporting terms, document version, and approval request.
    Decision
    An authorised approver accepts or rejects the exact terms presented for review.
    Evidence output
    Approval history tied to the approved document hash and the people responsible for the decision.
  3. 03

    Stage 03

    Establish the financial profile

    Record the commercial model that explains how the offering is expected to operate before investors are admitted.

    Input
    Capital objective, price, denomination, subscription parameters, fees, and relevant financial assumptions.
    Decision
    The operator confirms that the commercial profile agrees with the approved instrument terms.
    Evidence output
    A financial profile linked to the instrument and available to the following control checks.
  4. 04

    Stage 04

    Confirm issuance readiness

    Bring the legal, financial, operational, and network requirements into one review before distribution begins.

    Input
    Approved terms, financial profile, responsible roles, network configuration, and outstanding requirements.
    Decision
    The assigned reviewer records whether the instrument is ready to accept subscriptions.
    Evidence output
    A readiness decision with the checks completed, open conditions, actor, and time of review.
  5. 05

    Stage 05

    Qualify the investor and wallet

    Connect the eligible investor, their organisation context, and the wallet intended to receive the position.

    Input
    Investor identity, eligibility record, organisation, wallet address, and wallet ownership evidence.
    Decision
    The responsible role approves or rejects investor access and the linked destination wallet.
    Evidence output
    An attributed qualification decision and an approved investor to wallet relationship.
  6. 06

    Stage 06

    Approve the subscription

    Capture the requested commitment as an exact obligation and review the allocation before it can progress.

    Input
    Qualified investor, approved wallet, instrument, quantity, price, amount, and subscription request.
    Decision
    The offering team accepts, adjusts, or rejects the requested allocation within the approved terms.
    Evidence output
    A subscription record with exact values, status history, allocation, and accountable decision maker.
  7. 07

    Stage 07

    Reconcile settlement evidence

    Match the approved obligation to the evidence received before any issuance instruction is authorised.

    Input
    Approved subscription, expected amount, settlement reference, received amount, and supporting evidence.
    Decision
    The financial control role determines whether the obligation and settlement evidence reconcile.
    Evidence output
    A reconciliation result connected to the subscription, evidence reference, and approval history.
  8. 08

    Stage 08

    Issue, verify, and finalise

    Execute the authorised instruction, observe the network result, and connect it back to the ownership records.

    Input
    Reconciled subscription, approved wallet, authorised quantity, network, contract, and issuance instruction.
    Decision
    The platform finalises only after the execution result can be matched to the authorised instruction.
    Evidence output
    Transaction receipt, contract reference, finality state, token supply, investor position, and legal register record.

Exception control

What stops the workflow.

Progress is not the same as completion. A control remains open until its required decision and evidence agree.

  1. 01

    The terms no longer match

    A missing approval, changed document, or hash mismatch sends the instrument back for review before later actions continue.

  2. 02

    Readiness is incomplete

    Open legal, financial, operational, or network conditions remain visible and prevent the workflow from being treated as ready.

  3. 03

    Investor access is unresolved

    An unqualified investor, rejected eligibility decision, or unapproved wallet cannot receive an allocation or issuance.

  4. 04

    The obligation does not reconcile

    A subscription, expected amount, received amount, or settlement reference that does not agree remains outside issuance.

  5. 05

    Execution cannot be proven

    A failed transaction or unmatched network result cannot be promoted into a final investor position or legal register record.

BlockXOne

Digital ownership infrastructure for private markets.

Structure instruments, qualify investors, control settlement, issue tokens and preserve ownership evidence in one accountable platform.

BXOMulti-asset tokenisation
BlockXOnePrivate-market infrastructure, built for accountable operation.