Liquidity Bootstrapping Pool Manager

Paladin1 address on Arbitrum

Paladin reviewed Swerve (Liquidity Bootstrapping Pool Manager) on 23 Aug 2023: 14 findings, 0 critical; 12 marked fixed, 2 acknowledged.

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

Report hosted on paladinsec.co.

Trustblock does not review code.

Findings14

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

SeverityOpenAcknowledgedFixed
Critical000
High002
Medium012
Low018
HighAdding liquidity to TraderJoe will result in stuck fundsFixed

The report gives no description here.

HighFees can be circumvented by partial withdrawalsFixed

The report gives no description here.

MediumBoth exit functions are vulnerable to frontrunningFixed

The report gives no description here.

MediumUsers can circumvent the fee on fundTokenFixed

The report gives no description here.

Low_feeRecipientsBPS and _recipientAddresses are privateFixed

The report gives no description here.

Low_recipientAddresses distribution is flawedFixed

The report gives no description here.

LowgetPools will eventually malfunction due to gas issuesFixed

The report gives no description here.

LowLack of validationFixed

The report gives no description here.

LowLBP creators are limited in their privilegesFixed

The report gives no description here.

LowLeftover tokens can get stuck during createLBPFixed

The report gives no description here.

Show 2 more
LowThe contract does not work with tokens that have a fee on transferFixed

The report gives no description here.

LowTypographical issuesFixed

The report gives no description here.

Contracts in scope1

AddressChainSource code
0xfddec530d36d3b51753018948ef40ea64626046bChain: ArbitrumSource code: Verified source

Part of Swerve’s security record

Swerve
Audits1 audit by 1 firmLast audit Aug 2023, by Paladin.
Critical findingsNo open critical findingsIn 1 report.
Open Swerve’s security record

Security firm

Paladin

176 projects reviewed · 241 reports · latest Apr 2025

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