Block Agent security record

Arbitrum, Basebonusblock.io

As of 29 Oct 2026, Block Agent has 1 audit report on Trustblock, by Resonance Security, dated 11 Apr 2024. That report lists no open critical findings.

Critical findings
No open critical findings
In that report, 1 critical finding was reported. It is marked fixed by the firm that reported it. See the findings
Open the latest report
Your label, live
Get the label for your site

Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.

Audits1

Newest first

AuditSecurity firmDateScopeCritical findingsReport
BonusBlockSecurity firm: Resonance SecurityDate: Scope: Not recorded (see the report)1 critical finding, fixedOpen · IPFS

Findings11

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

SeverityOpenAcknowledgedFixed
Critical001
High001
Medium002
Low304
LowMissing Usage Of ERC165 StandardBonusBlock · Resonance Security · 11 Apr 2024Open

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 report
LowPossible Reentrancy In safeMint()BonusBlock · Resonance Security · 11 Apr 2024Open

The 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 report
LowRedundant Code On verifySignature()BonusBlock · Resonance Security · 11 Apr 2024Open

It 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 report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

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

Facts

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.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-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