Solidus Ai Tech security record
As of 30 Oct 2026, Solidus Ai Tech has 4 audit reports by 2 security firms on Trustblock; the latest is by CertiK, dated 12 Feb 2025. Those reports list no open critical findings. It also holds 1 deployed contract on 1 chain.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Audits4
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Vision Makers | Security firm: CertiK | Date: | Scope: Files named in the report | No open critical findings | Open · skynet.certik.com |
| SOLIDUS AI TECH / Gpu-Blockchain-Smartcontra | Security firm: Hacken | Date: | Scope: 1 address on BNB Chain | No open critical findings | Open · hacken.io |
| SOLIDUS AI TECH / ERC20 | Security firm: Hacken | Date: | Scope: 1 address on BNB Chain | No open critical findings | Open · hacken.io |
| Ai-Tech - Revised | Security firm: CertiK | Date: | Scope: Files named in the report | No open critical findings | Open · skynet.certik.com |
Findings25
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 1 | 2 | 1 |
| Medium | 0 | 0 | 5 |
| Low | 2 | 4 | 10 |
HighCentralization Related RisksAi-Tech - Revised · CertiK · 14 Jun 2022Open
In the contract `AITECH`, the role `MINTER` has authority over the following functions: - function mint() In the contract `AITECH`, the role `BURNER` has authority over the following functions: - function burn() - function burnFrom() Any compromise to the `MINTER/BURNER` accounts may allow a hacker to take advantage of this authority.
Open the reportLowFloating PragmaSOLIDUS AI TECH / Gpu-Blockchain-Smartcontra · Hacken · 26 Jul 2024Open
The report gives no description here.
Open the reportLowUnlocked Compiler VersionAi-Tech - Revised · CertiK · 14 Jun 2022Open
The contract has unlocked compiler version. An unlocked compiler version in the source code of the contract permits the user to compile it at or above a particular version. This, in turn, leads to differences in the generated bytecode between compilations due to differing compiler version numbers. This can lead to an ambiguity when debugging as compiler specific bugs may occur in the codebase that would be hard to identify over a span of multiple compiler versions rather than a specific one.
Open the reportContracts1
| Address | Chain | Source code |
|---|---|---|
| 0x2d060ef4d6bf7f9e5edde373ab735513c0e4f944 | Chain: BNB Chain | Source code: Verified source |
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="solidus-ai-tech"></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