YoloRekt audit reports

YoloRekt has 1 public audit report from QuillAudits; dated 7 Mar 2022; 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 firm15

Statuses are the security firms’ own

15 findings are still open or acknowledged in the firms’ reports: 3 high, 5 medium, 7 low (3 open, 12 acknowledged).

High
3
Medium
5
Low
7
  • High Open

    Exploiting rewards#2

    YoloRekt · QuillAudits · 7 Mar 2022 · Report ↗

  • High Acknowledged

    Missing sanity value checks on amount in makeMarketBid

    YoloRekt · QuillAudits · 7 Mar 2022 · Report ↗

  • High Acknowledged

    Users can harvest more rewards than expected

    YoloRekt · QuillAudits · 7 Mar 2022 · Report ↗

  • Medium Acknowledged

    Centralization of withdraw

    YoloRekt · QuillAudits · 7 Mar 2022 · Report ↗

  • Medium Acknowledged

    ERC20Burnable comes with one more burn function that burnFrom

    YoloRekt · QuillAudits · 7 Mar 2022 · Report ↗

  • Medium Acknowledged

    Missing Address Validation

    YoloRekt · QuillAudits · 7 Mar 2022 · Report ↗

  • Medium Acknowledged

    Mutable URIs

    YoloRekt · QuillAudits · 7 Mar 2022 · Report ↗

  • Medium Acknowledged

    Possible manipulation of settlementPrice and nextStrikePrice:

    YoloRekt · QuillAudits · 7 Mar 2022 · Report ↗

  • Low Open

    Logical Code Optimization#1

    YoloRekt · QuillAudits · 7 Mar 2022 · Report ↗

  • Low Open

    Logical Code Optimization#2

    YoloRekt · QuillAudits · 7 Mar 2022 · Report ↗

All 15 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
YoloRektSecurity firm: QuillAuditsDate: Scope: Files listedNone openFindings: 13 high · 12 medium · 13 low
23 fixed · 12 acknowledged · 3 open
quillaudits.com ↗

Findings46

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

SeverityOpenAcknowledgedFixed
Critical000
High1210
Medium057
Low256
HighExploiting rewards#2YoloRekt · QuillAudits · 7 Mar 2022Open

Functions updateTracking and bumpDuringUpgrade are supposed to be called by NFTTracker and YoloNFTPack respectively. However, the modifier utilized i.e onlyAuthorized expands this capability to anyone having: • NFT_TRACKER or YOLO_NFT_PACK role in BiddersRewards • NFT_TRACKER or YOLO_NFT_PACK role in associated YoloRegistry of BiddersRewards • DEFAULT_ADMIN_ROLE or ADMIN_ROLE role in associated YoloRegistry of BiddersRewards can call the concerned functions. This widens up the attack surface, as authorized roles may take advantage of their privileged roles and may use these functions to exploit rewards.

Open the report
LowLogical Code Optimization#1YoloRekt · QuillAudits · 7 Mar 2022Open

Functions getCombinedLevelsWeighting and releaseFunds calculates weightage of every level as: rewardsMultiplier * (totalBidCount * COUNT_WEIGHT + totalCumulativeBidAmount * CUM_AMOUNT_WEIGHT) However, there is a strict condition, that rewardsMultiplier should be set for all the levels, and if any level’s rewardsMultiplier is not set, the entire function will revert. This can be optimized by making another memory array at the start, with a length same as nftLevelIdsListLength, and fetching and storing all the levels’ rewardsMultiplier. If any rewardsMultiplier is missing, the function can revert at this stage, without calculating the weightage of any level, thus reducing the number of operations and saving gas cost.

Open the report
LowLogical Code Optimization#2YoloRekt · QuillAudits · 7 Mar 2022Open

Functions getCombinedLevelsWeighting and releaseFunds calculates weightage of every level as: rewardsMultiplier * (totalBidCount * COUNT_WEIGHT + totalCumulativeBidAmount * CUM_AMOUNT_WEIGHT) However, the code can be optimized to calculate level weighting only if there exists any bid i.e.,  totalBidCount > 0, as it doesn’t make any sense to calculate level weighting if there exists no bid as the calculation will yield to 0 anyways.

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

YoloRekt: questions

Is YoloRekt audited?

Trustblock holds 1 public audit report for YoloRekt, dated 7 Mar 2022. The latest is by QuillAudits (“YoloRekt”).

Who audited YoloRekt?

QuillAudits wrote the report Trustblock holds for YoloRekt.

Are there open findings in YoloRekt’s audits?

15 findings are still open or acknowledged in the firms’ reports: 3 high, 5 medium, 7 low (3 open, 12 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="yolorekt"
></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