EcosystemEducation

Building multichain financial products with Centrifuge's VDK and LayerZero

By LayerZeroNov 20, 20266 min read
LayerZero and Centrifuge logos

The short answer

  • Centrifuge's Vault Development Kit (VDK) gives builders one configurable vault for tokenized investment products, with multichain distribution built in.
  • This post explains how the VDK works and where LayerZero fits in its cross-chain design.

In November 2026, Centrifuge announced its Vault Development Kit (VDK). The VDK is built on a simple principle: builders of tokenized investment products like tokenized treasury funds, or private credit funds should control the features that make their product different, and rely on shared infrastructure for everything else.

One critical component of these products is their reach. Investors, liquidity and integrators sit on many chains, and a product that lives on one chain, or splits into a separate copy per chain, limits who can use it.

The VDK allows builders of these investment products to focus on what makes their products differentiated, while using a shared infrastructure for features like cross-chain interoperability. It gives builders one configurable vault contract, and it runs that vault across chains from a single balance sheet, thanks to the LayerZero cross-chain infrastructure built in.

Bringing traditional fund mechanics onchain

Tokenized funds are moving past simple wrappers. Institutional asset managers have used mechanisms within products like notice periods, redemption gates, lockups and capital calls for decades. These mechanics balance investor liquidity against the liquidity of the underlying portfolio, and are critical functionality if tokenized products are going to be adopted at scale.

Yet bringing these features to onchain products has historically meant a significant amount of custom development. A team writes and audits its own request handling, settlement math, escrow and pricing for its first product. But the next product with different terms often means a fork or a new vault.

To design the VDK, the Centrifuge team examined 60 product mechanics from real-world investment structures, including:

  • Notice periods and dealing windows
  • Redemption gates
  • Lockups and early-exit penalties
  • Cooldown exits
  • Drawdown funds and capital calls
  • Swing pricing and entry and exit spreads
  • Side pockets

The VDK is designed so that none of these needs a fork or a separate vault implementation. Builders use the same contract with different terms.

Who the Centrifuge VDK is for

The VDK supports products beyond Centrifuge's existing funds. Each one below is a configuration of the same contract, and each can reach investors on every supported spoke.

  • Tokenized treasury funds. Instant redemptions backed by a liquidity buffer or an outside facility, plus scheduled dealing windows.
  • Private credit funds. Notice periods, redemption gates, lockups and scheduled settlement.
  • Tranched credit. Senior and junior share classes with different pricing and redemption priority.
  • Fund-of-funds. Portfolios that redeem instantly through the liquidity of the funds they hold.
  • Looping strategies. Vaults that issue shares while the underlying subscription settles.
  • Distribution vaults. Partner-specific liquidity, pricing and redemption terms on an existing share class.

Distribution vaults show how the two layers work together. A fund manager can give a wallet, exchange or fintech its own terms on a chain where that partner's users already are. The partner gets a product built for its users, and the manager keeps one share class and one NAV.

One vault, configured by plugins

The VDK is a single immutable vault contract. Builders configure it with plugins, which are contracts the vault calls for the parts that differ between products. Most plugins already have shipped implementations, so a builder usually writes only one or two.

A product is the vault plus six plugin choices:

PluginWhat it decides
Request policyWho may request, and how requests group for settlement: per investor, per request or per dealing window
Instant policyHow much can move instantly, the entry and exit spread, and who may fund a position for another investor
Liquidity routeWhere instant redemption liquidity comes from when escrow is short
OracleThe prices every conversion uses
Settlement observerWhat happens after a settlement lands, such as true-ups or accrual
Role hookWho may hold, transfer or be paid: allowlists, freezes and lockups

The first five are fixed when the vault deploys. The role hook belongs to the share token and can change for the whole share class. To change a vault's terms, a builder deploys a new vault on the same position and moves flows to it. Both vaults issue the same share token, so investors keep one position.

Standard infrastructure also helps distribution. Every product built on the VDK exposes the same interfaces, so wallets, protocols and exchanges integrate one vault design instead of many. Integration guide

One balance sheet, connected by cross-chain messaging

The VDK follows a hub-and-spoke model: each pool picks one hub chain, which holds the balance sheet, accounting and pricing. Spoke chains, such as Ethereum, Base and Arbitrum, issue, transfer and redeem shares.

A vault deployed across spokes settles against that one balance sheet. As a result:

  • Requests from every chain go into one order book.
  • The hub sets one price for every request it fills.
  • Shares move between chains by burn and mint, not as wrapped claims.

This model depends on messages to carry this information. Every deposit request, redemption, settlement and price update has to move between the hub and its spokes. If those messages are late or wrong, the single balance sheet stops being true.

Where LayerZero fits

Centrifuge sends hub-and-spoke messages through adapters using LayerZero’s cross-chain messaging infrastructure. Each message travels with proofs from more than one provider. A message executes only after more than one provider verifies it, so one transport alone cannot change a pool's state. Risk teams that review a VDK product can evaluate this design directly.

The hub and every spoke share one state. Messages between them carry proofs from more than one provider, and LayerZero is one of those providers.

Builders get this messaging from the protocol. They do not integrate a messaging provider per vault. The protocol also batches messages, retries failed ones and can subsidize gas, so investors do not need native gas tokens on each spoke.

Start building

The VDK handles product logic, cross-chain messaging handles reach. Together, they let a builder design a fund product once and offer it on every supported chain from one balance sheet.

To design a product, read the VDK overview and follow its quickstart. To learn how LayerZero messaging works across chains, start at Developers or reach out to our team.

To learn more about how LayerZero and Centrifuge are working together to make tokenized assets genuinely useful across the full surface area of onchain capital markets, read our co-authored research: Unlocking Tokenized Fund Composability.

Connect to our team

Start building