Libertum Bonding smart contract audit

HashlockCode version: not recorded (see the report)

Hashlock reviewed Libertum (Libertum Bonding smart contract audit) on 1 May 2025: 6 findings, 0 critical; all marked fixed.

No open critical findings
Open the reportOpen Libertum’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings6

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

SeverityOpenAcknowledgedFixed
Critical000
High003
Medium002
Low001
HighBondingToken#_finalizeSale() - Incorrect fee parameter will result inFixed

The report gives no description here.

HighBondingToken#_finalizeSale() - Uninitialized state variable is used during UniswapV3 pool creation.Fixed

The report gives no description here.

HighBondingToken#buy/sell - An attacker can force any user to buy or sell tokens on their behalfFixed

The report gives no description here.

MediumBondingToken#_finalizeSale() - Lack of slippage protection will result in suboptimal swaps.Fixed

The report gives no description here.

MediumBondingToken#buy/sell - Hardcoded lbm cost might be problematicFixed

The report gives no description here.

LowBondingToken/BondingFactory- Contract does not follow CEI pattern.Fixed

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

Libertum
Audits4 audits by 2 firmsLast audit May 2025, by Hashlock.
Critical findingsNo open critical findingsAcross 4 reports.
Open Libertum’s security record

Security firm

Hashlock

198 projects reviewed · 279 reports · latest Jul 2026

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