← Protocols
Centrifuge
RWA·Ethereum · Base · Arbitrum · Plume · Avalanche · Centrifuge Chain

Centrifuge

01Description

Onchain asset management infrastructure for tokenizing real-world assets into permissioned pools and tranched senior/junior tokens. V3 (April 2025) added multichain pool deployment via Wormhole on Ethereum, Base, Arbitrum, Plume, Avalanche, and Centrifuge Chain.

02Best for
  • 01private credit pools
  • 02RWA tokenization
  • 03tranched senior/junior pool tokens
  • 04multichain fund administration
  • 05issuer-managed allowlists
03Install
  • pnpm add @centrifuge/sdk
04Environment variables
VariableScopeDescription
CENTRIFUGE_RPC_URLServerEVM RPC endpoint for the chain hosting the Centrifuge pool you target.
NEXT_PUBLIC_CENTRIFUGE_POOL_IDClientPool ID (e.g. Anemoy LTF, New Silver) — read from Centrifuge app URL.
05Prompt snippet
Use Centrifuge V3 for tokenizing illiquid RWAs into pools with senior/junior tranches. Each pool issues an ERC-20 tranche token gated by a per-issuer allowlist registry; transfers revert if either sender or receiver is not in the pool's allowed-investor set. Read pool state, NAV, and tranche prices via `@centrifuge/sdk` (`Centrifuge` client → `pool(poolId).tranche(trancheId)`); investments require `requestDeposit`/`mint` flow and settle on epoch close. Compliance lives at the EVM-adapter layer (off-token), so do not assume free transferability — always check `checkTransferRestriction` before attempting `transferFrom`. Multichain deployments use Wormhole; pick the chain matching the target tranche (Ethereum mainnet for most established pools, Base/Arbitrum/Plume for newer ones).
06Gotchas
  • Tranche tokens are NOT freely transferable — every transfer is gated by a per-pool allowlist; calling `transfer` to a non-allowed wallet reverts.
  • Investments and redemptions are epoch-based: requests are queued and only settle when the issuer closes the epoch, so UX must show 'pending' states (orderbook).
  • NAV is published off-chain by the pool issuer (Anemoy, New Silver, BlockTower, etc.) — your UI must surface that NAV is operator-attested, not fully onchain.
  • Each pool has its own KYC provider and jurisdiction rules (US accredited vs. non-US professional); never assume a single global investor allowlist.
  • V3 pools span multiple chains via Wormhole — withdrawing on a different chain than you deposited can take minutes-to-hours and incur relayer fees.
07Alternatives