Control has a trail.
A 3-of-5 governance multisig controls the proxy admin. Follow the path to understand who can change the system.
WEB3 SMART CONTRACT REVERSE ENGINEERING
Reverse engineer smart contracts.
Inspect bytecode, uncover proxy links, and map on-chain control from any contract address.
◈Start with code.
Follow every clue.
Follow every clue.
Read-only smart contract investigation. No wallet connection needed.
RPC connection settings
Reads are sent to the selected RPC provider. Use a browser-compatible endpoint; no wallet required.
Atlas Protocol SAMPLE ANALYSIS
Ethereum ·
0x7a24…bE31✓ Source availableConnected contracts06 across the system
Privileged roles03 Review permissions
UpgradeabilityUpgradeable Proxy pattern
Analysis scopeIllustrative Demo data only
System map 6 nodes
The architecture, at a glance.
ownsupgradesdepositsroutes assets
Contract details
↗Atlas Vault
PROXY CONTRACT
The protocol’s front door. Accepts asset deposits and issues vault shares, while delegating execution to its implementation.
Contract typeERC-1967 proxy
Source statusIllustrative sample
NetworkEthereum
Function selector candidates
PUSH4 constants extracted from bytecode. Suggested signatures are guesses, may collide, and are not a verified ABI.
A clearer picture
Three things this map tells youFollow the money.
Assets enter the vault and move into a strategy. Vault shares represent a depositor’s position.
One address, two layers.
The vault’s address stays fixed while its implementation can change. The map separates access from execution.
Saved analyses
SMART CONTRACT REVERSE ENGINEERING
What can you uncover from deployed code?
ReLens is a Web3 reverse-engineering workspace. Start with a contract address and investigate the evidence the chain exposes.
01 — Inspect deployed bytecode
Read the contract’s bytecode and balance at a fixed block. PUSH4 constants are surfaced as possible function selectors to guide further investigation; they are guesses, not a recovered ABI.
02 — Find proxy and control links
Check standard proxy slots, minimal proxy patterns, beacon targets, and owner() responses to map relationships between contracts and addresses.
03 — Follow the evidence
Inspect raw RPC responses, save a snapshot in this browser, or export the evidence as JSON. The Atlas sample is fictional; live snapshots are labeled with their block number.
ReLens is an investigative starting point. It does not currently decompile Solidity, retrieve verified source, trace transactions, or produce an audit verdict.