The end of the airdrop is computed as the start time plus the duration in seconds, and the start time defaults to zero until the owner sets it. With a normal duration and a default start time, the end lands at a fixed timestamp near the Unix epoch, so on any live chain the finished check is already satisfied and the owner can withdraw all funds before the airdrop is ever configured, while claims stay closed. With an unusually large duration the window can instead span the current time, allowing eligible users to claim before the start time is set at all. A related initialization gap is that the constructor accepts a duration of zero even though the duration setter rejects zero, so a contract can be deployed with duration zero and, while the start time is still unset, the end also evaluates to zero, leaving the withdrawal path immediately open while claims stay permanently closed until both values are configured. All of these behaviors stem from deriving the schedule from unvalidated defaults rather than from a required nonzero start and duration.

The claim path approves the escrow and the withdrawal path transfers the remaining balance, and in both cases the boolean return value is ignored. The in repository token returns true and would not misbehave, but the escrow and token are external trust boundaries, and relying on a call that could return false without reverting is unsafe practice. A safe wrapper that reverts on a false return or a missing return value should be used.

The owner-only withdrawal function transfers the remaining token balance to a recipient supplied by the caller without checking that the recipient is not the zero address. A mistaken call would move the entire remaining balance to an address from which it cannot be recovered. Since this is owner controlled the likelihood is low, but a simple guard removes the hazard.

The claim function verifies an individual entitlement and immediately creates the vote escrow lock, but the contract never checks that its own balance of the claim token covers the sum of all outstanding entitlements in the tree. If the contract is funded with less than the total the tree allocates, or funding is otherwise reduced before every eligible account has claimed, the early claims succeed and the lock creation for a later, equally eligible account reverts once the balance is exhausted. Eligible beneficiaries are then treated unequally based only on the order in which they claim. Because airdrop recipients have not necessarily paid for their allocation, the impact is lower than the unfunded presale claim, but the absence of any reserve or solvency invariant is a real fairness and availability weakness.