proxy-inspect

Analyze smart contract proxy patterns via EIP-1967 storage slots and bytecode.

1|Updated Feb 26, 2026

Search Tags:#security #audit #smart contract #proxy #foundry #upgradeability #eip-1967

Ready to run

npx skills add https://github.com/0xHoneyJar/construct-protocol --skill proxy-inspect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: proxy-inspect
Source: https://github.com/0xHoneyJar/construct-protocol/tree/main/skills/proxy-inspect
Command: npx skills add https://github.com/0xHoneyJar/construct-protocol --skill proxy-inspect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you understand the underlying architecture of proxy contracts, identify the actual implementation code, and determine who has the authority to upgrade them, crucial for security and auditing.

Core Features & Use Cases

Proxy Identification: Detects various proxy patterns like Transparent, UUPS, Beacon, and Minimal proxies.
Implementation Discovery: Finds the address of the contract logic being executed.
Upgrade Authority Analysis: Traces the chain of control for contract upgrades, identifying risks associated with EOAs, multisigs, or timelocks.
Use Case: Before interacting with a DeFi protocol's main contract, use this Skill to verify its proxy pattern and ensure that upgrade authority is held by a secure multisig or timelock, not a single EOA.

Quick Start

Inspect the proxy contract at address 0x123...abc on mainnet to understand its architecture and upgrade controls.

Frequently Asked Questions about proxy-inspect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify the proxy pattern of a smart contract?▼

To identify a smart contract proxy pattern, you read EIP-1967 storage slots and analyze bytecode to detect types like Transparent, UUPS, Beacon, Diamond, or Minimal proxies.

How do I find the implementation address of an EIP-1967 proxy?▼

Finding the implementation address of an EIP-1967 proxy requires reading specific storage slots to uncover the actual contract logic being executed behind the proxy architecture.

How do I trace the upgrade authority chain for a UUPS or Transparent proxy?▼

Tracing the upgrade authority chain for UUPS or Transparent proxies involves identifying the admin or owner address and assessing security risks associated with EOAs, multisigs, or timelocks.

Can I audit proxy upgradeability risks using Foundry?▼

Yes, you can audit proxy upgradeability risks using Foundry by analyzing EIP-1967 storage slots and contract bytecode to assess security risks associated with the upgrade mechanisms.

What is the difference between Beacon and Diamond proxy patterns?▼

Beacon proxies route logic through a shared beacon contract, whereas Diamond proxies use EIP-2535 facets for modular logic, both identifiable by reading specific storage slots and bytecode.

Why should I check proxy admin ownership before interacting with a DeFi protocol?▼

Checking proxy admin ownership is crucial before interacting with a DeFi protocol to verify that upgrade authority is held by a secure multisig or timelock, mitigating unauthorized upgrade risks.