Cross-Chain Architecture
How Nest vaults coordinate EVM accounting and cross-chain share movement.
Cross-Chain Architecture
Nest vaults are designed to operate across multiple chains while preserving one consistent vault accounting model. When Nest extends a vault to an EVM chain, the full vault architecture can be deployed on that chain: vault entrypoints, share tokens, accounting contracts, authorization controls, and cross-chain messaging configuration. This lets users interact with a vault from the chain they already use while the vault system preserves consistent share accounting across deployments.
On Arc, integrate only with the vaults and deposit assets in the Vault Directory. The Smart Contracts page lists their Arc addresses; other chain deployments are not Arc entrypoints.
Each vault uses an accountant to determine the share price and enforce accounting guardrails such as rate bounds, update timing, and pause controls. For cross-chain vaults, Nest uses a hub-and-spoke accountant model: the hub accountant acts as the canonical accounting source, while spoke accountants on connected chains expose the accounting state needed for local deposits, redemptions, and share conversions. Integrations should read the accountant configured for the chain where they transact; Nest operations update configured accountant state so conversions remain aligned across supported chains.
Cross-chain share movement is handled through LayerZero's OFT infrastructure. Nest vault shares move cross-chain through OFT messaging. Depending on the deployment version, this may be implemented through the vault OFT path or a native share-token OFT; in both cases, users are moving vault share state across supported chains with burn/mint-style OFT messaging rather than receiving a wrapped bridge receipt token.
EVM Architecture
On EVM chains, users interact with Nest through local vault contracts. Deposits and redemptions are executed against local Nest vault infrastructure, and share movement between EVM chains is handled through the Nest share OFT. This means an EVM integrator usually does not need to reason about a separate bridge flow: the vault contracts and share OFT expose the relevant deposit, redeem, and transfer surfaces.
When a user moves vault shares between EVM chains, the source-chain share representation is burned or debited and the destination-chain representation is minted or credited through LayerZero OFT messaging. The vault's accounting model remains tied to the Nest accountant state rather than to the chain where the user happens to hold shares.