OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Developer Tools

Madmax

Madmax is a command-line static-analysis tool that examines Ethereum smart contracts for gas-focused vulnerability patterns by analyzing Gigahorse intermediate representation lifted from bytecode.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Madmax — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Madmax when you have compiled Ethereum contract bytecode and want static-analysis findings for gas-focused patterns such as wallet griefing, unbounded mass operations and overflow loop iterators.

Who it is for

  • Ethereum smart-contract developers reviewing compiled contract artifacts.
  • Security and engineering teams processing one contract or a directory of contracts for gas-focused findings.

Documented uses

  • Analyze compiled Ethereum contract bytecode for gas-focused vulnerability patterns.
  • Review CSV and JSON outputs and check named result relations for individual contracts.
  • Use a command-line workflow to process a directory of compiled contracts.
Before you choose

Requirements & limits

Madmax is available as a public GitHub repository under the BSD-3-Clause license. Its documented use requires Gigahorse and its listed dependencies.

  • Inputs are compiled Ethereum bytecode files or directories of contracts.
  • Analysis runs through Gigahorse’s command-line tooling and uses Gigahorse’s intermediate representation.
  • Gigahorse installation requires the Souffle Datalog engine, custom functors and Boost.
  • The first run can take longer because Datalog files are compiled.
  • Some Madmax techniques are used in the separate Dedaub Watchdog deployment.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Run Madmax on compiled Ethereum contract bytecode

Analyze a compiled contract file or contract directory and inspect Madmax’s gas-focused vulnerability findings.

Before you start

  • A recursive clone of the Madmax repository, including its submodules.
  • Gigahorse installed according to its instructions, including the Souffle Datalog engine, custom functors and Boost.
  • A compiled Ethereum contract bytecode file or a directory of contracts.

Steps

  1. Clone the Madmax repository recursively.

  2. Install Gigahorse by following its installation instructions.

  3. Run gigahorse-toolchain/gigahorse.py -C madmax.dl , substituting the compiled contract file or directory.

  4. Review the printed summary and the output under .temp/**/out/*.csv and results.json; for an individual contract, check the WalletGriefing, UnboundedMassOp and OverflowLoopIterator relations.

Expected outcome

Madmax produces a command-line summary and CSV/JSON analysis results that can be checked for the named gas-focused vulnerability patterns.

Guide limitations

  • The README says the first run can take longer while Datalog files are compiled.
  • The documented input is compiled Ethereum contract bytecode, not source code.
  • Results identify patterns to review; the README does not describe them as a substitute for broader contract review.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
15 October 2026
Original website title
nevillegrech/MadMax · Official homepage title · retained in its source language
How we review sourcesSuggest a correction

Related options

Dedaub Watchdog — The Madmax README says some techniques developed in the project are used in Dedaub Watchdog; it is a separate deployment.