Swift Finance audit reports

Swift Finance has 1 public audit report from Paladin; dated 22 Oct 2021; no critical findings reported. It also holds 4 deployed contracts on 1 chain.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm22

Statuses are the security firms’ own

22 findings are still open or acknowledged in the firms’ reports: 1 high, 21 low (all acknowledged).

High
1
Low
21
  • High Acknowledged

    Severely excessive rewards issue when a token with a transfer tax is added

    Audit Report · Paladin · 22 Oct 2021 · Report ↗

  • Low Acknowledged

    Adding EOA or non-token contract as a pool will break updatePool and massUpdatePools

    Audit Report · Paladin · 22 Oct 2021 · Report ↗

  • Low Acknowledged

    Contract can be refactored as it only contains a single pool

    Audit Report · Paladin · 22 Oct 2021 · Report ↗

  • Low Acknowledged

    deposit, withdraw and emergencyWithdraw can be made external

    Audit Report · Paladin · 22 Oct 2021 · Report ↗

  • Low Acknowledged

    deposit, withdraw and emergencyWithdraw can be made external

    Audit Report · Paladin · 22 Oct 2021 · Report ↗

  • Low Acknowledged

    depositRewards should be restricted to onlyOwner

    Audit Report · Paladin · 22 Oct 2021 · Report ↗

  • Low Acknowledged

    Lack of constructor safeguards

    Audit Report · Paladin · 22 Oct 2021 · Report ↗

  • Low Acknowledged

    Lack of events for add, set, setReferralCommissionRate, updateStartTimestamp, forceWithdraw, transferSwiftTokenOwnership

    Audit Report · Paladin · 22 Oct 2021 · Report ↗

  • Low Acknowledged

    Lack of events for setRewardPerBlock, setRewardEndTimestamp and updateStartTimestamp

    Audit Report · Paladin · 22 Oct 2021 · Report ↗

  • Low Acknowledged

    Lack of sanity checks in switchActivePool

    Audit Report · Paladin · 22 Oct 2021 · Report ↗

All 22 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Audit ReportSecurity firm: PaladinDate: Scope: 4 addresses on AvalancheNone openFindings: 2 high · 3 medium · 21 low
4 fixed · 22 acknowledged
paladinsec.co ↗

Findings26

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

SeverityOpenAcknowledgedFixed
Critical000
High011
Medium003
Low0210

No open finding in these reports.

Contracts4

AddressChainSource code
0xf0ee9f1ffb32c6ceef7e491daa189cc74352b8dbChain: AvalancheSource code: Verified source
0xb4569ddf3deab09cc94e5c6697e001bf7ee70884Chain: AvalancheSource code: Verified source
0x1d14af50a6691e2af983dd32d715c674ca8ab05cChain: AvalancheSource code: Verified source
0x9c88dfaeb52b126be5ed3d554f82bd0385953085Chain: AvalancheSource code: Verified source

Swift Finance: questions

Is Swift Finance audited?

Trustblock holds 1 public audit report for Swift Finance, dated 22 Oct 2021. The latest is by Paladin (“Audit Report”).

Who audited Swift Finance?

Paladin wrote the report Trustblock holds for Swift Finance.

Are there open findings in Swift Finance’s audits?

22 findings are still open or acknowledged in the firms’ reports: 1 high, 21 low (all acknowledged). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="swift-finance"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

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