The Solidity documentation recommends "that Solidity contracts are fully annotated using NatSpec for all public interfaces (everything in the ABI)." NatSpec documentation should be used for improved readability, a better user experience, enhanced auditability, enablement of automated testing and verification, and to promote standardization and interoperability.
There are 16 instances of this issue.
| File Link | Instance Count | Instance Links |
|---|---|---|
| Beedle.sol | 2 | 11,36 |
| File Link | Instance Count | Instance Link |
|---|---|---|
| Fees.sol | 1 | 19 |
| File Link | Instance Count | Instance Links |
|---|---|---|
| Lender.sol | 3 | 73,108,116 |
| File Link | Instance Count | Instance Links |
|---|---|---|
| Staking.sol | 2 | 8,31 |
| File Link | Instance Count | Instance Links |
|---|---|---|
| IERC20.sol | 6 | 7,8,9,10,11,12 |
| File Link | Instance Count | Instance Link |
|---|---|---|
| ISwapRouter.sol | 1 | 16 |
| File Link | Instance Count | Instance Link |
|---|---|---|
| Ownable.sol | 1 | 19 |
Decreased readability and usability.
baudit: a custom static code analysis tool; manual review
Add NatSpec comments for all public functions.
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.