BlockGuard

Resonance SecurityCode version: not recorded (see the report)

Audit · firm’s term: audit report

Resonance Security reviewed BlockGuard on 6 May 2025: no findings reported.

No open critical findings
Open the reportOpen BlockGuard’s security record
Report stored on IPFS. Content hash QmXxv7ZGeH6bUXqymYTLkCpL1Uadf5v2ChCiwk6Pk9T6g1

Trustblock does not review code.

Findings4

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium000
Low000

Marked Info by the firm. Not counted as findings.

InfoSolidity Version 0.8.20 Incompatibilities Due To PUSH0Acknowledged

The 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.

InfoFloating PragmaFixed

The 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.

InfoStorage Collision RiskFixed

The 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.

InfoUpdate Import Usages To Add ModularityFixed

Two 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.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Part of BlockGuard’s security record

BlockGuard
Audits2 audits by 1 firmLast audit May 2025, by Resonance Security.
Critical findingsNo open critical findingsAcross 2 reports.
Open BlockGuard’s security record

Security firm

Resonance Security

27 projects reviewed · 57 reports · latest Dec 2025

See Resonance Security’s audits

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