YieldNest
Audit · firm’s term: smart contract review
Zokyo reviewed YieldNest on 4 Feb 2025: 7 findings, 0 critical; 3 marked fixed, 4 acknowledged.
No open critical findings
Open the reportOpen YieldNest’s security record
Report stored on IPFS. Content hash QmPnyJm4TMbUzHnFU1qafc3GT5kfou2XECSTGZMgpAhUCq
Trustblock does not review code.
Findings7
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 4 | 3 |
LowCache the state value into a memoryFixed
The report gives no description here.
LowMissing a zero address checkFixed
The report gives no description here.
LowPayable modifier could be removedFixed
The report gives no description here.
Contracts in scope
No deployed address is recorded for this audit.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (6)
- https://github.com/yieldnest/yieldnest-protocol/src/ynEIGEN/TokenStakingNodesManager.sol at commit efda4776f5a043003f45795853969cec90e0c2ac
- https://github.com/yieldnest/yieldnest-protocol/src/ynEIGEN/EigenStrategyManager.sol at commit efda4776f5a043003f45795853969cec90e0c2ac
- https://github.com/yieldnest/yieldnest-protocol/src/lib/ArrayLib.sol at commit efda4776f5a043003f45795853969cec90e0c2ac
- https://github.com/yieldnest/yieldnest-protocol/src/ynEIGEN/TokenStakingNode.sol at commit efda4776f5a043003f45795853969cec90e0c2ac
- https://github.com/yieldnest/yieldnest-protocol/src/StakingNodesManager.sol at commit efda4776f5a043003f45795853969cec90e0c2ac
- https://github.com/yieldnest/yieldnest-protocol/src/StakingNode.sol at commit efda4776f5a043003f45795853969cec90e0c2ac
Part of YieldNest’s security record
YieldNestAudits3 audits by 2 firmsLast audit Feb 2025, by Zokyo.
Critical findingsNo open critical findingsAcross 3 reports.
Open YieldNest’s security recordSecurity firm
Zokyo89 projects reviewed · 131 reports · latest Feb 2025
See Zokyo’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