# Multistake Systems

Multistake operates as a single ERC-4626 vault on a canonical settlement layer that orchestrates strategy execution across multiple heterogeneous execution environments. Each environment contributes distinct execution characteristics, and the system aggregates them to achieve yield opportunities that cannot be efficiently captured within a single network. This architecture defines the logical components, data flows, and responsibility boundaries within the protocol.

At a high level, the system separates accounting, execution, and verification:

**Accounting**\
Accounting occurs exclusively within the Multistake vault. This includes `totalAssets()`, share minting and burning, net asset value (NAV) updates, and risk enforcement. The vault remains the sole authority over user-facing state and deterministic ERC-4626 semantics.

**Execution**\
Execution occurs within isolated strategy environments. Strategies operate across any supported blockchain based on execution efficiency, liquidity availability, and market conditions. Execution environments are treated as untrusted with respect to accounting and cannot directly modify vault state.

**Verification**\
Verification occurs through trust-minimized validation channels. All strategy-reported balances and profit-and-loss (PnL) values are independently validated before being incorporated into vault accounting.

This separation ensures that cross-domain execution never compromises vault correctness. Even if an execution environment stalls, misprices, or becomes temporarily unavailable, the canonical vault remains solvent and maintains deterministic accounting guarantees.


---

# 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://multistake-1.gitbook.io/multistake-docs/documentation/system-overview/multistake-systems.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.