> 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/key-management-and-execution-engine.md).

# Key Management & Execution Engine

When curators launch a vault, they choose how capital is held and how is executed. Upshift supports two models. Both key management and execution engines follow the same safety model: non-custodial by construction, policy-gated execution, and independent NAV validation. \
\
The difference is the operational style that fits the curator needs.

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

### August Subaccount (smart-contract wallet)

A smart-contract wallet deployed by August and owned by the vault. Curator receives a trader role and execute against a whitelisted set of protocols and tokens. The same address works across EVM chains, with built-in swap and bridging modules. August calculates NAV across spot, DeFi, perps, and options. Whitelist policies are on-chain, cryptographically enforced and verifiable.&#x20;

### Fordefi (MPC)

A shared MPC workspace operated jointly with August, governed by transaction-level policy controls. Curators propose NAV updates that August’s pricing engine validates. This suits curators who prefer an MPC key-management and signing workflow. Fordefi policies are maintained off-chain.

<table data-header-hidden><thead><tr><th width="172.93359375"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Dimension</strong></td><td><strong>August Subaccount</strong></td><td><strong>Fordefi (MPC)</strong></td></tr><tr><td>What it is</td><td>A smart-contract wallet deployed by August, owned by the vault. You receive a trader/strategist role.</td><td>A shared MPC workspace operated jointly with August, governed by transaction policies. You propose and execute through it.</td></tr><tr><td>Best for</td><td>Strategies that live on and off-chain and benefit from native cross-chain execution and August's full prime-brokerage surface. Integrations with CeFi.</td><td>Curators who want MPC key management and a familiar institutional signing workflow.</td></tr><tr><td>Execution surface</td><td>Whitelisted protocols and tokens; swap module and bridge module (LayerZero / Stargate, Chainlink CCIP); same address across EVM chains.</td><td>Policy-gated transactions across approved venues.</td></tr><tr><td>Custody control</td><td>Non-custodial by design; funds can only move between whitelisted strategy contracts and the vault, never to an external wallet.</td><td>MPC threshold signing with off-chain policy controls.</td></tr><tr><td>NAV</td><td>August calculates NAV across spot, DeFi, perps, and options.</td><td>Curator proposes NAV updates; August's pricing engine validates them.</td></tr></tbody></table>


---

# 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/key-management-and-execution-engine.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.