app.morpho.org migration from Bundler3 to Bundles

On September 24, 2026, the Morpho app will move from Bundler3 to a new set of Bundles contracts.

This migration changes the contracts used by the app to prepare and execute transactions. Your existing positions remain in the same Morpho protocol contracts, but your wallet may ask you to authorize or approve a new contract the next time you perform an action.

Bundler3 is a generic system that can combine many contract calls. Bundles instead use dedicated entry points for specific Morpho actions.

This makes transactions more predictable and easier for wallets, MPC policies, and security tools to verify, while still completing multiple steps atomically in one transaction.

For most users, no action is required before the migration.

The first time you interact with a Morpho Blue position after the migration, the app may ask you to complete a one-time authorization for the new BlueBundlesV1 contract. Once confirmed, this position authorization normally does not need to be repeated unless you revoke it or the authorized contract changes.

This authorization is separate from token approvals:

- Position authorization allows the Bundles contract to act on your Morpho Blue position. This is normally completed once.

- Token approval or signature allows the Bundles contract used for the action to transfer a specific token. For Variable Rate Market actions, this is BlueBundlesV1. The app may still request this for each token transfer, as before.

Always review the contract and action displayed in your wallet before confirming a transaction.

If you use Fireblocks, Utila, Fordefi, or another MPC or institutional wallet, your organization may restrict which smart contracts your wallet can interact with.

Your wallet administrator may need to add the relevant Bundles contracts to your policy or contract allowlist before you can continue using the Morpho app.

The relevant contract depends on the action:

- BlueBundlesV1: Variable Rate Market actions, including supply collateral, withdraw collateral, borrow, repay, supply loan asset, withdraw loan asset, and position migration on app.morpho.org.

- VaultBundlesV1: Morpho Vault deposits, withdrawals, and V1-to-V2 migrations.

- VaultExitBundlesV1: in-kind redemptions and Vault V2 force-withdraw flows.

- MidnightBundlesV1: Fixed Rate Market actions on markets.morpho.org.

Contract addresses differ by network. Use the official Morpho contract addresses page to find the address for your network and intended action.

If the relevant contract is not allowed by your wallet policy, your wallet may block the transaction before it is submitted.

No. The migration changes the transaction-routing contracts used by the Morpho app. It does not require you to withdraw, redeposit, or recreate an existing position.

You only need to review and confirm the new authorization or approval when prompted.

Yes. After the migration, you can remove contracts used only for the old Bundler3 flow.

Keep the Morpho core protocol contracts and any Morpho Vault addresses your organization still uses. These remain part of the new flow. You must also allowlist the relevant new Bundles contracts.

This applies only to managed wallet policies. Retail users do not need to take any action.

You may see both:

1. A one-time authorization for the new Bundles contract to manage your Morpho position.

2. A token approval or signature for the asset involved in the transaction.

These permissions have different purposes, so confirming the first one does not remove the need for the second.