# Auditing IDE

> The Auditing IDE works on transactions, calldata, and storage against a live fork you control: Composer, Scanner, MorphVM, storage, graph, and decoding panels.

Platform

The panels for working a target: compose transactions as any sender, read storage slot by slot, and trace what actually executed.

The Auditing IDE

## Every panel a security engineer expects — rebuilt for the EVM, plus Solana program scanning and tracing

The layout is deliberately familiar. Where a web proxy works on HTTP requests, the Auditing IDE works on transactions, calldata, and storage — against a live environment you control.

- Works on: transactions, calldata, storage
- Runs against: a live fork (EVM) or captured account state (Solana)
- Panels: Composer, Scanner, MorphVM, and six more
- Output: a finding, proven by replay

Target

Every contract in scope, with **selectors grouped per contract** — proxies, implementations, and linked contracts resolved into one map of the attack surface.

Composer

Compose a transaction and send it **as any address** — no keys needed on a fork. Inspect the full result, revert reason, and step-level debug trace.

Scanner

**Static detectors** plus execution-validated checks. A candidate only becomes a finding when its proof-of-concept replays successfully on the fork.

Graph

Interactive **control-flow graph** of the deployed bytecode — computed jumps resolved, orphan blocks surfaced, paths traceable selector by selector.

Storage

Slot-level storage layout with **mapping-key math done for you**. Watch reads and writes flow through a transaction to see exactly what state a finding depends on.

Heap

A **heap-and-stack view of every selector**: memory allocations, mapping regions, and reachable state — the runtime picture next to the static one.

Decoder

Calldata, returndata, and event decoding backed by a **function-selector database** — paste raw bytes, get back what the contract actually saw.

MorphVM

Some contracts hide their logic behind a **custom byte-VM dispatcher**. MorphVM lifts the obfuscated dispatcher into readable logic so you can audit what it really does.

Blocks

Per-block analysis: **which selectors can reach a block**, what state it touches, and where a computed jump can land. The view auditors use to chase odd paths.

On Solana

## The Scanner and execution tracing are available on Solana (SVM) — the remaining panels are EVM concepts

- Unit: a program and the accounts it touches
- Source: Rust, read and analyzed; no Anchor toolchain, so nothing is compiled
- Available: Scanner with twenty program detectors; execution tracing
- Not available: Composer instruction building, Graph, Storage, Heap, Decoder, MorphVM, Blocks — EVM bytecode concepts
- Evidence: compute units, logs and account diffs; SARIF export

## Every finding, replayed.

A candidate becomes a finding only when its proof-of-concept reproduces against the pinned fork.

[Launch app](https://app.trilocore.ai/) [Analysis engine](https://trilocore.com/platform/analysis-engine) [Read the docs](https://platform.trilocore.com/docs/en/auditing-ide/)

---

[Canonical HTML version](https://trilocore.com/platform/auditing-ide)