• [CONTRACT CREW] Deploy Migration Split Allocator option to V1 and V2 payouts, which forwards to a V3 treasury.
• [JBDAO TX] Set Migration Split Allocator to be fee-less in V2 ETH payment terminal.
• [CONTRACT CREW] Deploy a Migratable ERC-20 Token Deployer that projects can use. These tokens can be attached to a project using setFor, and will:
  • Allow holders of a particular V1 token or V2 token (claimed or unclaimed) to transfer them in to mint a commensurate amount of V3 tokens.
  • Self-report total supply that includes all versions, making redemptions on V3 convenient.
• [JBM] Give people the option to payout to the Migration Split Allocator.
• [JBM] Give people the option to deploy and attach a Migratable ERC-20 Token to their V3 project, which will take an optional V1 project ID whose tokens should be accepted from 1:1 token migrations. Holders of V1/V2 will now be able to convert to the new version of the token to have access to V3 treasury redemptions.
• [JBM] Give people instructions on how to launch V3 Funding cycles that are synchronized with their V2 or V1 treasuries, and how to deprecate the treasury they’re no longer using.
  • If there is an intent to continue accepting payments to V1 and/or V2 while V3 is active:
    • Synchronize funding cycle start time, duration, discount rate, and redemption rate to maintain consistent token issuance across versions. If there are any future changes, make sure they are reflected across all versions.
  • Else:
    • Configure V1 and/or V2 treasury to have manual funding cycles and have paused payments.
    • Launch Funding cycles on V3 where the V1 and/or V2 treasuries left off.
• [OPTIONAL JBDAO TX] Set fee to 0% on V1 and V2. Pause JBDAO V1 and V2 treasuries so they’re no longer issuing and so we no longer have to keep them in sync.