Developers readme - Red Potion

Thirteen contract types across three layers. Each has a reference page (responsibility, flows, functions). Source of truth: zentryHQ/redpotion-contracts.

Contract	Layer	Role
FundManagerDeployer	Protocol root	Creates tenants; canonical implementations; protocol fee recipient
FundManager	Tenant	Launchpad: funds and strategies via 8 factories
Factory	Shared	Transparent-proxy factory + entity registry
Fund	Fund hub	Assets, settlement, role registry, strategy/wallet management
FundShare	Fund spoke	ERC-20 shares; mint/burn only by Fund
DepositQueue	Fund spoke	Batched deposits: deposit → cancel/settle → claim shares
RedeemQueue	Fund spoke	Batched redemptions: redeem → settle → fund → claim assets
Oracle	Fund spoke	Batch clock + NAV reports with safety checks
FeeManager	Fund spoke	Five fees in minted shares; high-water mark
RiskManager	Fund spoke	Caps, minimums, drawdown gate, whitelist, emergency pause
Strategy	Execution	Fund-controlled allowlisted call wallet
StandaloneStrategy	Execution	Same engine, detached from Fund, for other chains

Auth patterns

Contracts that own role state (Fund, FundManager, FundManagerDeployer, Strategy, StandaloneStrategy) use local ACL (ACLModule). The five fund spokes hold no role state — modifiers call the Fund ACL. Manage fund + spoke roles on the Fund. Details: Access control and roles.

Conventions

Prices — 1e18 asset-per-share: shares = amount × 1e18 / price
Native ETH — 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE
onlyFund — callable only through the Fund (spoke pattern)
Roles checked on the Fund — function on a spoke, authorization against Fund ACL