Velodrome

MixBytesCode version: not recorded (see the report)

MixBytes reviewed Velodrome Finance (Velodrome) on 3 Oct 2025: 13 findings, 0 critical; 10 marked fixed, 3 acknowledged.

No open critical findings
Open the reportOpen Velodrome Finance’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings13

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium001
Low039
MediumUnclaimed Fees Become Inaccessible After V2Locker.unlock()Fixed

The report gives no description here.

LowFees Remain on Locker When bribeAmount Is ZeroFixed

The report gives no description here.

LowLeft-Over Token Dilution During V2 Playground MigrationFixed

The report gives no description here.

LowMissing Pool Validation Lets Anyone Create Lockers for Arbitrary TokensFixed

The report gives no description here.

LowMissing Reentrancy Protection in CLLocker.increaseLiquidity()Fixed

The report gives no description here.

LowPotential Revert on Zero Bribe AmountFixed

The report gives no description here.

LowPre-Transferring Tokens Enables Front-Running AttackFixed

The report gives no description here.

LowStaked Lockers Cannot Be Unlocked Without Prior UnstakingFixed

The report gives no description here.

LowUnnecessary Zero Token Transfers in Fee ClaimsFixed

The report gives no description here.

LowUnused and Redundant ImportsFixed

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

Velodrome Finance
Audits11 audits by 3 firmsLast audit Oct 2025, by MixBytes.
Critical findingsNo open critical findingsAcross the 11 reports, 1 critical finding was reported. It is marked fixed by the firm that reported it.
Open Velodrome Finance’s security record

Security firm

MixBytes

26 projects reviewed · 81 reports · latest Nov 2026

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