Digital Asset Infrastructure for Banks and Credit Institutions

Less than most bank boards assume, and the details are specific. For trading and custody, MiCA Article 60 lets a credit institution notify its regulator at least 40 working days before providing crypto-asset services; the authority checks within 20 working days that the notification is complete (Article 60(8)), and the text sets no approval decision, though ESMA Q&A 2088 says the notification must still fit national banking rules.

Staking is not a listed crypto-asset service, but a Commission answer published by ESMA as Q&A 2067 (20 June 2024) treats staking-as-a-service as ancillary to custody, so custody obligations follow it, and Article 75(8) keeps the institution liable for client crypto-asset losses attributable to it. The lending itself sits outside MiCA scope as the rules stand in 2026 (Recital 94); MiCA gives no passport for it, so the loan runs on the bank's existing credit permissions under each country's credit and consumer-protection rules.

And a euro e-money token can be put in the product by contracting a licensed issuer, though distributing and custodying a third-party EMT is itself a crypto-asset service, and Article 50 bars passing any holding-linked yield to the client. On top of all of it sit DORA and the recast Transfer of Funds Regulation.

The regulation decides which products may exist. What it does not supply is the operational half: consent flows, per-customer records, segregation, and evidence.

We build the engineered layer, and we operate it after launch. For in-app crypto trading and custody, crypto-as-a-service integration connects the rail a bank chooses, or its own custody stack, to the app and the core banking system.

Where a bank's counterparties settle on Canton, Canton Network development covers the Daml applications, validator nodes and links to EVM chains. Where a bank needs transactions hidden from the public but open to its supervisor, our onchain privacy guide compares who holds the disclosure key on Canton, private ledgers, FHE tokens and shielded pools.

For custody, Safe multisig deployment and Fireblocks integration put key governance under policies a risk committee approves; we deployed Safe on 120+ EVM networks, where it secures $2B+. For the compliance chain, compliance integration wires KYC, screening, and Travel Rule data flows into the bank's existing stack.

For staking, we run validator infrastructure and build the per-customer reward attribution the rented stack does not produce: operators report per validator, while the bank's statements and tax reporting need rewards attributed per customer in its own core. For credit against crypto collateral, white-label lending provides the collateral marking and liquidation machinery on a hardened base. Proof-of-reserve infrastructure publishes reserve balances continuously, oracle integration prices collateral on manipulation-resistant feeds, and managed on-chain operations keeps the whole stack watched 24/7.

For the bank's own money on chain, a tokenized deposits platform issues a deposit token that is minted and burned against the core ledger. Before any of it faces customers, smart-contract audit hardens what will hold client assets.

Our blueprint library documents digital-asset architectures already running at regulated institutions: the regime that permits each one, named institutions operating it, and which layers a bank owns, rents, or has us build. Six are drawn for banks: