MAINNETNo vaults

Strategy & Parameters

read-only

Layer A · on-chain contract parameters

ParameterCurrent (on-chain)FunctionRoleDelayNote
Performance fee—setPerformanceFeeCURATORnonecap 20% in code · spec expects 1 h timelock
Management fee—setManagementFeeCURATORnonecap 5% in code
Minimum deposit—setMinAssetsCURATORnone
Maximum vault size—setMaxTotalAssetsCURATORnone0 = no limit
Entry provider—setEntryProviderADMINnonezero address → deposits stay idle
Add provider—addProviderTimelocknot collected
Remove provider (empty)—removeProviderADMINnonereverts while it holds assets
Force-remove provider—forceRemoveProviderTimelocknot collected
Treasury—setTreasuryTimelocknot collected
Timelock—setTimelockTimelocknot collected
Grant / revoke role—grantRole / revokeRoleADMINnone
Pause deposits / withdrawals—pauseWATCHDOGnone
Unpause—unpauseRECOVERYnone
Emergency withdraw—emergencyWithdraw(providers[])WATCHDOGnonesingle key; funds → vault
Re-allocate after EW—allocateRECOVERYnone
Upgrade implementation—ProxyAdmin.upgradeProxyAdmin owner—owner to be confirmed

No vault data from the API. Fields marked “not collected” need an on-chain reader (epic C).

Layer B · PSO & Automation Engine

No Layer B config in the DB yet — PSO/automation parameters are not persisted.

Layer C · CRA config

—

No CRA config version in the DB yet — layer C (ladder, hysteresis, weights) is not persisted.

Pinned, not editable: a failed gate always means 0%; no score means no allocation (fail-closed); a zero vault timelock is always a violation.