YieldNest audit reports

Arbitrum, Base, BNB Chain, Ethereum, Scrollyieldnest.financeXGitHub

YieldNest has 4 public audit reports from Zokyo, Composable Security and ChainSecurity; the latest is Zokyo, 4 Feb 2025; no critical findings reported.

Critical findings
No open critical findings
Across 4 reports.
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 firm6

Statuses are the security firms’ own

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

Medium
3
Low
3
  • Medium Acknowledged

    Fee on withdrawal from strategy can lead to protocol's loss

    YieldNest Integration with Kernel on BNB Chain · Composable Security · 6 Jan 2025 · Report ↗

  • Medium Acknowledged

    Inability to unstake required assets from Kernel

    YieldNest Integration with Kernel on BNB Chain · Composable Security · 6 Jan 2025 · Report ↗

  • Medium Acknowledged

    Lack Of Checks To Prevent Adding Duplicate Assets in the Initialize() Functions

    YieldNest · Zokyo · 7 May 2024 · Report ↗

  • Low Acknowledged

    Decimals should be read from asset

    YieldNest Integration with Kernel on BNB Chain · Composable Security · 6 Jan 2025 · Report ↗

  • Low Acknowledged

    Inability to deposit and withdraw different asset than the base

    YieldNest Integration with Kernel on BNB Chain · Composable Security · 6 Jan 2025 · Report ↗

  • Low Acknowledged

    Lack of clear limitations on fees

    YieldNest Integration with Kernel on BNB Chain · Composable Security · 6 Jan 2025 · Report ↗

Audits4

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
YieldNestSecurity firm: ZokyoDate: Scope: Repository at commit efda477None openFindings: None listedIPFS ↗
YieldNest Integration with Kernel on BNB ChainSecurity firm: Composable SecurityDate: Scope: Not recorded; see the reportNone openFindings: 1 high · 8 medium · 5 low
9 fixed · 5 acknowledged
GitHub ↗
YieldNestSecurity firm: ZokyoDate: Scope: Repository at commit be177b7None openFindings: 1 high · 2 medium
2 fixed · 1 acknowledged
IPFS ↗
YieldNest ProtocolSecurity firm: ChainSecurityDate: Scope: Files listedNone openFindings: 4 high · 2 medium · 8 low
14 fixed
chainsecurity.com ↗

Findings49

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

SeverityOpenAcknowledgedFixed
Critical000
High006
Medium039
Low0310

No open finding in these reports.

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

YieldNest: questions

Is YieldNest audited?

Trustblock holds 4 public audit reports for YieldNest, dated 19 Apr 2024 to 4 Feb 2025. The latest is by Zokyo (“YieldNest”).

Who audited YieldNest?

3 security firms wrote the reports Trustblock holds for YieldNest: Zokyo, Composable Security and ChainSecurity.

Are there open findings in YieldNest’s audits?

6 findings are still open or acknowledged in the firms’ reports: 3 medium, 3 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="yieldnest"
></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