Each player in a Pot claims their assigned reward with claimCut(). After the 90-day window the owner closes the pot through ContestManager::closeContest. The README says that "the manager takes a cut of the remaining pool and the remainder is distributed equally to those who claimed in time". So after the 10% manager cut, the whole unclaimed remainder should be split among the players who claimed.
Pot::closePot divides the post-cut remainder by i_players.length, which counts every player, including those who never claimed. The loop then pays only the claimants.length addresses. remainingRewards > 0 at close only when at least one player did not claim, so every real distribution pays out C/N of the bonus and leaves (N - C) * claimantCut in the Pot (C = claimants, N = players). With zero claimants the loop does not run at all and 90% of the pool stays in the Pot. Neither Pot nor ContestManager has a sweep, withdraw or rescue function, so this leftover has no intended exit.
Likelihood:
This occurs on every pot where at least one player does not claim before the close. That is the exact scenario the redistribution step exists for. No attacker and no admin error is needed: the trusted owner calling closeContest after 90 days, as designed, triggers it.
The zero-claimant variant occurs whenever no player claims during the window. The payout loop then runs zero times.
Impact:
In-time claimants receive only C/N of the bonus the README promises. With two players at 500 each and only p1 claiming, p1 receives a bonus of 225 instead of 450. With four players at 100 each and one claimer, p1 receives 67 instead of 270.
The unpaid share stays in the Pot with no intended recovery path. In the two-player case the 225 is frozen for good: p2's late claimCut (needs 500) and a second closeContest (needs 275) both revert with ERC20InsufficientBalance. With zero claimants, 900 of a 1000 pool stays in the Pot. Depending on balances, late non-claimers can instead take part of the leftover through the separate missing-deadline issue (shown in the four-player test). The in-time claimant is still not paid what they are owed.
The test deploys ContestManager and the repo's test/ERC20Mock.sol directly. It goes through createContest, fundContest, claimCut and closeContest, so the Pot is owned by ContestManager as in production. All four tests pass:
test_Baseline_AllClaim_NothingStranded (control): both players claim, the close moves nothing, and the Pot ends empty.
test_MC01_TwoPlayers_ClaimantUnderpaid_And_RemainderLocked: the manager cut is 50. p1's bonus is 225 instead of 450, and 225 is stranded. p2's claim reverts with ERC20InsufficientBalance(pot, 225, 500). A second close reverts with ERC20InsufficientBalance(pot, 175, 225). The Pot still holds 225 at the end.
test_MC01_FourPlayers_ClaimantUnderpaid: the bonus is 67 instead of 270, and 203 is left in the Pot. Two late non-claimers then take 100 each, and p1 never receives the rest of what it is owed.
test_MC01_ZeroClaimants_NinetyPercentLeftInPot: the manager cut is 100 and 900 stays in the Pot.
Save the file as test/PoC_MC-01.t.sol and run from the repository root:
Divide by the number of claimants. When nobody claimed, and for rounding dust, pay the rest to the manager instead of leaving it in the Pot. Combine this with the fix for the separate locked-manager-cut issue so that this amount actually reaches the admin, and with the claim-deadline fix so that claimants holds only in-time claimers.
## Description in `closePot` function while calclulating the shares for claimaint cut, `i_players.length` is used, instead of `claimants.length`, causing low amount being distributed to claimants. ## Vulnerability Details [2024-08-MyCut/src/Pot.sol at main · Cyfrin/2024-08-MyCut (github.com)](https://github.com/Cyfrin/2024-08-MyCut/blob/main/src/Pot.sol#L57) `Pot::closePot` function is meant to be called once contest passed 90 days, it sends the owner cut to owner and rest is splitted among the users who claimed b/w 90 days period. However, current implementation is wrong.  It uses total users (i_players.length) instead of the users (claimants.length) who claimed during the duration. This creates an unfair distribution to the participants and some of the funds could be locked in the contract. In worst case scenerio, it could be 90% if nobody has claimed from the protocol during the 90 days duration. ## POC In existing test suite, add following test: ```solidity function testUnfairDistributionInClosePot() public mintAndApproveTokens { // Setup address[] memory testPlayers = new address[](3); testPlayers[0] = makeAddr("player1"); testPlayers[1] = makeAddr("player2"); testPlayers[2] = makeAddr("player3"); uint256[] memory testRewards = new uint256[](3); testRewards[0] = 400; testRewards[1] = 300; testRewards[2] = 300; uint256 testTotalRewards = 1000; // Create and fund the contest vm.startPrank(user); address testContest = ContestManager(conMan).createContest( testPlayers, testRewards, IERC20(ERC20Mock(weth)), testTotalRewards ); ContestManager(conMan).fundContest(0); vm.stopPrank(); // Only player1 claims their reward vm.prank(testPlayers[0]); Pot(testContest).claimCut(); // Fast forward 91 days vm.warp(block.timestamp + 91 days); // Record balances before closing the pot uint256 player1BalanceBefore = ERC20Mock(weth).balanceOf( testPlayers[0] ); // Close the contest vm.prank(user); ContestManager(conMan).closeContest(testContest); // Check balances after closing the pot uint256 player1BalanceAfter = ERC20Mock(weth).balanceOf(testPlayers[0]); // Calculate expected distributions uint256 remainingRewards = 600; // 300 + 300 unclaimed rewards uint256 ownerCut = remainingRewards / 10; // 10% of remaining rewards uint256 distributionPerPlayer = (remainingRewards - ownerCut) / 1; // as only 1 user claimed uint256 fundStucked = ERC20Mock(weth).balanceOf(address(testContest)); // actual results console.log("expected reward:", distributionPerPlayer); console.log( "actual reward:", player1BalanceAfter - player1BalanceBefore ); console.log("Fund stucked:", fundStucked); } ``` then run `forge test --mt testUnfairDistributionInClosePot -vv` in the terminal and it will show following output: ```js [⠊] Compiling... [⠒] Compiling 1 files with Solc 0.8.20 [⠘] Solc 0.8.20 finished in 1.63s Compiler run successful! Ran 1 test for test/TestMyCut.t.sol:TestMyCut [PASS] testUnfairDistributionInClosePot() (gas: 905951) Logs: User Address: 0x6CA6d1e2D5347Bfab1d91e883F1915560e09129D Contest Manager Address 1: 0x7BD1119CEC127eeCDBa5DCA7d1Bd59986f6d7353 Minting tokens to: 0x6CA6d1e2D5347Bfab1d91e883F1915560e09129D Approved tokens to: 0x7BD1119CEC127eeCDBa5DCA7d1Bd59986f6d7353 expected reward: 540 actual reward: 180 Fund stucked: 360 Suite result: ok. 1 passed; 0 failed; 0 skipped; finished in 1.58ms (506.33µs CPU time) ``` ## Impact Loss of funds, Unfair distribution b/w users ## Recommendations Fix the functions as shown below: ```diff function closePot() external onlyOwner { if (block.timestamp - i_deployedAt < 90 days) { revert Pot__StillOpenForClaim(); } if (remainingRewards > 0) { uint256 managerCut = remainingRewards / managerCutPercent; i_token.transfer(msg.sender, managerCut); - uint256 claimantCut = (remainingRewards - managerCut) / i_players.length; + uint256 totalClaimants = claimants.length; + if(totalClaimant == 0){ + _transferReward(msg.sender, remainingRewards - managerCut); + } else { + uint256 claimantCut = (remainingRewards - managerCut) / claimants.length; for (uint256 i = 0; i < claimants.length; i++) { _transferReward(claimants[i], claimantCut); } } + } } ```
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.