Developers readme

Red Potion deploys 13 contract types across three layers. Each has a dedicated page covering its responsibility, key flows, and function reference. The authoritative source of truth is the zentryHQ/red-potion-contract repository.

Contract	Layer	One-liner
FundManagerDeployer	Protocol root	Creates tenants; holds canonical implementations and the protocol fee recipient.
FundManager	Tenant	Per-tenant launchpad: creates complete funds and strategies via its 8 factories.
Factory	Shared	Generic transparent-proxy factory + entity registry, reused everywhere.
Fund	Fund hub	Holds assets, orchestrates settlement, central role registry, strategy/wallet management.
FundShare	Fund spoke	ERC-20 share token; mint/burn only by the 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 price reports with safety checks and accept windows.
FeeManager	Fund spoke	Entry/exit/management/performance/protocol fees, paid in minted shares; high-water mark.
RiskManager	Fund spoke	Deposit/redeem guardrails: caps, minimums, drawdown gate, whitelist, emergency pause.
Strategy	Execution	Fund-controlled wallet limited to an allowlist of exact calls.
StandaloneStrategy	Execution	The same engine, detached from Fund control, for deploying on other chains.

The two auth patterns

Contracts authorize privileged calls one of two ways. Contracts that own their role state (Fund, FundManager, FundManagerDeployer, Strategy, StandaloneStrategy) use a local ACL (ACLModule, OpenZeppelin AccessControlEnumerable). The five fund spokes (DepositQueue, RedeemQueue, Oracle, FeeManager, RiskManager) hold no role state—their modifiers call back into the Fund’s access control. As a result, all roles for a fund and its spokes are managed on the Fund. Full detail in Access Control & Roles.

Conventions used throughout

Prices are 1e18-scaled asset-per-share: shares = amount × 1e18 / price.
Native ETH uses the sentinel 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE.
onlyFund means the function can only be reached through the Fund (spoke pattern).
Roles checked on the Fund means the function lives on a spoke but authorizes against the Fund’s ACL.

Getting started

Overview

Using Red Potion

Developers

Security

The two auth patterns

Conventions used throughout

​The two auth patterns

​Conventions used throughout

The two auth patterns

Conventions used throughout