oma 3

QuillAudits29 Jul 2024Files named in the report

Audit · firm’s term: audit report

QuillAudits reviewed OMA3 (oma 3) on 29 Jul 2024: 5 findings, 0 critical; 2 marked fixed, 3 open.

No open critical findings

Open the report Open OMA3’s security record

Report hosted on quillaudits.com.

Trustblock does not review code.

Findings5

Statuses are the security firm’s own, from its report.

Severity	Open	Fixed
Critical	0	0
High	0	0
Medium	1	0
Low	2	2

MediumCentralization RiskOpen

The current reward mechanism of the protocol and the user onboarding process are not conducted on-chain. This lack of on-chain implementation may lead to significant issues such as reduced transparency, limited traceability, and potential security vulnerabilities.

LowAddress appearing more than once in array causes gas wastageOpen

The tendency of generating a large array of addresses and amounts, with an address reoccur twice, is high. If an address occurs more than once in the array of parameters passed into the allow function, it will set the value more than once, depending on how often it reoccur.

LowSome conditions are dependent on an offchain activityOpen

Slash function allows the slasher address to slash users’ stakes on the OMA lock contract. Both staking contracts have the slashing attribute; however, the conditions for slashing users' stakes are not explicitly implemented in the contracts. This alongside some other conditions like evaluating the voting power mechanism of users, onboarding, etc.