When no bids have been placed on a listed NFT, the first bid should be accepted if it meets or exceeds the minimum price set by the seller, allowing auctions to start at the intended reserve level and encouraging participation.
The validation for the first bid incorrectly uses a strict greater-than (>) comparison instead of greater-than-or-equal (>=), which rejects bids exactly matching the minPrice, forcing bidders to overpay unnecessarily and creating inconsistency with other checks like subsequent bid increments or buy-now prices that allow equality.
Likelihood:
Sellers set a precise minPrice expecting bids to begin exactly at that amount
Potential first bidders submit exactly the minPrice, which is a natural choice for starting auctions
Impact:
Auctions fail to attract initial bids, leading to fewer successful sales and reduced platform activity
Frustration for users and potential loss of revenue for sellers who must relist with adjusted prices
Add the following test function into the existing tests in BidBeastsMarketPlaceTest.t.sol
Update the comparison to >= to allow exact matches, and adjust the error message for clarity. This ensures consistency across bidding logic and aligns with user expectations for minimum prices.
First bid validation uses > instead of >=, preventing valid starting bids.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.