Audit Report
Paladin reviewed Pangolin (Audit Report) on 8 Apr 2025: 11 findings, 0 critical; 5 marked fixed, 6 acknowledged.
No open critical findings
Open the reportOpen Pangolin’s security record
Report hosted on paladinsec.co.
Trustblock does not review code.
Findings11
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 2 |
| Medium | 0 | 2 | 1 |
| Low | 0 | 4 | 2 |
MediumThe fee parameter used in the swap path and for gathering specific pools no longer guarantees returning a pool which uses that feeAcknowledged
The report gives no description here.
MediumUsers who mint directly from the PangolinV3Pool contract will not receive any token rewardsAcknowledged
The report gives no description here.
LowGas optimizationsAcknowledged
The report gives no description here.
Lowinitialize() is not protected for the PangolinV3Pool implementation contractAcknowledged
The report gives no description here.
LowReward rate delta can be incorrect when the timestamp has surpassed type(uint32).maxAcknowledged
The report gives no description here.
LowUse of immutable clones rather than deploying pools as separate contracts will result in higher gas costs over timeAcknowledged
The report gives no description here.
Contracts in scope2
| Address | Chain | Source code |
|---|---|---|
| 0xf40937279f38d0c1f97afa5919f1cb3cb7f06a7f | Chain: Avalanche | Source code: Verified source |
| 0x1128f23d0bc0a8396e9fbc3c0c68f5ea228b8256 | Chain: Avalanche | Source code: Verified source |
Part of Pangolin’s security record
PangolinAudits1 audit by 1 firmLast audit Apr 2025, by Paladin.
Critical findingsNo open critical findingsIn 1 report.
Open Pangolin’s security recordSecurity firm
Paladin176 projects reviewed · 241 reports · latest Apr 2025
See Paladin’s auditsSomething 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