Submission Details
Severity:
Inconsistent Logic in Bid Validation
Description
For the first bid, the logic requires msg.value > minPrice. For subsequent bids, the check is msg.value >= previousBid increment. This creates an inconsistency: first bid must be strictly greater, while later bids allow equality.
placeBid():
require(msg.value > requiredAmount, "First bid must be > min price");
Risk
Impact:
-
Minor UX confusion for users.
-
A bidder may wonder why their first bid equal to the minimum price is rejected, while equal increments later are accepted.
Recommended Mitigation
Standardize the check across all cases by using >=.
Updates
Lead Judging Commences
cryptoghost about 1 month ago
Submission Judgement Published Assigned finding tags:
BidBeasts Marketplace: First Bid > Instead of >=
First bid validation uses > instead of >=, preventing valid starting bids.
Rewards breakdown
nSLOC
170This contest has a flat reward structure with the following payouts:
100 EXP
20 EXP
2 EXP
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.