# Accounting & Architecture in a Multi-Chain System

The Multistake vault treats execution environments as external modules. Although strategy execution spans multiple blockchain networks, the system behaves as a single-chain vault because:

* `totalAssets()` is computed exclusively within the canonical vault.
* Deposits mint shares only after final settlement is confirmed.
* Withdrawals burn shares only after liquidity is verifiably available.
* Strategy-reported balances must be validated before inclusion in accounting.
* Invalid, stale, or unavailable execution environments are excluded from NAV computation.

The protocol does not assume trust in any remote execution environment or external state source. Instead, it relies on trust-minimized validation mechanisms and deterministic ERC-4626 accounting to preserve correctness and safety.

***

### High-Level Architecture Diagram 

```
          +----------------------------------------+
          |           Canonical Vault             |
          |     ERC-4626 • NAV • Risk Controls     |
          +-------------------+--------------------+
                              |
                              v
                 +-------------------------------+
                 |        Rebalance Router       |
                 +-------------------------------+
                     /             |             \
                    v              v              v
          +----------------+  +----------------+  +----------------+
          | Execution Env A|  | Execution Env B|  | Execution Env C|
          |   Strategies   |  |   Strategies   |  |   Strategies   |
          +----------------+  +----------------+  +----------------+
                     \             |             /
                      \            |            /
                       v           v           v
                 +-------------------------------+
                 |     Validation / Verification |
                 |   (Balances, Rewards, PnL)    |
                 +-------------------------------+
                              |
                              v
                     Canonical NAV Update
```

The architecture enforces three fundamental guarantees:

**NAV Correctness**\
Only validated state updates can affect vault accounting. Failures or inconsistencies in external execution environments cannot inflate, corrupt, or compromise NAV.

**Execution Isolation**\
Each execution environment operates as an isolated module. Faults, downtime, or adverse behavior in one environment cannot propagate to others or impact vault integrity.

**User Predictability**\
Despite multi-environment execution, all user-facing behavior strictly conforms to ERC-4626 semantics, preserving consistent deposits, withdrawals, and share accounting.

These guarantees enable Multistake to safely exploit heterogeneous execution environments as a yield advantage without compromising trust assumptions, determinism, or protocol security.


---

# 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/accounting-and-architecture-in-a-multi-chain-system.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.