Velocore

Zokyo14 Aug 2023Code version: not recorded (see the report)

Audit · firm’s term: smart contract audit

Zokyo reviewed Velocore on 14 Aug 2023: 13 findings, 0 critical; 9 marked fixed, 2 acknowledged, 2 open.

No open critical findings

Open the report Open Velocore’s security record

Report stored on IPFS. Content hash QmfYmwgxSJphtXEnjVYzTZqQxGEv8rFZ4B6UfUtuW6b2HW

Trustblock does not review code.

Findings13

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

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

HighDouble spending through Double Entry Point TokensFixed

The report gives no description here.

HighExternal call to transfer ETH might fail because of memory returned dataFixed

The report gives no description here.

MediumInitializers are missing lock mechanismFixed

The report gives no description here.

MediumUnchecked delegatecall resultFixed

The report gives no description here.

LowAdd return statementFixed

The report gives no description here.

LowDebugging statements left in codeFixed

The report gives no description here.

LowDiamond implementation does not follow standardFixed

The report gives no description here.

LowTransaction executed successfully in _execute parameter edge case.Fixed

The report gives no description here.

LowVulnerable to phishingFixed

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

Velocore

Audits1 audit by 1 firmLast audit Aug 2023, by Zokyo.

Critical findingsNo open critical findingsIn 1 report.

Open Velocore’s security record

Security firm

Zokyo

89 projects reviewed · 131 reports · latest Feb 2025

See Zokyo’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.