QA Report

[code423n4]

Incentive to contribute late, after overflow

If the funding target is not met, the fund is not redeemable. However, after the funding target is hit, new contribution will have an advantage of redeemable, compare to early pay.

Suggestion:
Distinguish between redemption before and after funding target.

Constant discount rate for long going funding cycles will damper user's incentive to contribute

For any discount rate > 0, and multiple periodic funding cycle, the token received per ETH/USDC contribution would exponentially going to 0, makes the project less and less attractive to users. And eventually not worth contributing anymore.
For example, 0.9^20 = 0.12, 0.95^40 = 0.36, for discount rate of 10%, after 20 cycles, the token is only 12%, for discount rate of 5%, only 36% left. Keep in mind they it is exponentially decrease.

If a project is configured by a contract, not being able to change, the later stages of the project could be hard to develop.

Suggestion:
Creating alert for long going projects, or contract owned projects.

Reconfiguration can not be cancelled

There is a delay in the reconfiguration, but after submit, it can not be cancelled.
Sometimes project operators may make mistakes, or change their mind after community discussion.

Suggestion:
Allowing for cancellation for pending reconfiguration.

redemption rate should be > 0

If the redemption rate is set to 0, it is equivalent to not allow redemption, which can be set elsewhere.

Suggestion:
Enforce the redemption rate > 0