Source References: Code citations link to raw GitHub files pinned to commit

46bad16d

.

• You are configuring or debugging multicurve launches on V4
• You need curve share math and position distribution behavior
• You need locked vs migrable pool semantics

• Confirm curve set and share total (

  WAD

  exact)
• Decide variant:
  • Base multicurve (

    UniswapV4MulticurveInitializer

    )
  • Scheduled multicurve (

    UniswapV4ScheduledMulticurveInitializer

    )
  • Decay multicurve (

    DecayMulticurveInitializer

    )

1. Build

   Curve[]

   and validate shares/tick spacing.
2. Initialize pool with selected variant.
3. Confirm status path:

   • Initialized

     (migrable, no beneficiaries)

   • Locked

     (beneficiaries configured)
4. Track progression to far-tick exit (for migrable pools).
5. If locked, use fee collection paths instead of migration exits.

• Curve shares not summing to

  WAD

• Tick spacing misalignment
• Treating locked pools as migrable
• Wrong assumptions about scheduled start or decaying fee behavior

• PARAMETERS.md
• FLOW.md
• FORMULAS.md
• GOTCHAS.md
• VARIANTS.md

• v4-dynamic-auction
• doppler-hook-initializer
• fee-architecture
• verification