How It Works
Deviation detection
Blend continuously monitors all accounts using your Baskets. When a position deviates from its target allocation beyond a configurable threshold, a Rebalance Request is created with status
PENDING.The request includes a snapshot of the current position state: current balance, target balance, and deviation percentage.Risk Architect review
Pending requests appear in your admin portal’s rebalance queue. For each request, you can see:
- Which account and Safe address is affected
- The current vs. target allocation
- The deviation percentage
- The proposed rebalance strategy
PENDING requests can be automatically removed if market conditions change and the position returns to sync before you review it.
Approve or cancel
After reviewing, you can:
- Approve: Locks the request and queues it for execution. Once approved, a request cannot be deleted, only executed or explicitly cancelled.
- Cancel: Dismisses the request. The position remains at its current allocation.
Execution
Approved requests are executed by Blend’s automation engine. The status transitions through:
APPROVED: Queued for executionEXECUTING: Transaction in progressCOMPLETED: Successfully rebalancedFAILED: Execution failed (can be retried)
After completion, the transaction hash is recorded for full auditability.
Request States
| Status | Description | Can Delete? |
|---|---|---|
| PENDING | Awaiting Risk Architect review. May be auto-removed if position returns to sync. | Yes (auto or manual) |
| APPROVED | Locked in, awaiting execution. | No (must execute or cancel) |
| EXECUTING | Transaction in progress. | No |
| COMPLETED | Successfully executed. Archived with transaction hash. | No |
| FAILED | Execution failed. Can be retried. | No |
| CANCELLED | Explicitly cancelled by Risk Architect. Archived. | No |
Managing the Queue
Filtering and sorting
The rebalance queue in the admin portal supports filtering by:- Status: View only pending, approved, or failed requests
- Basket: Filter by specific Basket
- Chain: Filter by blockchain network
- Deviation: Sort by largest deviation to prioritize high-impact rebalances
Batch operations
For baskets with many accounts, you can batch-approve or batch-cancel requests to streamline operations.Why Queued Rebalancing?
The queued model offers several advantages over automatic rebalancing:- Risk Architect control: You decide when positions are adjusted, avoiding rebalances during unfavorable market conditions
- Cost management: Per-rebalance fees incentivize thoughtful, deliberate changes rather than frequent, small adjustments
- Auditability: Every rebalance has a clear approval trail with timestamps and responsible team member
- Liability reduction: Risk Architects explicitly approve each rebalance, rather than the system acting autonomously