SkillsAdd

smithery/sablier-labs

etherscan-verification

Verify smart contracts on Etherscan-compatible block explorers.

Installation

$ npx skills add smithery/sablier-labs --skill etherscan-verification
View on skills.sh ↗ Website ↗

Summary

  • Verify smart contracts on Etherscan-compatible block explorers.
  • This skill should be used when the user asks to "verify contract", "verify on etherscan", "verify on chain scan".
  • Handles standard verification, Etherscan V2 API for unsupported chains on foundry, proxy patterns, and factory-created contracts.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

connect-required-verification-information Similar name
stripe/ai

>- Use this skill when the user asks what information a Stripe Connect connected account must p…

25 installs
verification-before-completion Similar name
obra/superpowers

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs …

203.7K installs
extension-email-verification Similar name
caffeinelabs/skills

Support for sending an email with a link the recipient can click to prove they own the email ad…

18.5K installs
verification-loop Similar name
affaan-m/ecc

A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code …

9.1K installs
django-verification Similar name
affaan-m/ecc

Verification loop for Django projects: migrations, linting, tests with coverage, security scans…

8.8K installs
springboot-verification Similar name
affaan-m/ecc

Verification loop for Spring Boot projects: build, static analysis, tests with coverage, securi…

8.7K installs

Also in this package

Other skills from smithery/sablier-labs.

npx skills add smithery/sablier-labs
xstate-react 0 sablier-design 0 evm-deployment 0 btt 0

Browse all from smithery/sablier-labs

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.1.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,181 B
  • docs SUMMARY.md 337 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Overview

Contract verification on Etherscan-compatible explorers using Foundry's forge verify-contract. Covers standard verification, unsupported chains via Etherscan V2 API, proxy patterns, and factory-created contracts.

When to Use

  • Verify deployed smart contracts on Etherscan-compatible explorers
  • Verify proxy contracts (ERC1967, UUPS)
  • Verify factory-created contracts (CREATE2)
  • Extract constructor arguments from deployment data

Prerequisites

Requirement How to Get
Foundry ≥1.3.6 Run forge -V to check version
Contract address From deployment broadcast or user
Chain ID From explorer or network configuration
Explorer API key From Etherscan account (works for V2 multi-chain)
Source code Must match deployed bytecode exactly

Version Check

Before proceeding, verify Foundry version:

forge -V

Stop if version is below 1.3.6.

Verification Methods

Method 1: Standard (Native Support)

For chains Foundry supports natively:

FOUNDRY_PROFILE=optimized forge verify-contract \
  <CONTRACT_ADDRESS> \
  src/<Contract>.sol:<Contract> \
  --rpc-url <chain_name> \
  --verifier etherscan \
  --etherscan-api-key $ETHERSCAN_API_KEY \
  --watch

Method 2: Etherscan V2 API (Unsupported Chains on Foundry)

When Foundry shows "No known Etherscan API URL for chain X":

FOUNDRY_PROFILE=optimized forge verify-contract \
  <CONTRACT_ADDRESS> \
  src/<Contract>.sol:<Contract> \
  --verifier etherscan \
  --verifier-url "https://api.etherscan.io/v2/api?chainid=<CHAIN_ID>" \
  --etherscan-api-key $ETHERSCAN_API_KEY \
  --watch

Supported chains: https://docs.etherscan.io/supported-chains

Method 3: With Constructor Arguments

For contracts with constructor parameters:

FOUNDRY_PROFILE=optimized forge verify-contract \
  <CONTRACT_ADDRESS> \
  src/<Contract>.sol:<Contract> \
  --verifier etherscan \
  --verifier-url "https://api.etherscan.io/v2/api?chainid=<CHAIN_ID>" \
  --etherscan-api-key $ETHERSCAN_API_KEY \
  --constructor-args <ABI_ENCODED_ARGS> \
  --watch

Generate constructor args with cast abi-encode:

cast abi-encode "constructor(address,uint256)" 0x123... 1000

Special Cases

Reference: ./references/special-cases.md

Proxy Contracts

Verify implementation and proxy separately. See reference for ERC1967 pattern.

Factory-Created Contracts

Extract constructor args from broadcast initCode using scripts/extractconstructorargs.py.

Library Verification

For libraries, use full path:

src/libraries/<Library>.sol:<Library>

Troubleshooting

Reference: ./references/troubleshooting.md

Common Issues

Error Cause Solution
"No known Etherscan API URL" Chain not in Foundry Use --verifier-url with V2 API
"Bytecode does not match" Compilation drift Checkout deployment commit + reinstall deps
"Constructor args mismatch" Wrong/missing args Extract from broadcast or encode manually
"Already verified" Previously verified No action needed

Output

After successful verification:

  • Contract source visible on explorer
  • ABI available for interaction
  • Constructor args decoded
  • "Contract Source Code Verified" badge

Examples

Reference: ./references/examples.md for real-world verification examples from Monad deployment.