> For the complete documentation index, see [llms.txt](https://docs.upshift.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.upshift.finance/upshift-vault-curation/upshift-for-curators.md).

# Upshift for Curators

<figure><img src="/files/q6QaC1jfeDt1Os2lNSqL" alt=""><figcaption></figcaption></figure>

A curator (also called a strategist) is a KYC’d institutional yield manager appointed to run a vault’s strategy deploying vault capital into DeFi and CeFi venues. They operate inside hard, smart-contract-enforced boundaries: a curator can never withdraw user funds to an external address while capital only moves between the vault contract, its dedicated subaccount, and whitelisted strategy contracts.

In practice, the curator’s job has four recurring components:

* **Strategy execution:** deploying and rebalancing capital across whitelisted protocols, within the mandate defined by the vault’s policy engine.
* **Performance reporting:** NAV reporting.
* **Liquidity management:** keeping the withdrawal buffer funded and unwinding positions ahead of redemption epochs.
* **Risk ownership:** monitoring venue, oracle, and counterparty risk for every position; reacting to Hypernative alerts and emergency procedures.

### Curator Responsibilities

| **Curator**                                                                                                                                                                                                                                                                                                                                           | **Upshift**                                                                                                                                                                                                                                                                      |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>Strategy design and capital allocation within the approved whitelist.</li><li>Risk and exposure management for the strategy.</li><li>Executing trades and deployments through the chosen custody model.</li><li>Maintaining the withdrawal liquidity buffer to always process redemptions on a timely manner.</li><li>Reporting NAV</li></ul> | <ul><li>Vault smart contracts, share accounting, and audits</li><li>The policy engine and whitelisting enforcement</li><li>NAV validation and pricing</li><li>Deposits, redemptions, and fee mechanics</li><li>Institutional LP distribution and prime-brokerage rails</li></ul> |

## Roles and Permissions

Every Upshift vault separates governance, operations, and strategy execution into distinct roles. The separation is the core security claim: no single party can both move user funds and change the rules.

### **Vault Owner**

A secure multisig shared between Upshift, the curator and the partner protocol (e.g. 4-of-6). It governs the parameters that define the vault itself, so no individual party can quietly alter the vault's economics or risk settings.

* Sets management and performance fees, issuance limits, and the timelock duration
* Controls emergency functions: pausing deposits/withdrawals and sweeping funds to safety
* Critical changes (fees, withdrawal periods) sit behind a 24-hour timelock so depositors can exit before they take effect

### **Vault Operator**

An institutional-grade MPC wallet handles the day-to-day mechanics of keeping a vault running. The operator can move capital between the vault and the subaccount, but never outside that perimeter.

* Processes withdrawal requests as redemption epochs mature
* Updates the vault's NAV by syncing total assets with the externally calculated value of deployed positions
* Moves liquidity between the vault contract and the strategist's subaccount
* Charges and collects fees

### **Curator**&#x20;

A KYC'd institutional yield manager holding the trader role on the vault's dedicated subaccount.

* Deploys capital and manages the strategy, only within contracts, tokens, and functions whitelisted by the policy engine
* Has no access to vault admin functions

## The flexibility you get with Upshift

* **Curator picks the custody model**.&#x20;
  * Run on an August subaccount or via Fordefi MPC, whichever matches the strategy.
* **Single or multi-asset EVM vaults**.&#x20;
  * [V1 vaults](/vault-architecture/single-asset-vault.md) accept a single asset
  * [V2 vaults](/vault-architecture/multi-asset-vault.md) accept a basket of deposit assets (e.g. USDC, USDT, PYUSD) with a single reference asset for redemptions.&#x20;
* **Curators can build vaults on** [**Solana**](/vault-architecture/solana-vaults.md) **and** [**Stellar**](/vault-architecture/stellar-vaults.md).
* **Fully configurable risk controls**. Withdrawal liquidity buffer, NAV volatility limits, and timelocks are set per vault to match the strategy’s liquidity and risk profile.
* **Multi-chain reach**. Deploy the same strategy across EVM chains, Solana and Stellar without standing up new infrastructure each time.

## Why curate on Upshift

The reason to curate a vault on Upshift is that the curator inherits a deep stack consisting of:

* **Institutional distribution from day one.** Upshift vaults get access to August’s $500M+ institutional LP network (asset managers, family offices, trading desks, and treasuries).
* **Prime-brokerage access**. Through August’s prime brokerage (\~$7bn monthly volume), curators can tap credit lines, cross-margin across DeFi and CeFi, OTC options and lending, and recognition of vault receipt tokens as collateral.
* **Trust and safety**. Contracts audited multiple times, a policy engine that prevents misappropriation, independent NAV validation, and automated risk monitoring.
* **Faster time to launch.** No contract development, no security program, no distribution build-out. Configure a vault, pick a custody model, and start deploying.

## Get Started

For new curators, it is highly recommended to review the concepts outlined next for building an in-depth understanding of Upshift vault mechanics and capabilities.&#x20;

Refer to this [section](/upshift-vault-curation/reference-smart-contract-interface.md) for all smart contract functions.


---

# 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.upshift.finance/upshift-vault-curation/upshift-for-curators.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.