# Vault Capacities

SherpaEarn aims to provide responsibly scaled yield strategies with optimized risk/return relationships.

### **Global (Collective) Capacity**

Determined by calculating the max effective capacity of the yield strategies being run.  High quality, small scale strategies that benefit a select group are preferred over lower quality, large scale strategies that end up diluting depositors, introducing increased risk, and/or decreasing returns.  Appropriately sized capacities must be enforced to keep this dynamic in check.

### **Per Chain Capacities**

These are progressively adjusted up or down as a result of both the current yield prospects available and the current demand for depositing on a given network.  Individual chain capacities add up to and cannot collectively exceed the global vault capacity. &#x20;

For example if the global capacity is 10,000,000 `USDC`, then the per chain capacity composition will look something like:

* 5,000,000 `USDC` on Ethereum cap
* 2,000,000 `USDC` on Base cap
* 3,000,000 `USDC` on Monad cap

<figure><img src="/files/TLOZkPN6YIiNFkwL6OrD" alt=""><figcaption><p>Example scenario where no capacity availabe on the selected network.  Users must wait for withdrawals to process or cap to be raised.  Alternately use a different network with space capacity.</p></figcaption></figure>

<figure><img src="/files/3T2KzUksbxD4fvII5O1J" alt=""><figcaption><p>Example scenario where spare capacity available on the selected network.  Users can deposit any amount up to the cap.</p></figcaption></figure>

### Pricing & Yield Parity&#x20;

There are no special yield benefits for depositing on one network over another.  The [multichain synchronization](/sherpaearn-vault/multichain-architecture.md) ensures that same pricing is guaranteed throughout.  In general, Ethereum will tend to be allocated a higher capacity than other secondary networks due to higher liquidity and DeFi user activity. &#x20;


---

# Agent Instructions: 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:

```
GET https://docs.sherpa.trade/sherpaearn-vault/multichain-architecture/vault-capacities.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
