Surge Protocol audit reports

Ethereum, BNB Chainsurgeprotocol.io

Surge Protocol has 3 public audit reports from SolidProof and Cyberscope; the latest is Cyberscope, 18 Apr 2023; no critical findings reported. It also holds 3 deployed contracts on 2 chains.

Critical findings
No open critical findings
Across 3 reports.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm10

Statuses are the security firms’ own

10 findings are still open or acknowledged in the firms’ reports: 10 low (all open).

Low
10
  • Low Open

    AAO - Accumulated Amount Overflow

    Surge Protocol · Cyberscope · 18 Apr 2023 · Report ↗

  • Low Open

    CR - Code Repetition

    Surge Protocol · Cyberscope · 18 Apr 2023 · Report ↗

  • Low Open

    DDP - Decimal Division Precision

    Surge Protocol · Cyberscope · 18 Apr 2023 · Report ↗

  • Low Open

    L04 - Conformance to Solidity Naming Conventions

    Surge Protocol · Cyberscope · 18 Apr 2023 · Report ↗

  • Low Open

    L13 - Divide before Multiply Operation

    Surge Protocol · Cyberscope · 18 Apr 2023 · Report ↗

  • Low Open

    MU - Modifiers Usage

    Surge Protocol · Cyberscope · 18 Apr 2023 · Report ↗

  • Low Open

    PRL - Potential Reentrance Leverage

    Surge Protocol · Cyberscope · 18 Apr 2023 · Report ↗

  • Low Open

    #1: Contract doesn’t import npm packages from source (like OpenZeppelin etc.)

    SURGE · SolidProof · 14 Jan 2023 · Report ↗

  • Low Open

    #2 sender.: This is the behaviour how the contract should work.

    SURGE · SolidProof · 14 Jan 2023 · Report ↗

  • Low Open

    #1: Contract doesn’t import npm packages from source (like OpenZeppelin etc.)

    SURGE · SolidProof · 12 Jan 2023 · Report ↗

Audits3

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Surge ProtocolSecurity firm: CyberscopeDate: Scope: 1 address on BNB ChainNone openFindings: 7 low
7 open
IPFS ↗
SURGESecurity firm: SolidProofDate: Scope: 3 addresses on Ethereum and BNB ChainNone openFindings: 2 low
2 open
IPFS ↗
SURGESecurity firm: SolidProofDate: Scope: Not recorded; see the reportNone openFindings: 1 low
1 open
IPFS ↗

Findings12

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium000
Low1000
LowAAO - Accumulated Amount OverflowSurge Protocol · Cyberscope · 18 Apr 2023Open

The report gives no description here.

Open the report
LowCR - Code RepetitionSurge Protocol · Cyberscope · 18 Apr 2023Open

The report gives no description here.

Open the report
LowDDP - Decimal Division PrecisionSurge Protocol · Cyberscope · 18 Apr 2023Open

The report gives no description here.

Open the report
LowL04 - Conformance to Solidity Naming ConventionsSurge Protocol · Cyberscope · 18 Apr 2023Open

The report gives no description here.

Open the report
LowL13 - Divide before Multiply OperationSurge Protocol · Cyberscope · 18 Apr 2023Open

The report gives no description here.

Open the report
LowMU - Modifiers UsageSurge Protocol · Cyberscope · 18 Apr 2023Open

The report gives no description here.

Open the report
LowPRL - Potential Reentrance LeverageSurge Protocol · Cyberscope · 18 Apr 2023Open

The report gives no description here.

Open the report
Low#1: Contract doesn’t import npm packages from source (like OpenZeppelin etc.)SURGE · SolidProof · 14 Jan 2023Open

The report gives no description here.

Open the report
Low#2 sender.: This is the behaviour how the contract should work.SURGE · SolidProof · 14 Jan 2023Open

The report gives no description here.

Open the report
Low#1: Contract doesn’t import npm packages from source (like OpenZeppelin etc.)SURGE · SolidProof · 12 Jan 2023Open

The report gives no description here.

Open the report

Contracts3

AddressChainSource code
0xcd682ef09d07668d49a8103ddd65ff54aebfbfdeChain: EthereumSource code: Verified source
0x564ea1fcf1ba9ebd151ec3f34208cfaf1062f524Chain: EthereumSource code: Verified source
0x9f19c8e321bd14345b797d43e01f0eed030f5bffChain: BNB ChainSource code: Verified source

Surge Protocol: questions

Is Surge Protocol audited?

Trustblock holds 3 public audit reports for Surge Protocol, dated 12 Jan 2023 to 18 Apr 2023. The latest is by Cyberscope (“Surge Protocol”).

Who audited Surge Protocol?

2 security firms wrote the reports Trustblock holds for Surge Protocol: SolidProof and Cyberscope.

Are there open findings in Surge Protocol’s audits?

10 findings are still open or acknowledged in the firms’ reports: 10 low (all open). No critical finding is reported. Statuses are the security firms’ own.

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="surge-protocol"
></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