contract-verify

Verify on-chain smart contract state against frontend hardcoded values.

1|Updated Feb 26, 2026

Search Tags:#verification #smart contracts #web3 #foundry #on-chain #cast #dapp qa

Ready to run

npx skills add https://github.com/0xHoneyJar/construct-protocol --skill contract-verify-0xhoneyjar

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill verifies on-chain smart contract state against frontend hardcoded values, ensuring that what users see in the UI accurately reflects the deployed contract's parameters and logic.

Core Features & Use Cases

On-Chain State Verification: Compares deployed contract parameters (e.g., fees, percentages, addresses) with values present in the frontend codebase.
Proxy Detection: Identifies if a contract is a proxy and determines its implementation address for accurate state reading.
Discrepancy Reporting: Generates detailed reports highlighting critical mismatches, warnings for hardcoded values, and information on unreferenced parameters.
Use Case: Detects if a frontend displays a 2% bid increment while the on-chain contract enforces a 5% increment, preventing user errors and failed transactions.

Quick Start

Verify the on-chain state of the contract at address 0xABC...123 on mainnet against the frontend code.

Frequently Asked Questions about contract-verify

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

FAQPage Schema

How do I verify smart contract on-chain state against frontend hardcoded values?▼

To verify smart contract on-chain state, this Skill reads deployed parameters via `cast` and scans your frontend codebase to identify discrepancies. It generates detailed reports on critical mismatches, warnings for hardcoded values, and unreferenced parameters.

Can I detect proxy patterns and implementation addresses when verifying dApp parameters?▼

Yes, proxy pattern detection is supported during on-chain state verification. The Skill identifies if a contract is a proxy and determines its implementation address to ensure accurate state reading against frontend hardcoded values.

What is the best way to check if my web3 frontend displays incorrect contract fees?▼

Checking web3 frontend fee accuracy is done by reading deployed contract parameters via `cast` and comparing them against frontend hardcoded values. This prevents user errors by detecting critical mismatches like incorrect bid increments.

Does Foundry Cast work with this on-chain verification process for deployed contracts?▼

Yes, Foundry Cast is utilized directly to read on-chain smart contract state. The Skill uses `cast` to fetch deployed parameters and compares them with frontend hardcoded values to highlight any discrepancies.

What type of report is generated when scanning for hardcoded value mismatches?▼

The generated report details critical mismatches between on-chain contract state and frontend hardcoded values. It also includes warnings for hardcoded values and information on unreferenced parameters found during the codebase scan.

Why do my dApp users experience failed transactions due to incorrect UI assumptions?▼

Failed transactions occur when dApp frontends display hardcoded values like a 2% bid increment while the on-chain contract enforces 5%. Verifying on-chain state against frontend code prevents these user errors and failed transactions.