Architecture Explorer
A durable map of who controls what in a protocol — actors, controllers, and upgrade authority — derived from deployed bytecode and on-chain state, and versioned alongside the review it supports.
proxy VaultV2 (EIP-1967)
admin 0x4f2a…9c11 multisig
upgrade VaultV2, FeeRouter, Oracle
// one principal, three upgradeable contracts
Authority, resolved from the chain
The Explorer reads the storage slots that actually hold authority on a pinned fork, then classifies each controller it finds — externally owned account, multisig, timelock, governance, or contract. Controllers that appear across several contracts collapse into a single principal, so concentration is visible instead of implied.
- Readsstorage slots on a pinned fork
- Sourceoptional; verified ABIs enrich the map
- Resolvesactors, controllers, upgrade authority
- Outputa revisioned map with immutable snapshots
Rules that run, and paths you can follow
Structural rules run over the graph and surface the shapes that matter in a review — a single key behind an upgrade, authority that concentrates on one principal, a path from an external caller to a privileged function. Each result is a route through the model you can walk, not a severity label.
Versioned
The map is a revisioned document with immutable snapshots and an audit trail, so a review can cite the exact architecture it was performed against.
Reconciled
Replay a transaction on the fork and its real execution is compared against the model — edges confirmed, unexpected, or never observed.
Shared
Developers and auditors read the same map alongside the same fork, findings, and contract context.
Map the protocol before you review it
Open a target and the architecture is built from what is deployed.