DeFi Saver confirms a lower limit-order execution buffer

What happened

DeFi Saver’s official explanation confirms that its limit-order trigger buffer has been reduced from 1% to 0.15%.

What changed

The backend can attempt execution with a quote closer to the user’s target, changing the operational threshold for automated swaps.

What did not change

The user’s limit price remains unchanged. Execution still depends on backend submission, available balances and on-chain condition checks; orders fill completely or revert.

Confirmed

• The official notice identifies the old and new trigger buffers as 1% and 0.15%.
• The backend monitors conditions and submits the eventual transaction.
• The smart contract rechecks conditions and can revert if the price no longer qualifies.
• The notice states that reaching the limit price alone does not guarantee immediate execution.

Still open

• The precise rollout date and whether all supported deployments changed simultaneously.
• Measured execution and revert performance under volatile conditions.
• Which selected automation positions use this feature.

What it means for an advisor

• Review the DeFi Saver memo’s order-trigger and execution-reliability assumptions.
• Update operational testing scenarios to reflect the smaller trigger buffer.
• Keep backend transaction routing and execution latency in the automation dependency analysis.