Bloq security record

As of 19 Nov 2026, Bloq has 2 audit reports by 1 security firm on Trustblock; the latest is by Resonance Security, dated 5 Oct 2023. Those reports list no open critical findings.

Critical findings
No open critical findings
Across 2 reports.
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 Nov 2026. Trustblock does not review code.

Audits2

Newest first

ReportSecurity firmDateScopeCritical findingsSource
Bloq Metronome Synth Cross-Chain IntegrationSecurity firm: Resonance SecurityDate: Scope: Not recorded; see the reportNone openGitHub ↗
BloqSecurity firm: Resonance SecurityDate: Scope: Not recorded; see the reportNone openIPFS ↗

Findings18

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium044
Low022

Marked Info by the firms. Not counted as findings.

InfoCode Duplication Between Manageable And Pauseable ContractsBloq Metronome Synth Cross-Chain Integration · Resonance Security · 5 Oct 2023Acknowledged

The report gives no description here.

Open the report
InfoCode Duplication Between Manageable And Pauseable ContractsBloq · Resonance Security · 5 Oct 2023Acknowledged

The smart contracts Manageable and Pauseable implement the same functionality and could be adapted to remove the inherent duplication of code. Avoiding code duplication makes the code more readable for the smart contracts' users and saves gas during deployment.

Open the report
InfoHardcoded Zero Address As zroPaymentAddressBloq Metronome Synth Cross-Chain Integration · Resonance Security · 5 Oct 2023Acknowledged

The report gives no description here.

Open the report
InfoHardcoded Zero Address As zroPaymentAddressBloq · Resonance Security · 5 Oct 2023Acknowledged

The LayerZero protocol specification requires that whenever cross-chain estimates are being made or messages being sent, the input parameter zroPaymentAddress should not be hardcoded. This is due to the fact that different chains may have different implementations of the zero address, and, as such, this variable should be passed in as an argument by the user, and should not be hardcoded.It should be noted that the impact for this finding is specific to the respective chains being included and implemented in the protocol.

Open the report
InfoUnnecessary Modifier onlyIfSyntheticTokenIsActive On flashIssue()Bloq Metronome Synth Cross-Chain Integration · Resonance Security · 5 Oct 2023Fixed

The report gives no description here.

Open the report
InfoUnnecessary Modifier onlyIfSyntheticTokenIsActive On flashIssue()Bloq · Resonance Security · 5 Oct 2023Fixed

According to the code workflow implemented on the protocol, the modifier onlyIfSyntheticTokenIsActive being used on the function flashIssue() is not necessary since similar validations are already being made on the same smart contract interaction. This optimizes the code to save on gas during execution.

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="bloq"
></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