Summary: Lagoon is best understood not as just another tokenized-fund frontend or generic vault factory, but as an attempt to turn professional fund operations into a reusable onchain control plane. Its docs separate the layers that many onchain funds pitches flatten together: ERC-7540 request-and-settle vault accounting, a silo for pending flows, curator-run strategy execution, independently proposed valuation, admin-controlled lifecycle and fee policy, access-manager gating, security-council guardrails, and a protocol-registry-gated opt-in upgrade path. That decomposition makes Lagoon a useful comparison point for Reserve, tokenized-fund wrappers, and compliance-heavy tokenization stacks because it exposes where practical authority sits in a tokenized strategy: with the curator who allocates and chooses settlement timing, the valuation provider who proposes NAV inputs, the admin who can pause / close / reconfigure key roles, the access manager who decides investor admission, or the protocol layer that whitelists upgrade targets.
What it does:
Provides ERC-7540-based vault contracts for asynchronous subscription and redemption cycles, with optional synchronous mode and async-only configuration
Uses a request → valuation → settlement → claim workflow so deposits and withdrawals are batched and settled against a chosen NAV point rather than executed immediately
Separates operational roles across vault admin, curator, valuation provider, access manager, and security council instead of collapsing strategy, governance, and investor admission into one operator key
Supports non-custodial strategy operation through external curation setups such as Safe multisigs or institutional MPC, with Lagoon framing itself as compatible with multiple custody solutions
Adds protocol-registry-gated proxy upgrades through an opt-in transparent proxy plus delay mechanism, so each vault can choose whether and when to adopt Lagoon-whitelisted logic upgrades
Encodes fund-like fee logic, lifecycle controls, sanctions / whitelist / blacklist access modes, and onchain reporting metadata for investor-facing discovery and monitoring
Key claims:
Lagoon’s main analytical value is the way it decomposes a tokenized fund into distinct control surfaces. The docs make strategy execution, valuation, investor admission, safety guardrails, and upgradability separate roles rather than one generic vault manager authority.
The ERC-7540 async flow is the core mechanism worth preserving. Users request deposits or redemptions first, then a later settlement cycle prices them against a curator-approved valuation point. That makes settlement timing and NAV publication a first-class governance surface rather than a background ops detail.
The curator role is where practical investment discretion sits. Lagoon is explicit that the curator allocates capital, validates valuation proposals, and decides when batches settle, which makes the curator more like a portfolio operator plus transfer agent than a passive strategy bot.
The vault-admin role is equally important because it governs the non-strategy control plane: pausing, switching access modes, changing key addresses, initiating closure, and updating fee parameters. That makes non-custodial fund infrastructure less neutral than it first sounds.
The opt-in proxy model is especially worth keeping. Lagoon does not present upgrades as a simple admin privilege; it inserts a protocol-registry allowlist plus per-vault delay windows and a separate upgrade authority. That creates a useful comparison layer between immutable vaults, manager-upgradeable vaults, and protocol-curated implementation menus.
Investor admission is also split out clearly. Access control can be whitelist, blacklist, or sanctions-list-driven, and the docs treat that as a dedicated role rather than an incidental frontend filter. That matters for comparing tokenized funds against regulated-token stacks where eligibility policy is often hidden behind the issuer brand.
Lagoon belongs in the corpus because it sharpens an underrepresented onchain fund operating system branch: not just tokenized shares, but the full machinery of async dealing, NAV-based settlement, role segregation, upgrade governance, and investor gating.
The strongest caveat is that Lagoon still retains protocol-level influence over authorized upgrade paths. The docs and FAQ explicitly say Lagoon is the only entity capable of deploying vault upgrades, even if each vault’s own upgrade authority decides whether to enforce them.
Whitepaper: No dedicated whitepaper was reviewed for this entry. The canonical primary materials were the official docs pages collected in ../whitepapers/lagoon-primary-sources-2026-05-15.md.