Add verifying-contracts-on-basescan skill#37
Open
xam-dev-ux wants to merge 2 commits into
Open
Conversation
Collaborator
🟡 Heimdall Review Status
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #35
Summary
Adds
verifying-contracts-on-basescanskill covering smart contract verification on Base Mainnet and Base Sepolia.Motivation
A common failure mode for both developers and AI coding agents is recommending the deprecated Basescan V1 API instead of the unified Etherscan V2 API. V1 was fully deactivated on August 15, 2025. The exact error it returns:
Stale docs and LLM training data keep surfacing
api.basescan.org/apiand per-chain Basescan keys. This skill is the authoritative reference so agents stop suggesting V1 endpoints.Verification is also only mentioned in passing inside
deploying-contracts-on-base, with no coverage of standalone verification, Hardhat, Sourcify, or already-deployed contracts.This was tested live on Base Sepolia before opening this PR
SimpleStoragewith a constructor argumentforge verify-contract --verifier-url "https://api.etherscan.io/v2/api?chainid=84532"):0xA6E4e2977dD3470Fa3E9683B98DC30B888755D0a→Pass - Verified--verifier sourcify, no API key):0xF0E6DF13b99525f9144D82f23b9DF860BAB4EE1e→exact_matchalready verified. Skipping verificationbehaviour (graceful, not an error — corrected in the skill from the live test)Scope
forge verify-contract(Mainnet/Sepolia, constructor args,--watch, linked libraries)foundry.tomlV2 config replacing the deprecated per-chain basescan URLs@nomicfoundation/hardhat-verify— singleapiKeystring +customChainspointing to V2deploying-contracts-on-basefor deploy+verify flow — no duplicationOut of scope
Deployment — that lives in
deploying-contracts-on-base.Checklist
verifying-contracts-on-basescanskill #35