> For the complete documentation index, see [llms.txt](https://docs.bundles.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bundles.fi/performance/rebalancing-strategy.md).

# Rebalancing strategy

Bundles.fi employs a threshold rebalancing strategy as its core mechanism to drive bundle performance. This approach systematically adjusts asset weights to capture value from market fluctuations.

### How Threshold Rebalancing Works

{% hint style="info" %}
Threshold rebalancing captures value from market fluctuations by selling overperforming assets
\
and reinvesting in those with higher growth potential.
{% endhint %}

The strategy monitors deviations from target weights, triggering rebalancing when an asset exceeds the predefined threshold (e.g., 5% deviation). It sells the overweight asset (due to strong performance) and reinvests in the underweight one.

<div data-with-frame="true"><figure><img src="/files/5OryO144tTB1B7e9IE65" alt=""><figcaption></figcaption></figure></div>

### **Value Generation: Long-Term Dynamics**

While rebalancing does not generate immediate value, fees align with arbitraged value at execution, yielding no profit at that moment.&#x20;

It enables buy-low/sell-high dynamics over time. Deviations prompt swaps that realign the bundle, capturing rebounds from market cycles. In volatile conditions, where prices rise and fall, this exploits mean reversion: selling highs and buying lows compounds gains that a static hold would miss.

Over the long term, with sustained volatility, the compounded effect of these adjustments accumulates greater value than holding unchanged weights, as the bundle continually optimizes exposure to rising trends while mitigating underperformance.

### Rebalancing Fee Extraction

Rebalancing fees are paid with [$BUN](/ecosystem/usdbun.md). If the bundle accumulates excess $BUN—due to repeated rebalancing or $BUN appreciation used to repurchase depreciated assets (relative to others)—15% of the fee value is extracted from the bundle. This occurs after $BUN has gained value, positioning it as a structured accrual rather than an isolated cost. The extraction is allocated as follows:

* **With a Curator**: 5% to the curator, 10% burned.
* **Without a Curator**: 15% burned.

This mechanism supports the protocol's deflationary design, reducing $BUN supply while incentivizing balanced growth, and integrates seamlessly with [dynamic threshold adjustments](/ecosystem/interconnectivity-of-bundles-via-usdbun.md) for opportunistic rebalancing.

### Fully automated through arbitrage

*Arbitrage is the process of buying an asset on one market at a lower price and selling it on*
\
*another market at a higher price to earn a profit.*

Arbitrage automates rebalancing when thresholds are crossed, keeping bundles assets aligned with their target allocations.

This makes the bundles entirely self managed, requiring no action from investors while keeping asset
\
weights within their target allocations.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bundles.fi/performance/rebalancing-strategy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.