Missing Validation to Ensure Phase 1 Penalty is Greater Than Phase 2

Description

The project documentation explicitly states that Phase 1 should have "high penalties" while Phase 2 has "moderate penalties," implying a design requirement where phase1PenaltyBps > phase2PenaltyBps.

However, the TokenLaunchHook constructor does not enforce this relationship. It allows phase2PenaltyBps to be greater than or equal to phase1PenaltyBps, potentially leading to a misconfigured state that violates the intended economic design of the launch.

Risk

Likelihood:

• Depends on deployer input.

Impact:

• Could lead to wrong information if misconfigured,

Proof of Concept

Recommended Mitigation

Add a requirement in the constructor to enforce the intended penalty hierarchy.