task_050826_9 — Fair-Launch Token Distributor, Contract Slice (Robbert)

[umeradl]

Tracking discussion for task_050826_9, the first slice of issue #75 "start fair-launch token distribution."

Assigned: @robertocarlous
Branch: feat/fair-launch-distributor (from develop)
Scope: DinFairLaunchDistributor contract only — Merkle-drop claim + cliff/linear vesting, Transparent Proxy, tested against a hand-built Merkle fixture. Eligibility computation (who qualifies, for how much) is explicitly out of scope for this slice — deferred to an indexer-backed script once P4-IDX1/P4-IDX2 land.

Post progress updates, questions, and PR links here as the task moves — same convention as prior task-tracking discussions (e.g. #50, #73).

[umermjd11]

Closing — merged to develop.

PR #77 merged today (51914cc). Covers every deliverable in this task's checklist:

• foundry/src/DinFairLaunchDistributor.sol — single Merkle-drop distributor holding all recipient vesting positions (not one contract per recipient), Transparent Proxy pattern matching the existing platform contracts, custom errors throughout, full NatSpec. deposit()/setRoot()/openClaims() (one-way, freezes root and starts the vesting clock) → claim(proof) (double-hashed leaf, one claim per address, immediate transfer of anything already vested) → release() (collect newly-vested tokens anytime) → sweepUnclaimed() (admin recovery after vesting period + 30-day grace, never touches tokens belonging to addresses that did claim).
• Deploy script following DeployPlatform.s.sol's pattern.
• 35 tests (InitTest/VestedAmountTest/DepositAndRootTest/SweepTest/ClaimTest/ReleaseTest/FundingGuardTest) covering the full lifecycle, edge cases, and a fuzz test confirming vested amounts never exceed a recipient's total allocation.
• Confirmed on current develop: forge test green, full suite included.

Eligibility computation (who qualifies, how much) was explicitly out of scope for this task — that's the next piece, tracked separately per this task's own "Explicitly out of scope" section.