Elektrik audit reports

Elektrik has 1 public audit report from Zokyo; dated 9 Jul 2024; no critical findings reported.

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 firm10

Statuses are the security firms’ own

10 findings are still open or acknowledged in the firms’ reports: 1 high, 6 medium, 3 low (1 open, 9 acknowledged).

High
1
Medium
6
Low
3
  • High Acknowledged

    Facilitators can borrow assets and never repay it back

    Elektrik Smart Contracts Review · Zokyo · 9 Jul 2024 · Report ↗

  • Medium Open

    feeAmounts on orders are supposed to be optional (L12 OrderEngine.sol) meaning orders

    Elektrik Smart Contracts Review · Zokyo · 9 Jul 2024 · Report ↗

  • Medium Acknowledged

    Centralization Risk Due to Overpowered Owner

    Elektrik Smart Contracts Review · Zokyo · 9 Jul 2024 · Report ↗

  • Medium Acknowledged

    filledSellAmount Would Be Incorrect For Fee-On-Transfer Tokens

    Elektrik Smart Contracts Review · Zokyo · 9 Jul 2024 · Report ↗

  • Medium Acknowledged

    getUsdPrice WILL NOT WORK WITH COMPLEX/LARGE PATHS

    Elektrik Smart Contracts Review · Zokyo · 9 Jul 2024 · Report ↗

  • Medium Acknowledged

    Missing Handling for Tokens with Transfer Fees in fillOrders()

    Elektrik Smart Contracts Review · Zokyo · 9 Jul 2024 · Report ↗

  • Medium Acknowledged

    TWAP CAN BE MANIPULATED IF THE PERIOD IS SHORT ENOUGH

    Elektrik Smart Contracts Review · Zokyo · 9 Jul 2024 · Report ↗

  • Low Acknowledged

    Missing Context Header in for merkle proof

    Elektrik Smart Contracts Review · Zokyo · 9 Jul 2024 · Report ↗

  • Low Acknowledged

    Temporary DOS if one order contained a blacklisted address

    Elektrik Smart Contracts Review · Zokyo · 9 Jul 2024 · Report ↗

  • Low Acknowledged

    USE A MULTISIG ACCOUNT FOR THE OWNER

    Elektrik Smart Contracts Review · Zokyo · 9 Jul 2024 · Report ↗

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Elektrik Smart Contracts ReviewSecurity firm: ZokyoDate: Scope: Repository at commit e93d1d7None openFindings: 1 high · 6 medium · 13 low
10 fixed · 9 acknowledged · 1 open
IPFS ↗

Findings28

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

SeverityOpenAcknowledgedFixed
Critical000
High010
Medium150
Low0310
MediumfeeAmounts on orders are supposed to be optional (L12 OrderEngine.sol) meaning ordersElektrik Smart Contracts Review · Zokyo · 9 Jul 2024Open

The report gives no description here.

Open the report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

The repositories and files the reports name

Elektrik: questions

Is Elektrik audited?

Trustblock holds 1 public audit report for Elektrik, dated 9 Jul 2024. The latest is by Zokyo (“Elektrik Smart Contracts Review”).

Who audited Elektrik?

Zokyo wrote the report Trustblock holds for Elektrik.

Are there open findings in Elektrik’s audits?

10 findings are still open or acknowledged in the firms’ reports: 1 high, 6 medium, 3 low (1 open, 9 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="elektrik"
></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