As of 19 Nov 2026, BlockGuard has 2 audit reports by 1 security firm on Trustblock; the latest is by Resonance Security, dated 6 May 2025. Those reports list no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Newest first
| Report | Security firm | Date | Scope | Critical findings | Source |
|---|---|---|---|---|---|
| BlockGuard Fusio Token Smart Contract | Security firm: Resonance Security | Date: | Scope: —Not recorded; see the report | None open | GitHub ↗ |
| BlockGuard | Security firm: Resonance Security | Date: | Scope: —Not recorded; see the report | None open | IPFS ↗ |
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 | 0 |
| Low | 0 | 0 | 0 |
Marked Info by the firms. Not counted as findings.
The report gives no description here.
Open the reportThe compiler for Solidity 0.8.20 switches the default target EVM version to Shanghai, which includes the new PUSH0 op code. This op code may not yet be implemented on all L2s, so deployment on these chains may fail.The command forge build --force --extra-output evm.bytecode.opcodes will print the used opcodes in out/FusioToken.sol/FusioToken.json, where it is possible to search for the push0 opcode.
Open the reportThe report gives no description here.
Open the reportThe project uses floating pragmas ^0.8.20.This may result in the contracts being deployed using the wrong pragma version, which is different from the one they were tested with. For example, they might be deployed using an outdated pragma version which may include bugs that affect the system negatively.
Open the reportThe report gives no description here.
Open the reportThe upgradeable contract does not have a storage gap for future upgrades. This may cause new variables in upgraded contracts to collide with existing storage, should the contract be extended and inherited as a base contract from other contracts.
Open the reportThe report gives no description here.
Open the reportTwo different syntaxes for importing contracts from external libraries or dependencies are used in Solidity:import "@openzeppelin/contracts/token/ERC20/ERC20.sol";import {ERC20} from “@openzeppelin/contracts/token/ERC20/ERC20.sol”Second syntax allows developers to selectively import specific contracts from a file and provides finer control over which contracts are being imported. This could be useful for reducing namespace clutter or importing only necessary code for the contract.
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="blockguard"></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