LIKO PROTOCOL

Cyberscope1 address on BNB Chain

Audit · firm’s term: audit report

Cyberscope reviewed Liko Protocol on 22 Apr 2023: 12 findings, 0 critical; none marked fixed.

No open critical findings
Open the reportOpen Liko Protocol’s security record
Report stored on IPFS. Content hash bafkreibwlxoyfncjasnp237n7y6whemb7vmaeycd5vyybbm46rfeoojbki

Trustblock does not review code.

Findings12

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium100
Low1100
MediumBC - Blacklists AddressesOpen

The report gives no description here.

LowIDI - Immutable Declaration ImprovementOpen

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.

LowL12 - Using Variables before DeclarationOpen

The report gives no description here.

LowL16 - Validate Variable SettersOpen

The report gives no description here.

LowL20 - Succeeded Transfer CheckOpen

The report gives no description here.

LowPVC - Price Volatility ConcernOpen

The report gives no description here.

LowRTS - Reward Token SanitisationOpen

The report gives no description here.

Show 2 more
LowST - Stops TransactionsOpen

The report gives no description here.

LowULTW - Transfers Liquidity to Team WalletOpen

The report gives no description here.

Contracts in scope1

AddressChainSource code
0x16dbe5a6626402a04d6f4f6fadc2826780409f39Chain: BNB ChainSource code: Verified source

Part of Liko Protocol’s security record

Liko Protocol
Audits1 audit by 1 firmLast audit Apr 2023, by Cyberscope.
Critical findingsNo open critical findingsIn 1 report.
Open Liko Protocol’s security record

Security firm

Cyberscope

1,783 projects reviewed · 2,056 reports · latest Oct 2026

See Cyberscope’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