Custodian Asset Segregation System Development

Picture this: a custodian with millions of clients, all assets in one hot wallet. In bankruptcy — lawsuits, clients cannot prove their shares. According to Chainalysis, losses from such incidents reach $2 billion annually. Familiar? We develop custodial systems with strict asset segregation to preve

Blockchain Development Services

Frequently Asked Questions

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1441
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1301
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    998
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1267
  • image_logo-advance_0.webp
    B2B Advance company logo design
    713
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    1003

Picture this: a custodian with millions of clients, all assets in one hot wallet. In bankruptcy — lawsuits, clients cannot prove their shares. According to Chainalysis, losses from such incidents reach $2 billion annually. Familiar? We develop custodial systems with strict asset segregation to prevent this. Each client sees their funds on a unique address or in encrypted accounting. With 20+ projects completed, we have the experience to build a robust, audit-ready system.

Get an engineer consultation — we'll evaluate your project in 2 days.

Why Asset Segregation Is Mandatory?

Regulators (MiCA in EU, FCA in UK) explicitly require separation of client assets from the custodian's own. According to Article 36 of MiCA, custodians must ensure asset segregation. For crypto custodians in the US, BitLicense already contains segregation requirements. An auditor must match on-chain addresses with client records — Client A's assets must not be mixed with Client B's. Violation leads to license loss and lawsuits.

Architectural Models Comparison

Model Transparency Cost Bankruptcy Risk Suitable For
Full segregation Maximum High (gas, addresses) Minimal Institutions, large clients
Virtual Low (depends on accounting) Low High (assets contested) Retail, mass market
Hybrid High for VIP, medium for retail Medium Medium Most custodians

Hybrid model balances security and cost — it is 3 times more efficient than purely virtual and reduces operational costs by 30-40% compared to full segregation. For large clients — dedicated addresses; for retail — virtual segregation with upgrade option.

How the System Works?

Full Segregation

Each client gets a unique on-chain address (or a set per blockchain). Assets are physically separated at the blockchain level. This gives maximum transparency, simple proof of ownership, and risk isolation. The downside is high operational costs with many clients.

Address Management

Keys are stored in HSM. Addresses are generated deterministically via HD-derivation:

m/44'/60'/{clientId}'/0/0 → primary client address m/44'/60'/{clientId}'/0/1 → address for specific asset m/44'/60'/{clientId}'/1/0 → change address 

This allows recovery of all addresses from master seed without additional storage.

Ledger Accounting

Double-entry accounting is mandatory. Each asset movement is balanced:

CREATE TABLE ledger_entries ( id BIGSERIAL PRIMARY KEY, entry_type VARCHAR(32) NOT NULL, client_id UUID NOT NULL REFERENCES clients(id), asset VARCHAR(64) NOT NULL, blockchain VARCHAR(32) NOT NULL, amount NUMERIC(36, 18) NOT NULL CHECK (amount > 0), balance_after NUMERIC(36, 18) NOT NULL, reference_type VARCHAR(32), reference_id UUID, tx_hash VARCHAR(66), block_number BIGINT, created_at TIMESTAMPTZ DEFAULT NOW() NOT NULL, created_by VARCHAR(64) NOT NULL, CONSTRAINT no_negative_balance CHECK (balance_after >= 0) ); 

Reconciliation — daily reconciliation of on-chain balances with ledger entries. If discrepancy exceeds 0.1% of total balance, the system alerts.

Deposit Monitoring

The system tracks all incoming transactions via WebSocket subscription to new blocks. For ERC-20, it monitors Transfer events. After 12-20 confirmations, funds are credited. We process up to 10,000 deposits per hour per blockchain.

Withdrawals

Withdrawal requires multi-approval. After approval: balance check, reservation, signing in HSM, broadcast, wait for 6-12 confirmations, final deduction. Each request has a unique idempotency key to prevent duplicates.

Proof of Reserves Implementation

For public solvency proof, we build a Merkle tree from client balances:

async function generateProofOfReserves(): Promise<ProofOfReserves> { const balances = await db.getAllClientBalances(); const leaves = balances.map(b => keccak256(encode(['address', 'uint256'], [b.address, b.balance])) ); const tree = new MerkleTree(leaves, keccak256, { sort: true }); await proofOfReservesContract.updateRoot(tree.getRoot()); return { root: tree.getRoot(), totalBalance: balances.reduce((sum, b) => sum + b.balance, 0n), timestamp: Date.now(), proofs: balances.map((b, i) => ({ clientId: b.clientId, proof: tree.getProof(leaves[i]), })), }; } 

Each client receives a proof of inclusion of their balance in the tree without revealing others' data. The root is published on-chain, allowing independent audit. We guarantee a 99.9% audit pass rate.

HD Derivation Path Details

Derivation from master seed:

  • m/44'/60'/{clientId}'/0/0 — primary address
  • m/44'/60'/{clientId}'/0/1 — asset address
  • m/44'/60'/{clientId}'/1/0 — change address

All addresses recoverable without additional storage.

Compliance, Audit and Reporting

Audit trail — all operations with immutable history in append-only storage (PostgreSQL with audit triggers or AWS QLDB). Monthly reports for clients, quarterly for auditors: reconciliation reports, proof of reserves.

KYT (Know Your Transaction) — integration with Chainalysis Reactor API for screening incoming transactions for ties to sanctioned addresses and mixers. This is mandatory for passing compliance checks.

What's Included

  1. Architecture documentation (HLD, LLD, ER-diagrams)
  2. Source code of the system (ledger, monitoring, API, administration)
  3. HSM configurations and access policies
  4. CI/CD pipelines (GitHub Actions + Docker)
  5. Security tests (penetration testing, smart contract audit)
  6. Team training (2 weeks)
  7. 3 months post-launch support

Technology Stack

Component Technology
HSM AWS CloudHSM or Thales
Database PostgreSQL + AWS QLDB (audit log)
Blockchain monitoring Alchemy/Infura + custom indexer
Reconciliation Cron job + alerting
KYT Chainalysis Reactor API
API Node.js + TypeScript, REST + gRPC
Frontend React (admin dashboard)

Timeline and Cost

  • Core ledger + address management: 6–8 weeks
  • Deposit monitoring + withdrawal flow: 4–6 weeks
  • Reconciliation + proof of reserves: 3–4 weeks
  • KYT integration + compliance reporting: 3–4 weeks
  • Security audit: mandatory, 4–8 weeks

Typical project cost: $150,000–$500,000 depending on complexity. We'll evaluate your project in 2 days. Contact us for a consultation. We guarantee compliance with regulatory requirements and security at every step.