[I-08] - Use the meaningful `errors` with trace location.
Details
We are the developers and for us these types of errors (PoolConfig()) are easy to understand but these are very difficult to understand for normal users.
In addition to that, adding a trace such as a contract name with an underscore before the error can help us later on to understand which contracts actually throw the error because sometimes similar errors exist in multiple contracts.
Links
AuctionStarted should be AuctionAlreadyStarted
https://github.com/Cyfrin/2023-07-beedle/blob/main/src/Lender.sol#L444-L445
Recommendations
Use meaningful errors and follow this convention for errors ContractName_ErrorName for better understanding later on.
Prize pool breakdown
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.