BlockGuard

Resonance Security6 May 2025Code version: not recorded (see the report)

Audit · firm’s term: audit report

Resonance Security reviewed BlockGuard on 6 May 2025: 4 findings, 0 critical; 3 marked fixed, 1 open.

No open critical findings

Open the report Open 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.

Severity	Open	Fixed
Critical	0	0
High	0	0
Medium	0	0
Low	1	3

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

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

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