Skip to main content

Deployment checklist, the 0→1 path

tip

This is the path that reduces mistakes and due diligence fatigue.

Step 1, pick a starting configuration​

  • asset
  • strategy choice
  • donation address, usually a splitter or Safe-controlled destination
  • role assignments: management, keeper, and emergency admin

Step 2, do a test cycle​

  • deploy with a small amount using the correct strategy factory, such as MorphoCompounderStrategyFactory for the USDC Morpho path
  • deposit
  • withdraw
  • call report() at least once (or simulate on fork) and confirm yield routing
  • confirm the keeper can call report() and management can perform required configuration actions
  • if you create a new splitter through the Safe app, confirm the Safe batch includes both createPaymentSplitter and createStrategy

Step 3, deploy real size​

  • scale deposit
  • set an expected keeper cadence
  • set monitoring

Step 4, operationalize​

  • confirm incident response ownership (who acts if bounds are hit, if a strategy is shut down)
  • confirm role rotation policy
  • document donation-address change procedures; changes use the strategy-level cooldown before finalization

If you want the technical mental model for why report() is the key operational moment, see the Strategy Development Tutorial, especially the “When Rewards Are Reported” flow.