Contract deployment sequence

Fresh deploymentCopy Anchor Link

script/ProtocolDeployBase.sol in everstrat-xyz/contracts constructs:

1. Registry.
2. EVE and the ExitQueue implementation/proxy.
3. Controller, Oracle, StrategyManager, and Converter implementations/proxies.
4. Whitelist.
5. AMM.

Initialization binds modules to the Registry. Registering peers, configuring feeds/routes, granting roles, and verifying parameters are separate setup steps.

Deploy the timelock and keeper executors, register them, and finalize ADMIN/SECURITY, MINTER, and KEEPER grants. Remove temporary deployer authority as specified by the deployment scripts. Set the treasury and performance fee explicitly; current production scripts do not silently default these environment inputs.

Automation activationCopy Anchor Link

Keeper executors deploy without allowed perform callers. Create/configure Mimic tasks and allowlist their exact smart account through ADMIN. Deploying a contract or publishing a function alone does not activate automation.

Strategies and later upgradesCopy Anchor Link

Converters and token feeds must support the strategies' assets and routes. A strategy is deployed separately and contributes to the basket only after registration.

Existing deployments use governance upgrade/registration operations rather than repeating the entire fresh-deployment sequence. See Current deployments for the Controller upgrade and v2 strategy migration.