Architecture

Vault Architecture

The Plume Vault framework is implemented as a modular smart-contract architecture designed to separate custody, accounting, compliance, and share issuance into independent components. This separation reduces operational risk and allows each layer of the system to evolve or be audited independently.

At the core sits NestVaultCore, an abstract vault contract implementing the ERC-4626, ERC-7540, and ERC-7575 tokenized vault standards. The vault serves strictly as the asset custody and execution layer and does not maintain internal share accounting. Instead, share ownership is represented by a dedicated ERC-20 token, NestShareOFT, which acts as the authoritative ledger for balances and total supply. Deposits and redemptions are executed through paired internal entry and exit routines that atomically transfer assets and mint or burn shares via privileged functions on the share token contract, ensuring consistent synchronization between assets under custody and issued shares.

Valuation and fee accrual are handled by NestAccountant, an independent rate and fee engine referenced by the vault. The accountant maintains the vault’s exchange rate, enforces governance-defined bounds on rate movements, and accrues management fees over time based on assets under management and elapsed time. Any rate update outside the permitted tolerance automatically pauses conversions, creating a built-in safeguard against pricing anomalies.

V2 deposit access is mediated by ComplianceProxy and its configured Predicate hook. The hook validates a signed, single-use attestation before the proxy transfers assets into the vault. For deposits on behalf, the policy screens both the executing caller and the original depositor; the share receiver is a separate address. Legacy V1 deployments use NestVaultPredicateProxy with a different proof format. Select the enabled deployment for each vault and chain, and explicitly request complianceVersion: "v2" in Actions mint requests. See the Deposit on behalf section in Integration Guides for the shared integration flow.

Vault shares themselves are implemented in NestShareOFT, a LayerZero-compatible omnichain fungible token. This design allows shares to move across chains by burning them on the source network and minting an equivalent amount on the destination chain, while the underlying assets remain stationary within the vault.

Finally, NestVaultComposer coordinates multi-step operations such as cross-chain deposits. It combines compliance verification, vault entry, and cross-chain share settlement into a single transaction flow, and integrates with Circle’s CCTP infrastructure when USDC must be bridged prior to deposit.

Together, these components form a vault infrastructure that aligns with institutional requirements for custody segregation, controlled pricing mechanisms, regulatory compliance gating, and cross-chain capital mobility.

---