The earnSnow function is designed to let each user earn 1 Snow token for free once per week.
However, s_earnTimer is a single global uint256 variable, not a mapping(address => uint256). When any user calls buySnow() or earnSnow(), the timer resets for everyone. This means only one user across the entire protocol can earn Snow per week.
Likelihood:
This happens on every single buySnow or earnSnow call - it is guaranteed to occur during normal usage.
An attacker can also deliberately grief by calling buySnow(0) (see H-04).
Impact:
Only 1 user total can earn free Snow per week instead of each user earning once per week.
The free earning mechanism is fundamentally broken for any multi-user scenario.
Combined with buySnow(0) griefing, an attacker can permanently block earnSnow for everyone at zero cost.
The issue manifests during normal protocol usage with multiple users. Because s_earnTimer is a single uint256 and not a per-user mapping, the first user who interacts with earnSnow or buySnow effectively locks out all other users from the free earning mechanism for an entire week.
Step-by-step scenario:
Alice calls earnSnow() at time T. She receives 1 Snow token and s_earnTimer is set to T.
Bob calls earnSnow() at time T+1 day. The check block.timestamp < (s_earnTimer + 1 weeks) evaluates to true because T+1 day < T+7 days. Bob's transaction reverts.
Charlie also tries during the same week — also reverted.
After 1 full week passes, Bob calls earnSnow() at T+7 days. He succeeds, but now s_earnTimer is reset again — blocking Charlie and Alice for another full week.
This means across the entire protocol lifetime, only ~52 users per year can earn free Snow tokens, regardless of how many users exist.
Change s_earnTimer from a single uint256 to a mapping(address => uint256) so that each user's cooldown is tracked independently. This preserves the intended "once per week per user" mechanic without allowing one user's activity to interfere with another. The buySnow function should also update only the caller's timer, and the earnSnow check should read from the caller's own mapping entry.
## Description: The `Snow::buySnow` function contains a critical flaw where it resets a global timer `(s_earnTimer)` to the current block timestamp on every invocation. This timer controls eligibility for free token claims via `Snow::earnSnow()`, which requires 1 week to pass since the last timer reset. As a result: Any token purchase `(via buySnow)` blocks all free claims for all users for 7 days Malicious actors can permanently suppress free claims with micro-transactions Contradicts protocol documentation promising **"free weekly claims per user"** ## Impact: * **Complete Denial-of-Service:** Free claim mechanism becomes unusable * **Broken Protocol Incentives:** Undermines core user acquisition strategy * **Economic Damage:** Eliminates promised free distribution channel * **Reputation Harm:** Users perceive protocol as dishonest ```solidity function buySnow(uint256 amount) external payable canFarmSnow { if (msg.value == (s_buyFee * amount)) { _mint(msg.sender, amount); } else { i_weth.safeTransferFrom(msg.sender, address(this), (s_buyFee * amount)); _mint(msg.sender, amount); } @> s_earnTimer = block.timestamp; emit SnowBought(msg.sender, amount); } ``` ## Risk **Likelihood**: • Triggered by normal protocol usage (any purchase) • Requires only one transaction every 7 days to maintain blockage • Incentivized attack (low-cost disruption) **Impact**: • Permanent suppression of core protocol feature • Loss of user trust and adoption • Violates documented tokenomics ## Proof of Concept **Attack Scenario:** Permanent Free Claim Suppression * Attacker calls **buySnow(1)** with minimum payment * **s\_earnTimer** sets to current timestamp (T0) * All **earnSnow()** calls revert for **next 7 days** * On day 6, attacker repeats **buySnow(1)** * New timer reset (T1 = T0+6 days) * Free claims blocked until **T1+7 days (total 13 days)** * Repeat step **4 every 6 days → permanent blockage** **Test Case:** ```solidity // Day 0: Deploy contract snow = new Snow(...); // s_earnTimer = 0 // UserA claims successfully snow.earnSnow(); // Success (first claim always allowed) // Day 1: UserB buys 1 token snow.buySnow(1); // Resets global timer to day 1 // Day 2: UserA attempts claim snow.earnSnow(); // Reverts! Requires day 1+7 = day 8 // Day 7: UserC buys 1 token (day 7 < day 1+7) snow.buySnow(1); // Resets timer to day 7 // Day 8: UserA retries snow.earnSnow(); // Still reverts! Now requires day 7+7 = day 14 ``` ## Recommended Mitigation **Step 1:** Remove Global Timer Reset from `buySnow` ```diff function buySnow(uint256 amount) external payable canFarmSnow { // ... existing payment logic ... - s_earnTimer = block.timestamp; emit SnowBought(msg.sender, amount); } ``` **Step 2:** Implement Per-User Timer in `earnSnow` ```solidity // Add new state variable mapping(address => uint256) private s_lastClaimTime; function earnSnow() external canFarmSnow { // Check per-user timer instead of global if (s_lastClaimTime[msg.sender] != 0 && block.timestamp < s_lastClaimTime[msg.sender] + 1 weeks ) { revert S__Timer(); } _mint(msg.sender, 1); s_lastClaimTime[msg.sender] = block.timestamp; // Update user-specific timer emit SnowEarned(msg.sender, 1); // Add missing event } ``` **Step 3:** Initialize First Claim (Constructor) ```solidity constructor(...) { // Initialize with current timestamp to prevent immediate claims s_lastClaimTime[address(0)] = block.timestamp; } ```
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.