Governance model
Deployment wires owner authority to a TimelockController (configured with a 2 day minimum delay), with a multisig as proposer/executor.
CLCore, CLManager, ReferralManager, adapters, valuation, and planner ownership are transferred to timelock-controlled governance.
Admin configuration surface
| Area | Owner-controlled settings |
|---|---|
| Pool allowlist and lifecycle | setPoolStatus controls Allowed, Deprecated, and NotAllowed status for each pool. |
| DEX adapter allowlist | addAllowedDex and removeAllowedDex control which adapters are usable. |
| Bot allowlist and fees | addBot/removeBot, setProtocolFeeBps, setBotFeeBps, and earned-fee settings. |
| Core wiring | setManager, setValuation, setProtocolReserve, and setBridgeTokens. |
| Manager and referral wiring | Planner, valuation, ReferralManager, default referrer, minimum open USDC, and max batch keys. |
Operational controls
| Control | Behavior |
|---|---|
| Pause control | Guardian pause blocks normal lifecycle execution paths while incident response is active. |
| Execution gating | Lifecycle actions are guarded by contract pause checks and allowlist checks. |
| Recovery behavior | Emergency recovery flows are documented in Emergency Response and Recovery. |
What users should verify
Use Contract Addresses for current timelock, core, manager, referral, and adapter addresses.
Use Allowed Pools for current pool status context and monitor on-chain contract events for configuration and lifecycle changes.
Report a security issue
EZManager does not currently operate a formal bug bounty program, but we appreciate responsible disclosures. If you believe you have found a security vulnerability, email us with relevant details and reproduction steps, or DM @tgc2005 on Telegram.
security@ezmanager.finance