Web3 · Smart Contract Audit

Oiler Security Audits

softstack has completed 3 smart contract audits for Oiler in May 2021, reporting 2 findings in total (2 low), of which 2 were resolved or mitigated before the final reports. Every report is published in the softstack public audit archive.

Key facts

Client
Oiler
Audits completed
3
First audited
Latest audit
Chains
Ethereum
Languages
Solidity

About the project

Oiler was a protocol for blockchain-native derivatives on Ethereum, built around variables observable on chain rather than off-chain asset prices. It depended on stablecoins and automated market makers for reliable pricing, infrastructure that only became available around 2019 and 2020. The oiler.network site no longer serves the application.

Findings

Combined across all 3 reviews softstack has completed for Oiler. Each report is broken out below.

0Critical
0High
0Medium
2Low
0Informational

2 of 2 findings resolved before the final reports.

Reports

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

  1. Staking smart contract audit

    · 1 file

    PDF
    0Critical
    0High
    0Medium
    2Low
    0Informational

    2 of 2 resolved

    Scope

    Components reviewed

    1 module · 1 file
    1. Staking.sol
    All 2 findings
    IDTitleSeverityStatus
    5.1.1A floating pragma is set

    Code Snippet Result/Recommendation The current pragma Solidity directive is ^0.8.3; It is recommended to specify a fixed version to ensure that the

    Lowfixed
    5.1.2Unsecure calculations

    Code Snippet Result/Recommendation The calculations could cause unhandled errors such as integer overflow.

    Lowfixed
  2. LBP Controller smart contract audit

    · 15 files

    PDF
    0Critical
    0High
    0Medium
    0Low
    0Informational

    No security findings reported.

    ScopeSource repositorygithub.com/balancer-labs/balancer-core

    Components reviewed

    14 modules · 15 files
    1. contracts/interfaces/ILBPController.sol
    2. contracts/interfaces/IUniswapV2Router02.sol
    3. contracts/interfaces/IUniswapV2Router01.sol
    4. contracts/lib/UniswapMath.sol
    5. contracts/lib/RightsManager.sol
    6. contracts/LBPController.sol
    7. contracts/abstracts/AbstractPool.sol
    8. contracts/abstracts/IERC20DecimalsExt.sol
    9. contracts/abstracts/BalancerOwnable.sol
    10. contracts/abstracts/CRPFactory.sol
    11. contracts/abstracts/ConfigurableRightsPool.sol
    12. contracts/abstracts/BRegistry.sol
    13. contracts/UniswapMigrator.sol
    14. contracts/Token.sol
  3. Vesting & Token smart contract audit

    · 7 files

    PDF
    0Critical
    0High
    0Medium
    0Low
    0Informational

    No security findings reported.

    Scope

    Components reviewed

    7 modules · 7 files
    1. contracts/Token/OilerToken.sol
    2. contracts/Token/Sacrifice.sol
    3. contracts/Distribution.sol
    4. contracts/IDistribution.sol
    5. contracts/IMultipleDistribution.sol
    6. contracts/MultipleDistribution.sol
    7. OilerToken.sol

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

Oiler 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 3 smart contract audits for Oiler in May 2021. The published reports are linked on this page and in the softstack public audit archive.

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

2 findings across all 3 reviews: 2 low. 2 of 2 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 May 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.