Rebalancing and editing

The fund’s manage screen shows each asset’s target next to its live weight. Rebalance moves the holdings back to the targets with Jupiter swaps, signed by your app wallet. The app lets a rebalance use up to 3% slippage — lower than for deposits, because a rebalance spends the fund’s money and its holders carry the slippage. Every rebalance is recorded onchain and listed in the fund’s rebalance history.

On every rebalance swap the contract checks that:

• the output lands in a declared asset of the same fund — nothing can be swapped out of the basket;
• the route touches no fund account other than the declared input and output;
• the amount received clears a minimum measured after the swap;
• the fund’s own policy limits are respected (see Fund policy).

These ceilings are compiled into the rebalancer. In the current version they bind delegated keys, not the creator: a creator rebalancing their own fund is limited only by the policy they set.

• Add an asset, change the targets, or remove one, then save. The new weights must add up to 100%.
• Removing an asset needs its balance in the vault at zero, so the app first sells it into the rest of the basket. Pressing minus on a row does both.
• A USDC cash sleeve stays declared at 0% and is never a row to remove: the next rebalance spends it back into the basket.
• Saving brings the holdings in line with the new targets, so the fund can keep accepting deposits right away.

The admin role moves in two steps: the current admin names a new wallet, and that wallet accepts. Until it accepts, nothing changes.

A creator can let a key rebalance on its own when drift crosses a threshold or on a schedule. That key can only rebalance, inside the delegated-key limits above. See Agent and MCP.