Sigvex
EVMWorkspace2 min read

EVM Studio

The full decompiler workspace for an EVM contract — disassembly, decompiled source, hex, call graph, and technical views side by side, with a function and cross-reference navigator.

Open EVM StudioAll guides
evmstudiodecompileride

EVM Studio is the workbench for reading a contract closely. It puts the decompiled source, the raw disassembly, the hex, the call graph, and the technical artifacts in one place, with a persistent navigator down the left so you can move between functions and cross-references without losing your spot.

Why it exists

Auditing bytecode means constantly switching between representations — you read the decompiled Solidity, drop to disassembly to check what the compiler actually emitted, look at storage layout, then trace a call. Doing that across separate pages is friction. Studio hosts every view together with consistent keyboard shortcuts, so the contract stays loaded and the context stays put as you jump between angles.

Who uses it

  • Auditor — reads the decompiled source and follows cross-references through the contract.
  • Researcher — works in disassembly and inspects the IR, storage, events, and metrics behind it.

How to open it

  1. From an EVM Contract Overview → the Studio breadcrumb action.
  2. From an asset card → Open in Studio.
  3. Direct URL — /evm-studio with a contract loaded.

Working in the studio

The left sidebar is the navigator: Functions, Cross References, Annotations, and Bookmarks, each on its own tab with its own letter shortcut. The centre holds the analysis views — Disassembly, Source, Hex, and Call Graph, plus technical sub-views for storage, IR, events, calls, and metrics. The number keys switch views directly; the letter keys switch sidebar panels. A Details panel on the right, toggled from the edge, shows the specifics of whatever you have selected.

Limits

  • Requires a signed-in account and a loaded contract.
  • The decompiled source is reconstructed from bytecode — it is a faithful approximation of what the contract does, not the original file the developer wrote.
  • The technical sub-views populate only when the underlying data exists, so a sparse view often just means a simple contract.