FestivalPass.sol
createMemorabiliaCollection(...)
redeemMemorabilia(uint256 collectionId)
The normal behavior is that a memorabilia collection created with maxSupply = N should allow exactly N successful redemptions. In particular, a 1-of-1 collection should allow one successful redemption, and a collection with supply 10 should allow ten redemptions.
The issue is that each collection starts with currentItemId = 1, but the sold-out check in redeemMemorabilia() requires currentItemId < maxSupply instead of allowing the final item. This makes the last item in every collection unreachable.
As a result:
a 1-of-1 collection is immediately unreedeemable on the very first attempt;
a collection with maxSupply = N only ever allows N - 1 redemptions;
organizer-configured inventory is silently overstated;
honest users are blocked from redeeming valid advertised supply.
The root cause is the mismatch between:
currentItemId being 1-indexed;
and the sold-out condition using strict < maxSupply.
For example, when maxSupply = 1, the very first redeem attempt starts with currentItemId = 1, so the contract evaluates:
which immediately reverts.
Likelihood:
The issue occurs deterministically for every collection because it is caused by fixed initialization and a fixed comparison.
The bug triggers on normal honest-user redemption flow and does not require any special attacker capability.
Every 1-of-1 collection is broken from the moment it is created.
Every larger collection loses its final redeemable item.
Impact:
Honest users cannot redeem the full advertised memorabilia supply.
1-of-1 collections can never be redeemed at all.
The organizer can configure supply values that the contract can never actually deliver.
The protocol’s BEAT-to-memorabilia redemption flow is broken at the collection boundary.
The following Foundry test shows that a collection created with maxSupply = 1 is already considered sold out before the first redemption:
Observed result:
This confirms that the very first redemption of a 1-of-1 collection reverts as sold out, so the collection can never produce its single intended item.
The sold-out check should be aligned with the 1-indexed currentItemId. With the current indexing model, redemption should stay open while currentItemId <= maxSupply.
An equivalent alternative is to switch currentItemId to zero-based indexing and keep the comparison consistent. The important requirement is that a collection with maxSupply = N must permit exactly N successful redemptions.
# Off-by-One in `redeemMemorabilia` Prevents Last NFT From Being Redeemed ## Description * The `createMemorabiliaCollection` function allows an organizer to create an NFT collection that can be exchanged for the BEAT token via the `redeemMemorabilia` function by users. * The `redeemMemorabilia` function checks if `collection.currentItemId` is less than `collection.maxSupply`. However, the `currentItemId` starts with 1 in the `createMemorabiliaCollection` function. This prevents the final item (where `currentItemId` equals `maxSupply`) from being redeemed. ```Solidity function createMemorabiliaCollection( string memory name, string memory baseUri, uint256 priceInBeat, uint256 maxSupply, bool activateNow ) external onlyOrganizer returns (uint256) { require(priceInBeat > 0, "Price must be greater than 0"); require(maxSupply > 0, "Supply must be at least 1"); require(bytes(name).length > 0, "Name required"); require(bytes(baseUri).length > 0, "URI required"); uint256 collectionId = nextCollectionId++; collections[collectionId] = MemorabiliaCollection({ name: name, baseUri: baseUri, priceInBeat: priceInBeat, maxSupply: maxSupply, @> currentItemId: 1, // Start item IDs at 1 isActive: activateNow }); emit CollectionCreated(collectionId, name, maxSupply); return collectionId; } function redeemMemorabilia(uint256 collectionId) external { MemorabiliaCollection storage collection = collections[collectionId]; require(collection.priceInBeat > 0, "Collection does not exist"); require(collection.isActive, "Collection not active"); @> require(collection.currentItemId < collection.maxSupply, "Collection sold out"); // Burn BEAT tokens BeatToken(beatToken).burnFrom(msg.sender, collection.priceInBeat); // Generate unique token ID uint256 itemId = collection.currentItemId++; uint256 tokenId = encodeTokenId(collectionId, itemId); // Store edition number tokenIdToEdition[tokenId] = itemId; // Mint the unique NFT _mint(msg.sender, tokenId, 1, ""); emit MemorabiliaRedeemed(msg.sender, tokenId, collectionId, itemId); } ``` ## Risk **Likelihood**: * A legitimate user calls `redeemMemorabilia` attempting to redeem the last NFT in a collection. **Impact**: * The user fails to get the NFT, even though the redemption counter has not reached the maximum supply of the collection. ## Proof of Concept The following test shows a user trying to redeem the 10th NFT in one collection. Running `forge test --mt test_Audit_RedeemMaxSupply -vv` shows the output that the 10th redemption is reverted due to the sold out. ```Solidity function test_Audit_RedeemMaxSupply() public { vm.prank(organizer); uint256 maxSupply = 10; // Cap for memorabilia NFT collection uint256 collectionId = festivalPass.createMemorabiliaCollection( "Future Release", "ipfs://QmFuture", 10e18, maxSupply, true ); vm.startPrank(address(festivalPass)); beatToken.mint(user1, 10000e18); // Give enough BEAT for user vm.stopPrank(); vm.startPrank(user1); for (uint256 i = 0; i < maxSupply - 1; i++) { festivalPass.redeemMemorabilia(collectionId); console.log("Redeem sucess:", i + 1); // Redeem success from 1 to 9 } // 10th redeem call reverts with "Collection Sold out" vm.expectRevert("Collection sold out"); festivalPass.redeemMemorabilia(collectionId); console.log("Redeem reverted:", maxSupply); vm.stopPrank(); } ``` ## Recommended Mitigation Modify the supply check in `redeemMemorabilia` to use `<=` (less than or equal to) instead of `<`, ensuring that the final item can be redeemed. This approach is preferable to modifying the `createMemorabiliaCollection` function (which is clearly documented to start `currentItemId` at 1). ```diff // Redeem a memorabilia NFT from a collection function redeemMemorabilia(uint256 collectionId) external { MemorabiliaCollection storage collection = collections[collectionId]; require(collection.priceInBeat > 0, "Collection does not exist"); require(collection.isActive, "Collection not active"); - require(collection.currentItemId < collection.maxSupply, "Collection sold out"); + require(collection.currentItemId <= collection.maxSupply, "Collection sold out"); // allow equals // Burn BEAT tokens BeatToken(beatToken).burnFrom(msg.sender, collection.priceInBeat); // Generate unique token ID uint256 itemId = collection.currentItemId++; uint256 tokenId = encodeTokenId(collectionId, itemId); // Store edition number tokenIdToEdition[tokenId] = itemId; // Mint the unique NFT _mint(msg.sender, tokenId, 1, ""); emit MemorabiliaRedeemed(msg.sender, tokenId, collectionId, itemId); } ```
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.