IPOR Fusion is Ready for Compound v3's Main and Institutional Markets

Supported markets:

• Ethereum: USDC (main and Institutional), USDT
• Base: USDC, ETH
• Arbitrum: USDC

Across all its markets, Compound v3 holds over $1B in collateral.

Vaults can supply, borrow, claim rewards and value their positions onchain through a dedicated set of fuses, with every market and limit set in the vault’s configuration.

Get started with IPOR Fusion and Compound v3

• Integration guide (configuration and addresses): compound_v3 README
• Build vaults with AI agents (MCP, Python SDK, Launchpad): AI vaults
• Python SDK and CLI: pip install -U ipor-fusion
• MCP server: mcp.ipor.io
• Docs: Build on Fusion
• Quick start: quick start guide
• Compound v3 markets: app.compound.xyz/markets

What the IPOR Fusion x Compound v3 integration unlocks for operators

• Supply and collateral in one fuse: CompoundV3SupplyFuse supplies the market’s base asset or any collateral asset to the Comet, and withdraws it, capped at the vault’s actual balance. Compound v3 has no collateral switch, so every supplied collateral asset counts towards the borrowing limit automatically. Only assets granted to the vault’s Compound market can be used.
• Borrowing the base asset: CompoundV3BorrowFuse borrows USDC against collateral supplied by the vault on the Ethereum USDC markets, main and Institutional, and on the Base USDC market. On Arbitrum, supply, rewards claiming and valuation are live, with borrowing following as the rollout progresses. Collateralisation and liquidation stay with the Comet itself.
• Exact repayment: repayment through the borrow fuse is capped at the outstanding debt, so it never turns into a stray supply position. A full repayment closes the debt to exactly zero, with no interest dust left behind and no token allowance left open to the Comet.
• Rewards claiming: rewards accrued on the vault’s Compound v3 positions can be claimed within the vault’s rules, through IPOR Fusion’s rewards claim fuses.
• Net position valued onchain: the balance fuse values the vault’s full Compound v3 position (supplied base, collateral, minus debt) using the vault’s own price oracle (or the Comet’s price feeds, for vaults that only supply), and feeds it into the vault’s share price.

Compound v3 Institutional Market

The Institutional Market is a dedicated USDC market on Ethereum, with curated collateral: ETH, wstETH, wBTC and cbBTC. It runs on its own Comet, and IPOR Fusion vaults reach it through a dedicated set of fuses, with the same mechanics as the main market: supplying collateral, borrowing and repaying USDC, onchain valuation, and rewards claiming, ready for when rewards are configured for the market.

The market is permissionless for supplying and borrowing, so operators can add it to their vaults through configuration straight away.

Compound also runs an early access program with boosted rewards for whitelisted USDC suppliers. IPOR Fusion vault operators who meet the criteria are welcome to apply by submitting their vault address.

Compound v3’s design, a single borrowable base asset per market with collateral isolated per Comet, maps directly onto IPOR Fusion’s market structure.

One IPOR Fusion market corresponds to exactly one Comet, so an operator decides market by market which assets a vault can supply, post as collateral or borrow. Collateral assets the operator doesn’t grant are simply out of scope.

Five protocol-specific fuses

These capabilities come from five protocol-specific fuses:

• CompoundV3SupplyFuse: supplies and withdraws base and collateral assets.
• CompoundV3BorrowFuse: borrows the base asset and repays it, capped at the outstanding debt.
• CompoundV3ClaimFuse: claims rewards distributed through Compound’s CometRewards.
• CompoundV3WithPriceOracleMiddlewareBalanceFuse: values the position through the vault’s price oracle middleware, for vaults that borrow.
• CompoundV3BalanceFuse: values the position with the Comet’s own price feeds, for vaults that only supply.

In practice: borrowing on Compound v3 from an IPOR Fusion vault

Here’s what a borrow cycle looks like on the main Ethereum USDC market.

The vault posts wstETH as collateral and borrows USDC against it in a single execution, then unwinds the same way: repay the full debt, then withdraw the collateral. Both steps run atomically, so each either completes in full or not at all. Amounts are illustrative.

// open: supply wstETH as collateral, then borrow USDC against it
actions[0] = FuseAction(supplyFuse, abi.encodeWithSignature("enter((address,uint256))",
    CompoundV3SupplyFuseEnterData({asset: WSTETH, amount: 10e18})));
actions[1] = FuseAction(borrowFuse, abi.encodeWithSignature("enter((uint256))",
    CompoundV3BorrowFuseEnterData({amount: 10_000e6})));
PlasmaVault(vault).execute(actions);

// close: repay the full debt (capped at what's owed), then withdraw the collateral
actions[0] = FuseAction(borrowFuse, abi.encodeWithSignature("exit((uint256))",
    CompoundV3BorrowFuseExitData({amount: type(uint256).max})));
actions[1] = FuseAction(supplyFuse, abi.encodeWithSignature("exit((address,uint256))",
    CompoundV3SupplyFuseExitData({asset: WSTETH, amount: type(uint256).max})));
PlasmaVault(vault).execute(actions);

The Python SDK includes a worked example for the Institutional Market that runs the same cycle end to end, from deploying a vault and wiring market 57 to borrowing, repaying and withdrawing the collateral, in a single simulation with nothing signed.

To existing operators: Compound v3 access is a configuration away

Existing IPOR Fusion vaults on Ethereum, Base and Arbitrum can add Compound v3 without redeploying.

An operator holding the fuse manager role, granted by the vault’s Atomist, adds the fuses for the chosen Comet, grants its base and collateral assets as substrates and sets the balance fuse.

All of these fuses are listed in IPOR Fusion’s curated fuse whitelist, used by the app and the SDK. Vault users don’t need to take any action.

The Compound v3 fuses, including those for the Institutional Market, are also available in the IPOR Fusion Python SDK, CLI and MCP: operators and their agents can look up every fuse by name and check the configuration batch with preflight before anything is signed.

Data as of 5 November 2026.