Launch toolkit
Launching includes more than deploying contracts. The deployed configuration, governance, metadata, integrations, monitoring, and user-facing risk context all need an owner and a verification step.
This checklist is non-exhaustive. It is not certification or a substitute for reviewing the contracts and live deployment.
Launch sequence
| Step | Decide and verify | Start with |
|---|---|---|
| 1. Define the product | Choose EVK market, standalone vault, vault cluster, or Earn vault; identify intended users and dependencies. | Products, Vault types, Markets |
| 2. Design the configuration | For EVK, select assets, collateral relationships, oracle routes, IRM, caps, LTVs, liquidation settings, hooks, and fees. For Earn, select the asset, strategies, roles, caps, queues, allocation process, liquidity plan, and fees. | Curate, EVK introduction, Earn introduction |
| 3. Deploy | Use the Creator UI or reviewed scripts for EVK, or the Earn deployment guide for an Earn vault. | Creator UI, EVK deployment, Earn deployment |
| 4. Assign control | Set governors, timelocks, emergency roles, allocators, curators, fee recipients, and operational ownership. | Governance contracts, Pause and upgrade |
| 5. Verify deployed state | Read addresses, bytecode, assets, routes, parameters, roles, queues, and permissions from the target chain; simulate representative actions. | Contract addresses, Data querying |
| 6. Publish context | Add labels, metadata, entity information, notices, and links needed by users and integrators. | Labels and metadata |
| 7. Test integrations | Check app discovery, deposits, borrows, repayments, withdrawals, liquidations, allocation, monitoring, and failure paths that apply. | Build, Euler SDK |
| 8. Handoff operations | Record owners for monitoring, parameter changes, governance execution, incident response, communications, and post-launch verification. | Curate, Security |
Final review
Before making the deployment available to users, confirm:
- Market risk: collateral exposure, oracle behavior, caps, LTVs, liquidity, liquidation incentives, hooks, fees, and connected-vault dependencies.
- Control: current role holders, selector permissions, timelocks, upgradeability, pause paths, signer policy, and recovery limits.
- User context: asset and product labels, governance disclosures, reward and APY sources, withdrawal constraints, deprecation notices, and support ownership.
- Execution: representative transactions simulate successfully against the intended chain and addresses, with expected approvals, calldata, events, and post-state.
For Earn-specific roles, strategies, queues, caps, fees, and allocation checks, use the EulerEarn launch guide. For EulerSwap 2, verify the exact version and connected deployment before applying version-specific controls.