> For the complete documentation index, see [llms.txt](https://docs.ensemble.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ensemble.io/reference/parameters-and-limits.md).

# Parameters and limits

Where settings come from and how they affect exposure and transaction capacity.

Settings determine the strategy the vault aims to hold, the fees it charges, and how much you can transact. The vault and CircuitBreaker enforce different checks, so a request must fit both.

| Parameter                           | Scope             | Primary authority                                                       | User impact                       |
| ----------------------------------- | ----------------- | ----------------------------------------------------------------------- | --------------------------------- |
| Basket, direction, target leverage  | Product strategy  | Live vault strategy/config; published strategy describes product intent | Market exposure                   |
| Cash buffer target                  | Product strategy  | Vault config                                                            | Capital location and liquidity    |
| Rebalance interval and drift        | Product strategy  | Vault config                                                            | Maintenance eligibility           |
| Management and transaction fees     | Product economics | Vault config within contract bounds                                     | NAV or transaction proceeds       |
| Vault total cap                     | Vault accounting  | Vault                                                                   | Maximum accepted assets           |
| Deposit-window cap                  | Vault accounting  | Vault                                                                   | Time-window deposit capacity      |
| Route minimum and hard maximum      | Route             | CircuitBreaker                                                          | Accepted transaction amount       |
| Rolling protocol/vault/account caps | Route             | CircuitBreaker                                                          | Current remaining capacity        |
| Execution spread and slippage       | Maintenance       | Vault execution policy                                                  | Order eligibility and size        |
| Confirmation timeout                | Maintenance       | Vault execution policy                                                  | Stale-action cancellation         |
| Pause and emergency state           | Safety            | CircuitBreaker and vault                                                | Availability and transaction path |

See [Fees and caps](/how-it-works/fees-and-caps.md) for fee terms and the controls that affect capacity.

## Current capacity controls

The six production vaults share these vault-scoped controls. Capacity can be lower because of usage, account or protocol limits, liquidity, pauses and pending state. Settings can change.

| Control                          | Configured value |
| -------------------------------- | ---------------: |
| Total deposit cap                |         $500,000 |
| Deposit transaction maximum      |          $25,000 |
| Redemption transaction maximum   | $50,000 net USDC |
| Deposit route minimum            |              $10 |
| Redemption route minimum         |               $0 |
| Vault rolling deposit cap        |         $500,000 |
| Vault rolling redemption cap     |         $500,000 |
| Rolling bucket duration          |         24 hours |
| Static deposit-window cap        |          $50,000 |
| Adaptive deposit-window cap rate |                0 |

A zero redemption minimum adds no positive route minimum; other checks still apply. Adaptive rate zero disables adaptive sizing, leaving the static cap in force. A hard maximum of zero generally means unlimited policy, while a total cap or enabled adaptive effective cap of zero provides no capacity. See [CircuitBreaker](/safety/circuit-breaker.md) for field-specific semantics and attribution.

## Reading a live setting

Read settings from a verified deployment at a known block, then record where and when each value was observed.

1. Resolve the verified network and contract generation.
2. Read compatible contract or Lens state at a named block.
3. Read route state when the setting affects deposits or redemptions.
4. Label the value with source and observation time.

See [Fees and caps](/how-it-works/fees-and-caps.md).