Web3 · Smart Contract Audit

Bumper Finance Security Audits

softstack has completed 2 smart contract audits for Bumper Finance between October 2021 and December 2021, reporting 7 findings in total (1 medium, 1 low and 5 informational), of which 2 were resolved or mitigated before the final reports. Every report is published in the softstack public audit archive.

Key facts

Client
Bumper Finance
Audits completed
2
First audited
Latest audit
Chains
Ethereum
Languages
Solidity

About the project

Bumper was a decentralised price protection protocol built on Ethereum. Takers of protection paid a floating premium to set a floor price on crypto holdings, while makers deposited stablecoins into a liquidity reserve in return for that premium. The bumper.fi domain no longer resolves and the protocol appears to be discontinued.

Findings

Combined across all 2 reviews softstack has completed for Bumper Finance. Each report is broken out below.

0Critical
0High
1Medium
1Low
5Informational

2 of 7 findings resolved before the final reports.

Reports

Newest first. Every report covers its own scope and commit.

  1. Staking, Vesting, Airdrop smart contract audit

    · commit 22276af · 2 files

    PDF
    0Critical
    0High
    1Medium
    0Low
    3Informational

    1 of 4 resolved

    Scope

    Components reviewed

    2 modules · 2 files
    1. Vesting.sol
    2. Airdrop.sol
    All 4 findings
    IDTitleSeverityStatus
    5.1.1Locking and no rewards scenario

    Code Snippet Result/Recommendation If there is no reward sent to the contract, the contract can run out of balance.

    Mediumacknowledged
    5.1.2Public functions should be declared external

    Code Snippet Result/Recommendation In the current implementation several functions are declared as public where they could be external.

    Informationalacknowledged
    5.1.3Floating compiler versions

    Code Snippet Result/Recommendation The current pragma solidity directive is floating. It is recommended to specify a fixed compiler version to ensure that

    Informationalacknowledged
    5.1.4Using same require checks

    Code Snippet Result/Recommendation In the current implementation the same require checks are used multiple times at different

    Informationalfixed
  2. Protocol smart contract audit

    · 4 files

    PDF
    0Critical
    0High
    0Medium
    1Low
    2Informational

    1 of 3 resolved

    Scope

    Components reviewed

    4 modules · 4 files
    1. BumpMarketV2.sol
    2. BumperAccessControl.sol
    3. BUMPToken.sol
    4. TimeLockMechanism.sol
    All 3 findings
    IDTitleSeverityStatus
    5.1.1Upgrade chainlink AggregatorV3Interface to the newest version

    Code Snippet Result/Recommendation Old libraries can have bugs or vulnerabilities. import "@chainlink/contracts/src/v0.6/interfaces/ AggregatorV3Interface.sol"; It is recommended to upgrade the chainlink AggregatorV3Interface to the newest…

    Lowacknowledged
    5.1.2Fix Spelling and Grammatical Errors

    Code Snippet Result/Recommendation Spelling / Grammatical mistakes were identified in the codebase.

    Informationalfixed
    5.1.3ABIEncoder v2

    Code Snippet Result/Recommendation Solidity 0.8.0 has the ABI Encoder V2 activated by default. You can activate the old coder using pragma abicoder v1, or explicitly select v2 using pragma abicoder v2 - which has the same effect as pragma…

    Informationalacknowledged

About this engagement

A smart contract audit reviews on-chain code for flaws an attacker could exploit. Engineers trace how assets move through the contracts, check who can call privileged functions, and test the arithmetic, external calls and upgrade paths. Each finding is rated by severity, and fixes are re-checked before the final report.

How softstack runs smart contract audits

Methodology

Review process

  1. Scoping and threat modelling

    The commit hash is frozen and the attack surface is mapped: asset flows, trust assumptions, privileged roles and the external systems the code depends on.

  2. Automated analysis

    Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.

  3. Manual code review

    Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.

  4. Adversarial testing

    Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.

  5. Reporting

    Every finding is documented with a severity rating, its impact, the steps to reproduce it and a concrete remediation the team can act on.

  6. Remediation verification

    Submitted fixes are re-reviewed against the original finding, and the final report records the resolved state of each one.

Standards and references

  • SWC RegistrySmart Contract Weakness Classification
  • CWECommon Weakness Enumeration

FAQ

Bumper Finance was audited by softstack GmbH, a German Web3 security and software company based in Flensburg and certified to ISO/IEC 27001 by TÜV SÜD. softstack has completed 2 smart contract audits for Bumper Finance between October 2021 and December 2021. The published reports are linked on this page and in the softstack public audit archive.

2 separate reviews, the first in October 2021 and the most recent in December 2021. Each one covers its own scope and commit, and is listed individually on this page.

7 findings across all 2 reviews: 1 medium, 1 low and 5 informational. 2 of 7 were resolved or mitigated before the final reports.

Each report covers the code as it stood at the commit it names, the most recent in December 2021. Any code changed after that point is outside the reviewed scope.

Related audits

Browse all security audits

Disclaimer

This audit represents a point-in-time security assessment of the reviewed codebase and is intended for informational purposes only. While Softstack applies industry-standard security review methodologies, no audit can guarantee the absence of vulnerabilities, bugs, or other security risks. This report does not constitute financial, legal, regulatory, or investment advice, nor does it endorse the project, its business model, products, or services. Security is an ongoing process, and we strongly recommend conducting a new assessment following any material code changes or at least every 6 months to address newly emerging threats, vulnerabilities, and ecosystem developments.