Processing User Redemptions

Standard Redemption (Sufficient Reserves)

When a user requests a redemption, the swing price penalty is calculated immediately based on current reserve levels and locked in. If there are sufficient assets in reserve, the rebalancer can fulfill the redemption directly from reserve during the next rebalance window. Once fulfilled, the assets (minus the predetermined swing penalty) are transferred to the escrow contract, where they become available for the user to withdraw.

Component Liquidation

If reserves are insufficient, the rebalancer must liquidate components following the liquidation queue order, and the maximum swing penalty is applied. For example:

• User requests redemption of 100,000 USDC

• Node has 20,000 USDC in reserve

• Rebalancer can partially fulfill the redemption from the reserve

• Rebalancer must liquidate components to source remaining 80,000 USDC

• Components are liquidated in strict queue order (e.g., Aave positions before Ethena)

• Maximum swing penalty is applied to the redemption as it has depleted the reserve

• Once complete, assets are transferred to escrow for user withdrawal

The swing price penalty varies between reserve and component redemptions. Redemptions from reserves use a calculated penalty based on reserve impact, while redemptions requiring component liquidation automatically incur the maximum swing penalty, as defined by the Node Owner. This design protects longer term investors from short term speculative flows.