evm contract control audit

    1

    Audit who controls an EVM contract: map owners, proxy-upgrade admins, Safe signers and thresholds, timelock delays and AccessControl roles, and simulate privileged admin calls from on-chain state. Read-only.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    evm contract control audit

    Example session with this skill installed

    Audit the admin surface for the contract at 0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640 on Uniswap V3 (Ethereum). Tell me who can upgrade it and if there are any EOA admins.

    • Read your context and instructions
    • Compiled the evm contract control

    I have performed a read-only audit of the admin surface for the specified Ethereum contract. Please note that this is a chain view of the current state and not a verdict on protocol security.

    Admin Surface Audit: 0x88e6a0c2...

    ComponentEntityTypeDetail
    Target Contract0x88e6...5640Proxy/LogicUniswap V3 Pool
    Owner/Admin0x1a9C...7320EOAFlag: Single key control (No Timelock)
    Proxy Admin0x0000...0000N/ADirect immutable implementation
    AccessControlDEFAULT_ADMINEOAHeld by 0x1a9C...7320

    Findings

    Single EOA Admin: The owner role is held by a single externally-owned account. The chain cannot verify if this is a hardware wallet or an MPC setup.

    No Timelock Detected: Privileged calls to setFeeProtocol and collectProtocol do not appear to be routed through a timelock contract, allowing for immediate execution.

    • Direct Control: The holder of the DEFAULT_ADMIN_ROLE can manage other roles without a delay period.

    Read Scope Limitations
    This audit could not establish the off-chain custody practices for the EOA 0x1a9C...7320. It also does not cover roles that may have been granted without emitting standard RoleGranted events.

    Next steps

    1. Run ownerwatch probe --prove --rpc <rpc> 0x88e6...5640 to simulate a privileged call.
    2. Verify the off-chain identity and custody policy of the admin EOA.
    3. Generate a monitoring config to alert on OwnershipTransferred events.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Protocols often claim decentralization while retaining hidden admin keys or upgrade paths. This skill audits the admin surface of EVM smart contracts to identify who truly holds power, from proxy admins to timelock delays.

    What it does

    • Probes admin surfaces by walking the control graph of owners, upgrade admins, beacons, and timelocks.
    • Audits AccessControl roles by replaying logs to list every current role holder across a protocol.
    • Identifies EOA risks by flagging single-signature externally owned accounts and 1-of-N multisigs.
    • Simulates privileged calls using eth_call to prove a specific holder can execute mints, pauses, or upgrades.
    • Generates monitoring configs to track ownership changes, role grants, or threshold updates in real-time.
    • Verifies ERC-8241 disclosures against live chain state to confirm control transparency.

    How it works

    1. Probe: Run the probe command against a target address to identify owners, proxy admins, and role structures.
    2. Verify: Use the --roles-from-logs flag to extract AccessControl holders from deployment history.
    3. Prove: Execute the --prove flag to simulate calls like upgradeTo or grantRole to verify findings.
    4. Monitor: Output results to YAML to scaffold a continuous monitoring agent or GitHub Action.

    Frameworks & tools

    Built on ownerwatch and Python 3.10. It interacts with Ethereum, Base, Arbitrum, Optimism, Polygon, BSC, and Avalanche via standard JSON-RPC endpoints.

    Why this beats prompting it yourself

    Prompting an LLM to "audit this contract" usually results in hallucinated role names or guesses about upgradeability. This skill uses a specialized engine to trace actual on-chain state, ensuring every reported owner or signer is verified against the ledger.

    Use cases

    • Audit a protocol before a large deposit to verify if the team can rug via upgrade.
    • Track role drift in a complex AccessControl system during a migration.
    • Generate weekly reports for a DAO to confirm multisig thresholds remain correct.
    • Verify that a third-party ERC-8241 control disclosure is honest and complete.

    Known limitations

    Cannot establish off-chain key custody or MPC setups. Reads are limited by RPC node availability and log history; failed reads are reported as inconclusive, not clean.

    Requires Python 3.10+. Cannot identify off-chain key custody or MPC participants. Restricted to chain state; custom grantRole overrides may require simulation to confirm.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 9 days ago

    • Free with an Agensi account

    Requires

    Python

    Permissions

    Terminal / Shell
    Network Access
    Listed9 days ago

    What's inside

    Frequently Asked Questions

    This skill specializes in identifying hidden admin risks by tracing the control graph of proxy admins, timelocks, and AccessControl roles directly from on-chain state rather than just reading source code.

    The skill works with any standard JSON-RPC provider and supports major EVM chains including Ethereum, Base, Arbitrum, Optimism, Polygon, BSC, and Avalanche.

    No, the skill only requires a target contract address; it automatically reconstructs the control graph and role hierarchy by probing the chain and replaying event logs.

    You receive the 'evm contract control audit' skill package, documentation for CLI and API integration, and pre-configured YAML templates for setting up continuous monitoring.

    The skill uses 'eth_call' to simulate privileged actions like upgrades or minting, allowing it to prove whether a specific account actually holds the power it claims to have.

    The skill cannot verify off-chain MPC (Multi-Party Computation) setups or the physical custody of private keys; it focuses strictly on on-chain permissions and logic.

    New in Web3 & Crypto