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 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

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.

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

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.

We develop crypto wallets turnkey — from custodial solutions for fintech to smart contract accounts on EIP-4337. 5+ years in blockchain development, 40+ projects implemented. Let's examine which architecture to choose for your task and why MPC or Account Abstraction solve the private key problem that MetaMask and classic HD wallets could not close.

Why are classic wallets dangerous for business?

A seed phrase in a browser extension is the only way to restore access. For retail users, this is a barrier to entry (lost phrase = lost money). For corporate treasuries, it is incompatible with compliance (KYC/AML, role model, multisignature). Any single key leak compromises all funds. These risks are built into the architecture, not poor UX.

We eliminate them at the protocol level: MPC wallets (key never fully assembled), smart contract wallets (authorization logic in code), hardware HSM for institutional storage. Details below.

What is the real difference between custodial and non-custodial?

Custodial — the provider stores the private key. User authenticates via email/password/OAuth. Recovery is trivial, KYC/AML built-in. For centralized financial applications, often the only regulatory acceptable option. Risk: single point of failure (e.g., Bitfinex hack — $72M, FTX — $600M+ client funds).

Non-custodial — keys are with the user. Provider has no access to funds. Storage responsibility falls on the user. For 99% of people, this model is unworkable without additional protection — hence MPC.

MPC wallets: the key that doesn't exist

Multi-Party Computation (MPC) is a cryptographic protocol that allows multiple parties to jointly sign a transaction without revealing their partial secrets. The private key never exists in its assembled form.

Standard scheme: 2-of-3 MPC between user (share on device), provider server, and backup cloud storage. Transaction is signed by any two of three parties. Lost phone — recovery via server + cloud. Server compromised — attacker holds only one share, signing impossible.

TSS (Threshold Signature Scheme) is a concrete implementation of MPC for ECDSA/EdDSA. Algorithms: GG18, GG20, CGGMP21 (the latter is faster and has better security proofs). Libraries: tss-lib (Go, from Binance), multi-party-sig (Go, from Coinbase), ZenGo-X/multi-party-ecdsa (Rust).

MPC requires no on-chain changes — to the blockchain, the signature looks like a normal single-key signature. This saves gas and keeps the key management scheme confidential (not published in chain) — unlike multisig.

Account Abstraction (EIP-4337): smart contract as wallet

EIP-4337 completely changes the model: instead of EOA (Externally Owned Account), a smart contract Account is used. Authorization logic is in contract code, not in protocol cryptography. This opens up arbitrary signing logic, social recovery, session keys, sponsored transactions, and batch operations.

How the EIP-4337 stack works:

User → UserOperation → Bundler → EntryPoint contract → Account contract
                                          ↑
                                    Paymaster (optional, pays gas)

UserOperation — a new type of object (not an L1 transaction). Bundler collects UserOps from an alternative mempool, packs them into one transaction, and sends to EntryPoint. EntryPoint calls validateUserOp on the Account contract — Account decides if the signature is valid.

Practical capabilities:

Social recovery. The contract stores a list of guardians (other addresses or a service). Lost key — guardians vote for replacement. Argent has used this scheme since 2020.

Session keys. A temporary key with limited rights: interaction only with a specific contract, until a certain date, up to a certain amount. For GameFi and dApps — user does not sign every micro-transaction.

Paymaster. A third-party contract pays gas for the user. Onboarding pattern: user does not hold ETH, gas is sponsored by dApp or taken from ERC-20 tokens.

Implementations: Safe{Core} Protocol, Biconomy SDK (Stackup), ZeroDev (Kernel), Alchemy (Rundler bundler). EntryPoint v0.6/v0.7 is deployed and active on Ethereum mainnet, Polygon, Arbitrum, Optimism. We guarantee compatibility with the latest contract versions.

What is a Hardware Security Module for corporate wallets?

For treasuries and institutional storage: HSM (Hardware Security Module). The key is generated and never leaves the secure chip. Signing happens inside the HSM. Hardware attestation is supported. Solutions used: AWS CloudHSM, Azure Dedicated HSM, Thales Luna, YubiHSM 2 (for small volumes). Integration via PKCS#11 or cloud-specific API.

A combination of HSM + MPC is optimal for institutional use: key shares are stored in HSMs on different servers/jurisdictions, signing via TSS. This ensures compliance with regulatory requirements (e.g., for crypto custodians).

Integration with dApps: WalletConnect and standards

Any wallet must be able to interact with dApps. Standard: WalletConnect v2 (Sign API): QR code or deep link, peer-to-peer encrypted channel via relay server. For browser extensions: EIP-1193 (Ethereum Provider API).

On the frontend, we use wagmi + viem — one interface for MetaMask, WalletConnect, Coinbase Wallet, injected providers. For Account Abstraction: EIP-5792 (wallet capabilities) and EIP-7677 (paymaster service).

Development process

1. Threat model — who is the user (B2C, B2B, institutional), what operations, what is the acceptable risk model. Architecture depends on this.
2. Selection and design of key storage scheme — MPC, HSM, multisig, or a combination.
3. Development of Account contract (if EIP-4337) or integration of MPC library.
4. Backend — MPC coordination, session management, paymaster service (if needed).
5. Mobile/browser application — UI with WalletConnect integration, biometrics, QR.
6. Integration with dApps — EIP-1193, WalletConnect v2.
7. Audit of contracts and cryptographic implementations — mandatory step. MPC libraries have known vulnerabilities (GG18 susceptible to attack with malicious participant without abort protocol). We use libraries with up-to-date security reviews (CGGMP21). Experience passing audits with Certik, Hacken, Trail of Bits — we have certificates.

What is included in the work (deliverables)

• Source code of smart contracts (Solidity/Rust) with documentation
• Backend MPC coordination service (Go or Rust) with API
• Mobile application (iOS/Android) or browser extension
• Integration with WalletConnect, Ledger/Trezor (if required)
• Preparation for security audit (vulnerability report)
• Administrator and user documentation
• Access to repository, CI/CD, monitoring (Tenderly, Etherscan API)
• Training of your team (2-3 sessions)
• Post-launch support — 1 month

Timeline and cost

Cost is calculated individually for your project. We will estimate within one day — contact us by email or Telegram. We provide a guarantee on code and timeline.

Typical mistakes in crypto wallet development (and how to avoid them)

• Using outdated MPC libraries — GG18 without abort protocol. Choose CGGMP21 or tss-lib with up-to-date audit reports.
• Tight coupling to a single blockchain — not abstracting for L2/sidechains. Use viem/wagmi for cross-chain.
• Ignoring MEV attacks — when using multisig without timelocks. Add tx simulation (Tenderly) and sandwiching protection.
• Lack of fallback recovery mechanism — for Account Abstraction, not setting up social recovery. Include from the first release.

We eliminate these pitfalls at the design stage — for each project, we create a threat model and security checklist.

Need a reliable wallet with no compromises? Get a consultation from our architect — we will analyze your task and propose an architecture with a precise estimate. Leave a request — we will respond within a day.