Prime Numbers Labs security record
As of 26 Oct 2026, Prime Numbers Labs has 1 audit report on Trustblock, by QuillAudits, dated 7 Apr 2025. That report lists no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Audits1
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Prime Number Staking Contract | Security firm: QuillAudits | Date: | Scope: Files named in the report | No open critical findings | Open · quillaudits.com |
Findings7
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 2 |
| Low | 2 | 0 | 3 |
LowIncorrect Use of Custom Errors with require StatementsPrime Number Staking Contract · QuillAudits · 7 Apr 2025Open
The contract defines custom errors like ZeroStakeAmount(), RewardApyTooHigh(), and others. These are intended to be used as a clearer and more efficient alternative to revert strings. However, in multiple places, these errors are incorrectly passed as arguments to require(): require(amount > 0, ZeroStakeAmount()); // incorrect This is not the correct pattern for using custom errors. According to Solidity documentation, custom errors should be used with an if statement followed by a revert: if (amount == 0) revert ZeroStakeAmount(); // correct Using require(..., CustomError()) still compiles because custom errors are interpreted as expressions, but this pattern is invalid as it leads to inconsistent error handling and poor readability.
Open the reportLowMissing Checks for Math Operation Failures in Reward LogicPrime Number Staking Contract · QuillAudits · 7 Apr 2025Open
Throughout the reward calculation logic in the contract, the code uses Solidity’s tryAdd, trySub, and<br>tryMul functions from the Math library to perform arithmetic operations. These functions return a (bool success, uint256 result) and in the current implementation, the success flag is ignored in most cases.<br>(bool success, uint256 result) = rewardPerToken().trySub(s.userRewardPerTokenPaid[account]);<br>(success, result) = result.tryMul(balanceOf(account));<br>(success, result) = result.tryDiv(WHOLE);<br>(success, result) = result.tryAdd(_rewards[account]);<br>
Open the reportContracts
No deployed address is recorded for these audits.
The reports name a repository or files. Open a report to see its scope.
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
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.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="prime-numbers-labs"></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