Flying Tulip IncDiscuss a project

Onchain financial infrastructure

Engineering the infrastructure for onchain prime brokerage.

Flying Tulip Inc designs and develops software for institutions building digital-asset credit, collateral, execution, settlement, and risk products.

Discuss a project Explore capabilities

For fintechs digital-asset institutions protocols asset managers exchanges

System map Integrated stack
01
Credit & collateralAssets · financing · accounting
02
Margin & riskExposure · health · liquidation
03
Execution & liquidityRFQ · routing · price inputs
04
Settlement & lifecycleFunding · closeout · reporting
Smart contractsAPIsOperator tooling

01 / Capabilities

One engineering partner across the prime brokerage stack.

Onchain prime brokerage brings together financing, collateral, execution, settlement, and risk management. We translate those interconnected requirements into production software—from smart contracts and pricing logic to APIs, operator tooling, and protocol integrations.

We can work alongside internal product, risk, and engineering teams or take responsibility for a clearly defined build.

01

Credit & collateral

Margin lending, secured borrowing, shared collateral frameworks, interest models, position accounting, and asset onboarding.

  • Lending
  • Collateral
  • Accounting
02

Margin & risk

Cross-collateral and portfolio-margin systems, exposure limits, health calculations, liquidation design, and scenario testing.

  • Portfolio margin
  • Limits
  • Liquidation
03

Execution & liquidity

RFQ workflows, quote signing, order routing, venue integrations, oracle inputs, and inventory controls.

  • RFQ
  • Routing
  • Pricing
04

Settlement & lifecycle

Funding, carry, fees, P&L, closeouts, reconciliation, and reporting workflows across the full position lifecycle.

  • Settlement
  • Lifecycle
  • Reporting
05

Protocol & platform engineering

Smart contracts, backend services, APIs, indexers, SDKs, operator consoles, and client-facing applications.

  • Contracts
  • APIs
  • Applications
06

Security & delivery

Test strategy, invariants, simulations, access and upgrade controls, deployment tooling, audit preparation, and remediation support.

  • Testing
  • Controls
  • Operations

02 / System coverage

The complete system, clearly drawn.

Prime brokerage products work only when markets, capital, controls, and infrastructure share one coherent design.

01

Markets

  • RFQ & order routing
  • AMM & CLOB
  • Perpetuals & TRS
  • Liquidity integration
02

Capital

  • Lending & credit
  • Cross-collateral
  • Leverage
  • Liquidation
03

Controls

  • Margin & exposure
  • Pricing & oracles
  • Limits & permissions
  • Monitoring
04

Infrastructure

  • Accounting
  • Settlement
  • APIs & SDKs
  • Operator systems

Engineering library

Inside the systems we build.

Architecture, tradeoffs, and failure modes across the prime brokerage stack. Technical resources for product, risk, and engineering teams.

Original study: when reducing a hedge increases margin →

Explore the library ↗

03 / Engagements

Engage us where the gap is.

From a discrete technical mandate to an embedded product team.

Institutional architecture

From tokenized assets to functioning markets.

Explore the post-issuance liquidity, partner-instance, and settlement architecture behind the institutional work.

Deployment architecture and responsibilities

Cover of Institutional architecture brief

PDF · 12 pages · August 2026

Institutional architecture brief

A 12-page introduction to post-issuance liquidity, collateral, risk and settlement infrastructure for tokenized markets.

  • A proposed liquidity workflow connects approved assets, executable quotes, immediate settlement, issuer redemption and facility reconciliation.
  • Collateral treatment considers realizable depth, settlement time, concentration and custody dependencies alongside reference prices.
  • A staged engagement moves from a scoped diagnostic through controlled validation to a separately approved deployment and operating model.
  • Responsibility boundaries distinguish architecture, contracts and integration support from the client's custody decisions and regulated activities.
Read the brief (PDF)

Discussion architecture. The source PDF preserves its dated market context and illustrative workflow; it does not establish current deployment availability or financial-service provision by FT Inc.

Cover of Partner deployment and instance brief

PDF · 3 pages · 20 August 2026

Partner deployment and instance brief

A three-page architecture proposal for a configurable account and risk layer connecting credit, execution, derivatives and carry settlement.

  • A common account and risk engine can coordinate approved cross-collateral exposures while retaining isolated markets or subaccounts.
  • Proposed RFQ workflows cover target exposure, unwind and liquidation, with explicit execution policy and fallback paths.
  • Partner controls include asset eligibility, concentration limits, solver permissions, fees, governance and loss policy.
  • A carry-settlement extension tracks an immediate advance through issuer redemption to debt repayment and position closure.
  • The proposed first release uses a small collateral set, one settlement asset, limited solvers, hard caps and tested incident procedures.
Read the brief (PDF)

Discussion architecture. The source PDF includes dated product comparisons and proposed modules; enablement depends on scope, review, liquidity and the operating arrangement.

Cover of Liquidity for settlement-lagged assets

PDF · 1 page · 20 July 2026

Liquidity for settlement-lagged assets

A one-page proposed integration showing how a controlled tokenized asset can support an immediate advance while issuer redemption settles later.

  • The proposed advance is based on expected redemption value less financing carry, risk reserves and fees.
  • The asset remains controlled in an isolated position while the issuer follows its normal redemption process.
  • An issuer adapter must register the request, control the asset, route proceeds and close the obligation without duplicate settlement.
  • Eligibility, permissions, chain conditions, available liquidity, risk limits and settlement timing determine the scope of an integration.
Read the brief (PDF)

Proposed integration concept. The source PDF retains dated, illustrative liquidity and rate figures; these are not current capacity, pricing, return or redemption commitments.

These source briefs describe architecture and proposed workflows. Availability, assets, capital, permissions, and operational responsibilities are established for each engagement. Figures in the original PDFs are dated illustrations, not current liquidity or pricing commitments.

04 / Process

Structured delivery, from specification to launch.

  1. 01

    Define

    Align on users, commercial objectives, assets, operating constraints, and risk requirements.

    Mandate & requirements
  2. 02

    Architect

    Establish system boundaries, specifications, interfaces, security assumptions, and milestones.

    Architecture & specification
  3. 03

    Build

    Deliver in reviewable increments with testing, documentation, and regular technical demonstrations.

    Working production code
  4. 04

    Validate & launch

    Support integration testing, external review, deployment, rollout, and operational handover.

    Hardened handover

05 / Company

Built within Flying Tulip. Available beyond it.

Flying Tulip Inc is the software development arm of the Flying Tulip ecosystem. Its mandate is broader than a single protocol: we work with third parties building their own digital-asset credit, execution, risk, and settlement products.

Engagements can be independent of the Flying Tulip protocol and designed around each client's architecture, venues, custody model, and operating requirements.

Related background: Andre Cronje’s public record and writing on market structure.

Start a technical conversation

Bring your prime brokerage product onchain.

Whether you are designing a new platform or extending an existing stack, we can help define and deliver the software behind it.

Discuss a project