Skip to main content
ChainGuard

Custody, liquidity & core banking

Continuity governance around institutional custody.

ChainGuard governs key-holder lifecycle, quorum policy, recovery ceremonies and audit evidence around external MPC, multisig and HSM systems. It does not store or reconstruct private keys.

Continuity architecture

Govern the people, policy and evidence around cryptographic systems.

Cryptographic shares remain inside the external custody provider, HSM or approved offline process. ChainGuard controls the institutional workflow around them.

Boundary

What the control layer does, and what it never does.

The distinction matters commercially and operationally. ChainGuard is not competing with your custodian, your liquidity venue or your core banking system. It governs what reaches them.

ChainGuard doesChainGuard does not
  • Governs key-holder lifecycle, quorum policies, rotations and recovery evidence around external custodyStores, exports or reconstructs a private key, seed phrase, MPC share or HSM master key
  • Validates readiness before an instruction is issuedHolds private keys or custodies assets
  • Records approvals and can submit an externally signed Bitcoin transaction when all gates permit itGenerates, stores or uses Bitcoin private keys to sign
  • Evidences the decision behind an instructionExecutes currency conversion
  • Reconciles the outcome back against the recordActs as the authoritative account balance

Integration workflow

From decision to reconciled execution.

Five steps, with the hand-off to the provider deliberately isolated as its own step.

  1. A decision is reached

    For a deposit, a withdrawal or a wallet registration, under the policy version in force.

  2. Operational readiness is checked

    Against custody, liquidity and core banking state: is the institution actually in a position to act?

  3. Approval is recorded

    Through maker/checker where the action requires a second, independent authoriser.

  4. The instruction is handed over

    To the relevant provider. For Bitcoin, an institution-controlled Core wallet can prepare a PSBT for external signing and broadcast the returned signed transaction. Execution remains separately gated and is never triggered by the compliance outcome alone.

  5. The outcome is reconciled

    Back against the ledger, and the reconciliation itself becomes part of the evidence record.

This describes the integration architecture. Production execution against a given provider is enabled per deployment, not by default. The Bitcoin path keeps signing outside ChainGuard and requires independent master, production, PSBT and broadcast gates.

Custody continuity

Long-term governance around external MPC, multisig and HSM systems.

ChainGuard governs custody continuity, key-holder lifecycle, quorum policies, recovery ceremonies and audit evidence around external MPC, multisig and HSM systems.

  1. Continuity is assessed

    ChainGuard deterministically compares the approved quorum policy with active participants, assignments, organizational and geographic diversity, attestations, rotations, recovery drills and provider observations.

  2. Lifecycle changes are governed

    A departure, participant replacement, share refresh, quorum change or provider migration becomes a maker/checker ceremony with MFA step-up and an auditable provider reference.

  3. Recovery is proven

    Non-destructive recovery drills verify governance readiness and external-provider access without exporting cryptographic shares or moving production funds.

Private deployment review

Discuss your custody, liquidity and core banking integration.

Map ChainGuard to your institution’s transaction, policy and evidence workflows.

Request a private demonstrationDiscuss your integration