As of 19 Nov 2026, Block Agent has 1 audit report on Trustblock, by Resonance Security, dated 11 Apr 2024. That report lists 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 |
|---|---|---|---|---|---|
| BonusBlock | Security firm: Resonance Security | Date: | Scope: —Not recorded; see the report | 1 critical finding, fixed | IPFS ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 1 |
| High | 0 | 0 | 1 |
| Medium | 0 | 0 | 2 |
| Low | 0 | 0 | 1 |
Marked Info by the firms. Not counted as findings.
It was observed that the Bonusblock contracts do not leverage ERC165 standard. Using ERC165 assures that a contract deployed to a given address implements expected functionalities. It also indirectly performs a check for zero-address. Using ERC165 is not a requirement for a contract to be implemented correctly, however using it limits the impact of a human error during contract's configuration and it is considered a good practice.
Open the reportThe function safeMint() indirectly performs an arbitrary external call through ERC721's _safeMint(), and does not follow the Checks-Effects-Interactions pattern nor does it implement verification mechanisms against reentrancy, such as OpenZeppelin's ReentrancyGuard.While it does not present an immediate security threat as it is, when further functionality is introduced, possible reentrancy scenarios may occur that may ultimately lead to financial loss on the protocol.
Open the reportIt was observed that both RewardsBank and MyToken ERC721 contract implement a verifySignature function. The logic of these functions is the same in both contracts. In consequence, both contracts contain this functionality, which makes them more expensive to deploy and operate. Although it is not a security vulnerability, it is considered a best practice for code quality and gas optimization to keep the shared functionalities in a library so that it is only deployed once on-chain and code can be reused.
Open the reportFloating pragmas is a feature of Solidity that allows developers to specify a range of compiler versions that can be used to compile the smart contract code. For security purposes specifically, the usage of floating pragmas is discouraged and not recommended. Contracts should be compiled and deployed with a strict pragma, the one which was thoroughly tested the most by developers. Locking the pragma helps ensure that contracts do not accidentally get deployed using too old or too recent compiler versions that might introduce security issues that impact the contract negatively.It should be noted however that, pragma statements can be allowed to float when a contract is intended for consumption by other developers, as in the case with contracts in a library or EthPM package.The smart contracts of Bonusblock's protocol make use of floating pragmas. These are not intended for use as libraries for other developers and, as such, should be locked of their pragma.
Open the reportThe constructor of the contract possesses the keyword payable, which means Ether can be sent to the contract during its deployment. However, any sent Ether may not be claimed as there is no implemented functionality that allows it.It should be noted that the severity of this finding has been reduced due to the fact that this may only happen during the deployment of the smart contract and by mistake.
Open the reportIt was observed that the RewardsBank contract defines a calculatePercentage function, however this function is not used anywhere in 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="block-agent"></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