Fusion by IPOR

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

Fusion, by IPOR, is a yield aggregation and execution engine that routes deposits across yield sources and automates strategies including looping, carry trades, and leveraged farming. At $49M TVL across Base, Ethereum, and Arbitrum at the 2026-08-14 survey, it sits below our $100M materiality line. Rejected on size: an advisory book moved into a venue this size on the same research becomes the exit crush, whatever the engine’s quality. If it crosses the line and holds, the reopened memo would apply our delegated-allocation test, and the looping and leveraged strategies in its own description would face the rules that reject recursive leverage for client money.

Kill criteria: the events that revoke this verdict
• TVL sustained above $100M for 30 days

The research file

Mechanism applicability

IPOR describes Fusion as customizable onchain vault infrastructure: depositors receive exposure to an Atomist’s strategy, while smart contracts hold assets and off-chain keepers or Alphas execute allocation and rebalancing logic through configured integrations called fuses. This establishes delegated yield-aggregation membership, including strategies that may use looping or staking. It does not validate any curator, algorithm, fuse, vault setting or resulting portfolio.

Current observation and scope

The DefiLlama protocol API read on 2026-08-15 showed about $46.6M of tracked Fusion TVL across its listed multi-chain footprint, below the shared v1 dossier’s $100M threshold. The current official overview continues to market professionally curated, automated strategies. Vault-by-vault allocations, Atomist and fuse-manager authority, timelocks, verified integrations, audits, incidents and chain reachability remain deferred rather than presumed safe.

Exit applicability

Fusion documents both instant and scheduled vault withdrawals. Scheduled withdrawal requires a request followed by share redemption after the administrator prepares assets, and the docs warn that leveraged looping or staking strategies may be slow or costly to unwind. Exit therefore depends on the selected vault’s strategy, fuse configuration, administrator action and underlying-market liquidity. At current aggregate size, a sleeve could also represent a material share of one vault rather than merely the protocol total.

Why the class rule decides

The shared v1 below-materiality dossier decides this application; it is not an individual endorsement or rejection of a Fusion vault. Reopen only after a reproducible survey shows at least $100M of protocol TVL continuously for 30 days. The reopened review must work vault by vault, verifying the curator mandate, allocations, keeper and role controls, fuse whitelist, timelocks, audits and incidents, and observed stressed withdrawals. It must also apply the separate delegated-allocation and leveraged-looping rules where relevant; size alone would not confer approval.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• IPOR Docs — Fusion protocol documentation · primary · accessed 2026-08-15
  Supports: vault infrastructure, curated strategies, onchain asset management, Fusion identity
• IPOR Docs — liquidity-provider controls and exits · primary · accessed 2026-08-15
  Supports: Atomist, instant withdrawal, scheduled withdrawal, fuses, timelocks, leveraged looping
• DefiLlama — Fusion by IPOR survey record · secondary · accessed 2026-08-15
  Supports: current TVL, chains, yield-aggregator category

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.