Three layers
Protocol root. The FundManagerDeployer holds canonical implementations, creates tenants, and stores the protocol fee recipient. Tenant. Each fund house gets a FundManager that can create funds and holds upgrade authority for that tenant’s contracts. Tenants are isolated. Fund. Each fund is a hub-and-spoke instance: a Fund hub, spokes for deposits, redemptions, pricing, fees, and risk, plus Strategy wallets that deploy capital.Design choices
Batch settlement. Most on-chain vaults price every deposit and withdrawal against a live rate. Red Potion groups requests into batches and settles each batch at one price from an operator-submitted NAV report. That fits funds whose value depends on off-chain or cross-chain positions that cannot be read live on-chain, and gives every participant in a batch the same execution price. Operator-run, allowlist-bounded. An operator manages capital; they are not an autonomous strategy. Deployment goes only through Strategy wallets restricted to an allowlist of exact calls. Deposits and redemptions pass through a per-fund RiskManager. Roles on the Fund. Privileged actions authorize against one access-control registry on the Fund. See Access control and roles. Multi-chain execution. Capital can run on other chains via a StandaloneStrategy. Assets are bridged operationally; results feed NAV through the Oracle.Audiences
Next: How batched fund shares work.