Onchain Operating Stack
for Institutional Asset Management
Three layers of the protocol
Onchain issuance, compliance, and NAV accounting for any real-world asset. Full double-entry bookkeeping — balanced debits and credits on every value movement.
Co-authored ERC-7540 — the async vault standard extending ERC-4626. Epoch-based batching ensures every investor in a batch receives the same price and pro-rata allocation.
One pool deploys to any number of chains in a single action. Cross-chain messages batch automatically. Native DeFi integration: Morpho, Aave, Pendle, Sky.
Hub-and-spoke multichain
Production deployments
Platform strategy
| Self-Build | Supported-Build | Managed-Build (Anemoy) | |
|---|---|---|---|
| Protocol access | ✓ | ✓ | ✓ |
| Onboarding support | — | ✓ | ✓ |
| Legal / regulatory | — | Partial | ✓ Full |
| Full-service build | — | — | ✓ |
| Target | DeFi protocols, developers | Asset managers with tech teams | TradFi institutions |
| Example | BlockTower | — | Apollo · Daylight |
Apollo went kickoff → live in under 3 months — that execution pattern needs to be systematized into a repeatable prospect-to-live framework with defined milestones per tier.
Three tiers require three distinct conversations: technical docs for the self-build developer, compliance framing for the asset manager, full regulatory stack for the TradFi institution.
Apollo, Janus Henderson, and BlockTower are strong proof points — 97% cost savings, under 3 months to live, S&P-rated. These need to be packaged as prospect-facing one-pagers with ROI framing.
The self-build tier needs a clear path from "I want to build on Centrifuge" to first vault deployed: quickstart, chain-specific setup, example repos, and integration reference architecture.
Every prospect needs technical scoping before committing to a tier — defining scope, chain preferences, compliance requirements, and pilot parameters is currently ad hoc and needs a structured function.