NettyWorth

Resonance Security6 addresses on Ethereum

Audit · firm’s term: audit report

Resonance Security reviewed NettyWorth on 25 Nov 2024: 13 findings, 3 critical; 12 marked fixed, 1 acknowledged.

3 critical findings, fixed
Open the reportOpen NettyWorth’s security record
Report stored on IPFS. Content hash Qmderke4rGECvjuGZwVb7Bm2zH7mnsk9vAayLJiDdChiLg

Trustblock does not review code.

Findings20

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

SeverityOpenAcknowledgedFixed
Critical003
High002
Medium012
Low005

Marked Info by the firm. Not counted as findings.

Info++i/i++ Should Be unchecked{++i}/unchecked{i++}Fixed

When it is not possible for counters to overflow, as is the case when used in for and while-loops, they should be unchecked. The unchecked keyword is new in solidity version 0.8.0, so this only applies to that version or higher, which these instances are. This saves 30-40 gas per loop.

InfoConsider Disabling renounceOwnership()Fixed

As NettyWorth does not include eventually giving up all ownership control, consider overwriting OpenZeppelin's Ownable's renounceOwnership() function in order to disable it.This will prevent the protocol from being left unattended in the event that the owners renounce ownership.

InfoCritical Changes Should Use Two-step ProcedureFixed

The critical procedures used to change proxies, fees or owners in this protocol should use a two step process in order to ensure the modification is indeed intended.

InfoEvents That Mark Critical Parameter Changes Should Contain Both The Old And The New ValueFixed

UpdatedAdminWallet() and UpdatedAdminFee() events should emit the previous information and the new one to improve traceability.This should especially be done if the new value is not required to be different from the old value

InfoNew Deployment Causes Loss Of Information About Used NoncesFixed

During loan creation, the protocol calls the SignatureUtils contract that manages and validates the signatures of the lender and borrower.The functions used for these validations use a nonce that is previously validated and stored in the _nonceUsedForUser mapping from the proxy, so it can only be used once per loan.In case that a new version of the contract is deployed, the _nonceUsedForUser mapping will be empty and the data in the old contract will not be accessible, allowing the reuse of nonces and the replay of signatures.

InfoNon-external Function Names (Private Or Internal) Should Begin With An UnderscoreFixed

According to the Solidity Style Guide, non-external function names should begin with an underscore.

InfoNon-external Variable (Private Or Internal) Should Begin With An UnderscoreFixed

According to the Solidity Style Guide, non-external variable names should begin with an underscore.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Part of NettyWorth’s security record

NettyWorth
Audits3 audits by 2 firmsLast audit Jul 2026, by CredShields.
Critical findingsNo open critical findingsAcross the 3 reports, 14 critical findings were reported. Each is marked fixed by the firm that reported it.
Open NettyWorth’s security record

Security firm

Resonance Security

27 projects reviewed · 57 reports · latest Dec 2025

See Resonance Security’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us