Tick a Lock
Audit · firm’s term: audit report
Cyberscope reviewed Tick a Lock on 5 Feb 2022: 4 findings, 0 critical; none marked fixed.
No open critical findings
Open the reportOpen Tick a Lock’s security record
Report stored on IPFS. Content hash bafkreidrhl7hznmljj7kwaumwobluj5hj6acpebdjfveuqz4s4je7y7xgu
Trustblock does not review code.
Findings4
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 4 | 0 | 0 |
LowL01 - Public Function could be Declared ExternalOpen
The report gives no description here.
LowL02 - State Variables could be Declared ConstantOpen
The report gives no description here.
LowL04 - Conformance to Solidity Naming ConventionsOpen
The report gives no description here.
LowL07 - Missing Events ArithmeticOpen
The report gives no description here.
Contracts in scope1
| Address | Chain | Source code |
|---|---|---|
| 0xa94f8d276638431fc85a1ef7059a20f1cd7d66ae | Chain: BNB Chain | Source code: Verified source |
Part of Tick a Lock’s security record
Tick a Lock
Audits2 audits by 1 firmLast audit Feb 2022, by Cyberscope.
Critical findings1 open critical findingReported in “Tick a Lock” by Cyberscope, Feb 2022. Not marked fixed in that report.
Open Tick a Lock’s security recordSecurity firm
Cyberscope1,783 projects reviewed · 2,056 reports · latest Oct 2026
See Cyberscope’s auditsSomething 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