Reactive Network security record
As of 3 Nov 2026, Reactive Network has 1 audit report on Trustblock, by QuillAudits, dated 11 Feb 2025. 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.
Audits1
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Reactive Network | Security firm: QuillAudits | Date: | Scope: Files named in the report | No open critical findings | Open · quillaudits.com |
Findings5
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 2 |
| Medium | 1 | 0 | 1 |
| Low | 1 | 0 | 0 |
MediumLack of Refund Mechanism on Failed Transfers in Bridge to Bridge Interaction ScenarioReactive Network · QuillAudits · 11 Feb 2025Open
In the current bridge implementation, once a transfer message is confirmed and successfully relayed from the source bridge to the destination bridge, the user's funds are effectively deducted from the source chain. However, if the transaction fails on the destination bridge due to any factors, the bridge does not provide a mechanism to refund the user’s assets.This issue specifically arises in BRIDGE <-> BRIDGE interactions, where one bridge communicates directly with another bridge without involving the ReactiveBridge (RNBRIDGE). Since BRIDGE <-> RNBRIDGE interactions are the intended, the lack of a refund mechanism is only a concern when bridges interact directly with each other. In such cases, users may face an irreversible loss of funds, exposing them to financial risk.
Open the reportLowLack of Test Coverage in the Bridge ContractReactive Network · QuillAudits · 11 Feb 2025Open
The bridge contract currently lacks a comprehensive testing suite, which poses significant risks to its reliability, security, and functionality. Without unit and integration tests, there is no systematic way to verify that the contract behaves as intended across different scenarios, including edge cases and failure conditions. This absence of testing increases the likelihood of undetected vulnerabilities, incorrect logic implementation, and potential financial losses due to undiagnosed bugs.
Open the reportContracts
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
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.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="reactive-network"></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