Spectra Bridge
Certora reviewed Spectra (Spectra Bridge) on 18 May 2026: 10 findings, 0 critical; 9 marked fixed, 1 acknowledged.
Report hosted on GitHub.
Trustblock does not review code.
Findings10
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 4 |
| Low | 0 | 1 | 5 |
MediumInconsistent rate limit handling between EVM and Soroban can permanently strand Inbound stellar messagesFixed
The report gives no description here.
MediumMessenger protocol changing can leave stranded inbound messagesFixed
The report gives no description here.
MediumMutable bridge fees can cause users to pay higher fees than expectedFixed
The report gives no description here.
MediumStranded gas tokens inside the messengerFixed
The report gives no description here.
LowBridge messages with zero address recipient can cause permanent loss of fundsFixed
The report gives no description here.
LowCaller is always the refund receiverFixed
The report gives no description here.
LowDeterministic oracle deployment can be front-run by an attacker causing DoSFixed
The report gives no description here.
LowInconsistent usage of transaction valueFixed
The report gives no description here.
LowMissing TTL extension for persistent storage DataKey entries can lead to DoS.Fixed
The report gives no description here.
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 Spectra’s security record
SpectraSecurity firm
Certora9 projects reviewed · 17 reports · latest Jun 2026
See Certora’s auditsSomething 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