As of 14 Oct 2026, NetMind has 1 audit report on Trustblock, by Quantstamp, dated 4 Aug 2024. That report lists no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Statuses are the security firms’ own. Trustblock does not review code.
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| NetMind | Security firm: Quantstamp | Date: | Scope: Repository at commit d52de61 | No open critical findings | Open · certificate.quantstamp.com |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 2 | 3 |
| Medium | 0 | 5 | 3 |
| Low | 1 | 7 | 4 |
<br> 1. qs-badge-fixed `AccountManage.updateSignNum()` does not validate that `signNum` is set to a value greater than a reasonable minimum. If `signNum` is zero, anyone can transfer the `providerFeeSum` amount of NMT tokens from the `AccountManage` contract to any address without valid signatures. 1. qs-badge-fixed `CommunityFund.updateLockTime()` does not validate that `LockTime` is within reasonable bounds. If `LockTime` is set far in the past, all funds could immediately become releaseable. Alternatively, if `LockTime` is set far in the future, no funds will be releasable until the `LockTime` is reached. 1. qs-badge-fixed `FinanceToken.launch()` does not validate: 1. A reasonable upper bound for `investmentPeriod`. The `sponsor` cannot initiate a `refund()` if set to a sufficiently high value. 1. A reasonable upper bound for `unlockIntervalDays`. If set to a sufficiently high value, the purchasers may never be able to withdraw all of their NMT tokens. 1. `unlockPercentage` is greater than zero. Purchasers cannot withdraw any of their NMT tokens if set to zero. 1. qs-badge-fixed `LongTermPledge.updateLockPeriod()` does not validate that `lockPeriod` is set to a value less than a reasonable maximum. If `lockPeriod` is set to a large value, users can never unstake their tokens. 1. qs-badge-acknowledged `Purchase.swapToken()` does not validate `_minOut`, which means it can be specified as zero and support unlimited slippage exposing this contract to the vulnerability of a sandwich attack upon swap. 1. qs-badge-acknowledged `RewardPool.init()` and `RewardPool.setSigNum()` do not validate that `SigNum` is set to a value greater than a reasonable minimum. If `SigNum` is set to zero, anyone can call `move()` or `burn()` without valid signatures. 1. qs-badge-fixed `StrategicFund.updateLockTime()` does not validate that `LockTime` is within reasonable bounds. If `LockTime` is set far in the past, all funds could immediately become releaseable. Alternatively, if `LockTime` is set far in the future, no funds will be releasable until the `LockTime` is reached. 1. qs-badge-fixed `TechnologyFund.updateLockTime()` does not validate that `LockTime` is within reasonable bounds. If `LockTime` is set far in the past, all funds could immediately become releaseable. Alternatively, if `LockTime` is set far in the future, no funds will be releasable until the `LockTime` is reached.
Open the reportThe reports name a repository or files. Open a report to see its scope.
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.
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.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="netmind"></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