abi-audit

Audit frontend ABIs against deployed smart contract ABIs for mismatches.

1|Updated Feb 26, 2026

Search Tags:#frontend #verification #auditing #smart contracts #wagmi #viem #abi

Ready to run

npx skills add https://github.com/0xHoneyJar/construct-protocol --skill abi-audit

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that the Application Binary Interfaces (ABIs) used in your frontend code precisely match the ABIs of your deployed smart contracts, preventing silent failures and data corruption.

Core Features & Use Cases

ABI Mismatch Detection: Compares frontend ABI definitions against deployed contract ABIs to find discrepancies.
Stale ABI Identification: Flags ABIs that are out of date with the latest contract deployments.
Function Signature Auditing: Verifies that function, event, and error signatures align between frontend and on-chain contracts.
Use Case: After a contract upgrade, your frontend might still be using the old ABI, leading to calls that revert or return incorrect data. This skill will identify these mismatches and guide you on how to update your frontend.

Quick Start

Run the abi-audit skill to compare all frontend ABIs against their deployed contract versions.

Frequently Asked Questions about abi-audit

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

FAQPage Schema

How do I check if my frontend ABI matches the deployed smart contract?▼

To check if your frontend ABI matches a deployed smart contract, you can audit function signatures, event definitions, and custom errors against the on-chain version to detect mismatches and prevent silent runtime failures.

Why does my wagmi contract call revert after a contract upgrade?▼

Contract calls revert after an upgrade because the frontend uses a stale ABI. Auditing the frontend Application Binary Interface against the newly deployed contract identifies outdated function signatures and integration bugs.

How do I audit viem integration bugs for stale ABIs?▼

You can audit viem integration bugs by comparing your frontend codebase ABIs with deployed contract addresses and chain information, which identifies stale ABIs and reports discrepancies in custom errors or events.

What do I need to audit frontend ABIs against deployed contracts?▼

Auditing frontend ABIs against deployed contracts requires access to the contract addresses, the target chain information, and the frontend codebase to accurately compare and verify data integrity.

What is the best way to sync frontend ABIs with deployed contracts?▼

The best way to sync frontend ABIs is to run an audit that compares your frontend definitions against deployed contract ABIs, automatically detecting and reporting mismatches in function signatures to ensure data integrity.