Skip to content
View ethever's full-sized avatar
🌴
On vacation
🌴
On vacation
  • Shenzhen China

Block or report ethever

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
ethever/README.md

English · 简体中文

ethever — Turning bytecode into behavior. Reverse engineering, EVM security, and program analysis.

ethever

Reverse Engineer · EVM Security · Program Analysis

Rust   EVM   Symbolic Execution   Reproducible Analysis

About

I'm ethever, a reverse engineer focused on Ethereum Virtual Machine (EVM) security and program analysis. I build Rust tooling to understand what smart contracts actually do — from bytecode and execution traces to state-dependent behavior, especially when source code or reliable contract metadata is unavailable.

My work brings together bytecode analysis, symbolic execution, and on-chain state. I care about both the reasoning behind a finding and the execution context needed to reproduce it.

Understand the behavior. Make the assumptions explicit. Reproduce the result.

What I work on

Area Questions I work on
Bytecode → semantics Recovering control flow, intermediate representations (IR), and contract behavior without source code.
Paths → constraints Combining symbolic and concrete execution, satisfiability modulo theories (SMT) solving, and concrete replay.
Tokens → state changes Understanding ERC-20 transfer fees, mint/burn behavior, permissions, and state-dependent rules.
State → security Analyzing DeFi interactions, cross-contract execution, and behavior against a specified chain state.

Current direction

I am working toward practical bytecode-level security analysis: preserving execution context, checking findings with concrete replay, and balancing exploration coverage with computational cost.

bytecode + chain state
          ↓
    execution & analysis
          ↓
inspectable behavior + reproducible traces

Tools I use

Layer Tools
Implementation Rust · Solidity · Linux
Execution & analysis Z3 · Foundry · Reth
Rules & data Datalog / Soufflé · DuckDB · Parquet
Reproducibility Nix · Git

How I approach analysis

  • Explicit assumptions. State what the analysis models and what it leaves out.
  • Evidence before claims. Separate observed behavior, modeled behavior, and hypotheses.
  • Reproducible results. Keep execution context and evaluate both coverage and computational cost.

Bytecode first. Behavior matters. Evidence over assumptions.

Popular repositories Loading

  1. rosetta-node rosetta-node Public

    Forked from dfinity/rosetta-node

    A passive node of the IC that can be interacted with using the Rosetta protocol

    Rust 1

  2. plug-coinflip plug-coinflip Public

    Forked from Psychedelic/plug-coinflip

    The coinflip is a sample project that showcases how applications can integrate Plug to authenticate users and use the PlugAgent through the IC Provider API!

    JavaScript 1

  3. eternity-ai-frontend eternity-ai-frontend Public archive

    The monorepo for eternity-ai frontend

    TypeScript 1

  4. blobl-mixer-test blobl-mixer-test Public

    blobl-mixer-test

    TypeScript 1

  5. test-state-machine-client test-state-machine-client Public

    Forked from dfinity/test-state-machine-client

    Rust library to interact with the ic-test-state-machine

    Rust 1

  6. qdrant qdrant Public

    Forked from qdrant/qdrant

    Qdrant - Vector Database for the next generation of AI applications. Also available in the cloud https://cloud.qdrant.io/

    Rust 1