~/squad-b/institutional-dlt

Institutional digital-asset systems your financial clients can approve, integrate and operate.

Squad B helps tokenization platforms, fintechs and digital-asset infrastructure providers build production-ready tokenization, DLT integration and wallet systems. Senior engineers with hands-on delivery experience on programmes for tier-1 banks and market infrastructures.

// who we work with

For teams whose customers are financial institutions

Our clients sell to banks, asset managers and market infrastructures. We help them ship systems that hold up in that customer's architecture and security review.

tokenization & RWA platforms

Issue and manage real-world assets

A token lifecycle that holds up to institutional scrutiny: permissions, transfer rules, corporate actions and clean integration with custody and back office.

fintechs & infrastructure vendors

Get through your client's technical review

Your product works. Now a financial institution wants to run it: environments, key management, event delivery and documentation have to meet its standards.

software integrators

Add specialist DLT delivery

You won a project with a blockchain component. We deliver that component — Kaleido, Besu, FireFly or public EVM — inside your delivery process.

// services

What we build

Defined subsystems with clear deliverables — not open-ended staffing.

SVC-01

Tokenization & RWA engineering

The smart-contract and service layer behind issuing, managing and transferring tokenized assets.

  • Token standards and lifecycle: mint, burn, transfer rules, freezes, corporate actions
  • Role-based permissions and allow-lists for regulated assets
  • Tokenized collateral, on-chain lending and cross-chain transfers
  • APIs and indexers that connect contracts to your backend

Solidity · Foundry · Morpho · Chainlink CCIP · The Graph

SVC-02

Enterprise DLT integration

Permissioned networks and middleware set up for real environments and wired into existing systems.

  • Kaleido, Hyperledger Besu (QBFT) and FireFly design and provisioning
  • Infrastructure as code with multi-environment CI/CD
  • Event delivery from chain to Kafka, APIs and back-office systems
  • Asset, wallet and workflow services configured for your use case

Kaleido · Besu · FireFly · Kafka · Terraform

SVC-03

Wallets, custody & key management

How keys are held, how transactions are approved, and how users interact — without seed phrases.

  • Remote-signing integration and governed secret management
  • Approval policies and transaction workflows
  • Smart accounts: ERC-4337, ERC-7579 and EIP-7702
  • Passkey authentication, sponsored and batched transactions

ERC-4337 · ERC-7579 · WebAuthn · Rust

SVC-04

Dedicated senior squad

A small senior blockchain team embedded in your roadmap and accountable for a defined area.

  • Works in your repositories, environments and rituals
  • Owns a defined subsystem end to end
  • Documentation, runbooks and handover built in
  • Direct senior involvement on every engagement

monthly · scoped by area of ownership

Oleh Rubanik, founder of Squad B

// senior-led, not handed off

Oleh Rubanik, founder

DLT architect and engineer with six years in production blockchain. Hands-on delivery on programmes for a tier-1 international bank, a European market infrastructure and an Asian securities firm, as well as tokenization, wallet and protocol products. Every Squad B engagement has his direct involvement.

  • Kaleido, Hyperledger Besu and FireFly in bank and market-infrastructure programmes
  • Solidity, Rust and EVM internals; ERC-4337, ERC-7579, EIP-7702
  • Uniswap Hook Incubator participant; Blockchain UA hackathon winner
  • Based in Warsaw, working with teams across Europe and Asia

// selected delivery experience

Experience of the Squad B core team

The examples below reflect work delivered by Squad B's founder and core engineers in current and prior engagements. Client names are withheld; the engagement context and our role are stated for each case.

CASE-01tier-1 international bankprior individual engagement

Multi-currency stablecoin tokenization on a private network

  1. Ops & approvals
  2. Workflow engine
  3. Asset & wallet managers
  4. FireFly
  5. Besu QBFT on Kaleido

scope owned

  • Architected and provisioned a private Hyperledger Besu network with QBFT consensus on Kaleido, with secure API orchestration.
  • Designed a multi-module Terraform codebase for the network, FireFly middleware and digital-asset layers, with per-environment toggles.
  • Deployed the digital-asset services: asset manager, wallet manager, ERC-20 indexer and workflow engine.
  • Set up governed multi-environment CI/CD with templated pipelines and secrets in managed variable groups.
our role
architecture, provisioning, delivery
network
Besu · QBFT · Kaleido
middleware
Hyperledger FireFly
iac
Terraform
ci/cd
Azure DevOps

outcomeStablecoin tokenization flows delivered for 20+ currencies.

open full spec →
CASE-02european market infrastructurecurrent individual engagement

Event delivery from tokenized securities to core systems

  1. Security token contract
  2. Besu node
  3. FireFly event stream
  4. Producer API
  5. Kafka topics
  6. Downstream systems

scope owned

  • Solution architecture for delivering on-chain securities lifecycle events into enterprise messaging.
  • Architecture decision record for chain-to-core event delivery, presented to the programme team.
  • Subscription design: acknowledgements, a retry ladder and mutual TLS between platform and consumers.
  • Configuration of event schemas and contract ABIs per asset type.
  • Code review of the integration service, including platform interaction and role-based access.
our role
solution architecture, design review
network
Besu · Kaleido
events
FireFly · webhooks
messaging
Kafka
security
mTLS · RBAC
CASE-03asian investment & securities firmcurrent engagement via a delivery partner

Tokenized RWA as collateral in on-chain lending

  1. RWA token
  2. Chainlink CCIP
  3. Destination chain
  4. Morpho lending market

scope owned

  • Smart-contract integration that lets tokenized real-world assets serve as collateral in Morpho lending markets.
  • Cross-chain movement of tokenized assets using Chainlink CCIP.
  • Delivered within a dedicated engineering team for the firm's RWA programme.
our role
smart-contract engineering
contracts
Solidity
lending
Morpho
interop
Chainlink CCIP
CASE-04wallet infrastructure startupprior engagement · product team

Modular smart-account wallet with passkeys

  1. Mobile app · passkey
  2. Rust backend
  3. Rust 4337 bundler
  4. EntryPoint
  5. ERC-7579 smart account

scope owned

  • Modular smart-account architecture compliant with ERC-7579 and ERC-4337.
  • P-256 passkey validator on the native RIP-7212 precompile, with no external cryptography libraries.
  • EIP-7702 integration for native, sponsored and batched execution.
  • Custom ERC-4337 bundler and real-time GraphQL event listener in Rust.
  • The full backend from scratch — APIs, wallet orchestration, private subgraph and AWS deployment.
our role
team lead, architecture, backend
standards
4337 · 7579 · 7702
auth
WebAuthn · RIP-7212
backend
Rust · Node.js / TS
infra
AWS · subgraph

outcomeWallet stack tested end to end on iOS and Android, with test infrastructure for UserOperations, 7702 flows and WebAuthn signatures.

// reference architecture

The layers we work on

Most delays happen between the layers, not inside them. We take responsibility for the joins.

L5 · business systemsCore banking, settlement, reporting
L4 · integrationEvent delivery, Kafka, APIs, reconciliation
L3 · digital-asset servicesAsset manager, wallets, workflows, indexers
L3 · custody & keysRemote signing, policies, approvals
L2 · middleware & contractsFireFly, token standards, smart accounts
L1 · networksBesu QBFT on Kaleido · Ethereum & EVM L2s
L0 · platformTerraform, CI/CD, AWS / Azure, observability

Highlighted layers: where we deliver directly. Grey: layers we integrate with.

// engineering standards

Engineered for institutional review and operation

We apply these practices where they are in scope and document the evidence your client's architecture and security teams need. Certification and vendor approval remain separate processes.

STD-01

Environments as code

Networks, middleware and services defined in code, identical from dev to production.

STD-02

Fail-closed by default

When state is uncertain, money does not move. Every automated action has a safe stop.

STD-03

Reliable event delivery

Acknowledgements, retry ladders and idempotent consumers between chain and core systems.

STD-04

Keys never in code

Remote signing, governed secret stores and approval policies from the first environment.

STD-05

Observable in production

Metrics, alerts and runbooks are part of the scope, so the operations team owns the system on day one.

STD-06

Decisions on record

Architecture decision records and design documents your reviewers can follow.

// delivery process

Alongside your teams and integrators

  1. 01 · discover

    30-minute technical call

    Current state, constraints, who must approve. Free, NDA on request.

  2. 02 · scope

    Fixed scope and price

    Deliverables, milestones and acceptance criteria agreed up front.

  3. 03 · build

    Milestone delivery

    Working increments in your environments, reviewed against your standards.

  4. 04 · hand over

    Runbooks and training

    Your engineers operate and extend the system without us.

Building something your financial clients will have to approve?

Start with a 30-minute technical call. No commitment, NDA on request.

Request a technical call

// faq

Common questions

Who are your typical clients?

Tokenization and RWA platforms, fintechs and digital-asset infrastructure providers whose customers are banks, asset managers and market infrastructures — and software integrators that need a DLT specialist on a project.

Where does your institutional experience come from?

Our engineers have hands-on delivery experience on programmes for a tier-1 international bank, a European market infrastructure and an Asian securities firm. Those were individual or partner engagements, not Squad B contracts, and each case on this site states its context.

Do you work directly with banks?

We work with the companies that serve financial institutions, and alongside banks' approved integrators where their rules allow. Direct vendor relationships with banks follow each bank's own approval process.

Permissioned network or public chain?

Whichever fits the asset and the customer. We work with Kaleido, Hyperledger Besu and FireFly as well as Ethereum and EVM L2s, and will tell you plainly when a simpler design is the better choice.

How do you handle security and confidentiality?

NDAs before any detail is shared, multi-factor authentication and least-privilege access, work inside your repositories and environments where possible, and no keys or secrets in code.

How does a project start?

With a free 30-minute call. If there is a fit, we propose an Institutional Readiness Sprint or a fixed-scope delivery with milestones, deliverables and a price agreed up front.