Freename - Name Service Smart Contract

Resonance SecurityCode version: not recorded (see the report)

Resonance Security reviewed Freename (Freename - Name Service Smart Contract) on 18 Mar 2023: 20 findings, 3 critical; 15 marked fixed, 5 acknowledged.

3 critical findings, fixed
Open the reportOpen Freename’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings24

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

SeverityOpenAcknowledgedFixed
Critical003
High003
Medium024
Low035
MediumConcurrent Usage Of Ownable And AccessControlAcknowledged

The report gives no description here.

MediumMinting SLD Does Not Require Existent TLDAcknowledged

The report gives no description here.

LowRedundant Code On _beforeMinting()Acknowledged

The report gives no description here.

LowRedundant Code On Storage ContractsAcknowledged

The report gives no description here.

LowUnnecessary Usage of EnumerableMapAcknowledged

The report gives no description here.

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 Freename’s security record

Freename
Audits2 audits by 1 firmLast audit Mar 2023, by Resonance Security.
Critical findingsNo open critical findingsAcross the 2 reports, 6 critical findings were reported. Each is marked fixed by the firm that reported it.
Open Freename’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