The auction mechanism implementation doesn't match the 3-day fixed duration required in the project specifications, using a dynamic 15-minute initial duration with extensions instead.
According to the requirements, auctions should have a fixed 3-day duration after which anyone can call endAuction() (method names are also different specified in requirement doc) to finalize the auction.
*The actual implementation sets auction end time to only 15 minutes after first bid and includes an anti-sniping extension mechanism that extends the auction by 15 minutes when bids are placed near the end, with no 3-day fixed duration anywhere in the contract.
Likelihood: High
Every auction listed in the marketplace has this incorrect timing behavior because it is hardcoded into the contract
All auction settlements are affected as no auction follows the required 3-day fixed period
Impact: High
Users expecting a fixed 3-day auction will encounter a completely different mechanism with much shorter initial duration
The unexpected auction extensions could lead to confusion and disputes between buyers and sellers who had different expectations about when auctions would end
Without the fixed 3-day period, the marketplace behavior fundamentally differs from what was documented and expected
The issue can be verified by examining the auction lifecycle:
Modify the contract to align with the required 3-day auction period:
Documentation for BidBeasts Marketplace is incomplete or inaccurate, potentially leading to misconfigurations or security misunderstandings.
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.