Ajna Protocol - lukris02's results

A peer to peer, oracleless, permissionless lending protocol with no governance, accepting both fungible and non fungible tokens as collateral.

General Information

Platform: Code4rena

Start Date: 03/05/2023

Pot Size: $60,500 USDC

Total HM: 25

Participants: 114

Period: 8 days

Judge: Picodes

Total Solo HM: 6

Id: 234

League: ETH

Ajna Protocol

Findings Distribution

Researcher Performance

Rank: 77/114

Findings: 1

Award: $36.24

QA:
grade-b

🌟 Selected for report: 0

🚀 Solo Findings: 0

QA Report for Ajna Protocol contest

Overview

During the audit, 9 non-critical issues were found.

â„–TitleRisk RatingInstance Count
NC-1Create a modifierNon-Critical3
NC-2Hardcoded valuesNon-Critical1
NC-3Use gender-neutral pronounsNon-Critical3
NC-4Use double quotesNon-Critical2
NC-5Inconsistency when using uint and uint256Non-Critical6
NC-6Prevent zero transfersNon-Critical2
NC-7No space between the control structuresNon-Critical4
NC-8Remove extra spacesNon-Critical11+
NC-9Missing leading underscoresNon-Critical20

Non-Critical Risk Findings(9)

NC-1. Create a modifier

Description

Duplicate code can be declared as modifier.

Instances

NC-2. Hardcoded values

Description

It is recommended to avoid using hardcoded values because they can change between implementations, networks or projects.

Instances

NC-3. Use gender-neutral pronouns

Description

Avoid using he/his/him.

Instances
Recommendation

Change "his" to "their".

NC-4. Use double quotes

Description

It is recommended to use double quotes for string literals.

Instances

NC-5. Inconsistency when using uint and uint256

Description

Some variables is declared as uint and some as uint256.

Instances
Recommendation

Stick to one style.

NC-6. Prevent zero transfers

Description

Check that amount to transfer > 0.

Instances

NC-7. No space between the control structures

Description

According to Style Guide, there should be a single space between the control structures if, while, and for and the parenthetic block representing the conditional.

Instances
Recommendation

Change:

if(...) { ... }

to:

if (...) { ... }

NC-8. Remove extra spaces

Instances

NC-9. Missing leading underscores

Description

Internal and private state variables and constants should have a leading underscore.

Instances
Recommendation

Add leading underscores where needed.

#0 - c4-judge

2023-05-18T18:36:31Z

Picodes marked the issue as grade-b

AuditHub

A portfolio for auditors, a security profile for protocols, a hub for web3 security.

Built bymalatrax © 2024

Auditors

Browse

Contests

Browse

Get in touch

ContactTwitter