addresses

Provide verified on-chain contract addresses for Ethereum and EVM-compatible chains.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/mashharuki/flare-sample --skill addresses-mashharuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: addresses
Source: https://github.com/mashharuki/flare-sample/tree/main/.claude/skills/eth-addresses
Command: npx skills add https://github.com/mashharuki/flare-sample --skill addresses-mashharuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents costly mistakes and hallucinations by providing curated, on-chain-verified contract addresses for Ethereum and EVM-compatible chains so users do not send funds or interact with the wrong contracts.

Core Features & Use Cases

  • Verified Addresses: A curated list of token, DEX, lending, oracle, bridge, and infrastructure contract addresses verified via bytecode checks and onchain calls.
  • Multi-Chain Coverage: Covers Mainnet and major L2s (Arbitrum, Optimism, Base, Polygon, zkSync, etc.) with notes on CREATE2 determinism and chain-specific differences.
  • Practical Use Cases: Developers preparing transactions, auditors cross-checking deployments, and traders or ops teams validating contract addresses before sending funds.

Quick Start

Provide the verified Optimism address for USDC and confirm its checksum and verification status.

Frequently Asked Questions about addresses

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

FAQPage Schema
How do I verify Ethereum and L2 contract addresses to prevent sending funds to malicious contracts?

Verify Ethereum and L2 contract addresses by checking bytecode presence, symbol/name calls, and documented protocol sources. This prevents costly mistakes and hallucinations by ensuring you interact with curated, on-chain-verified contracts across Mainnet and major L2s.

Does this provide verified contract addresses for EVM-compatible chains like Arbitrum and Base?

Yes, verified contract addresses are provided for EVM-compatible chains including Arbitrum, Optimism, Base, Polygon, and zkSync. Coverage includes notes on CREATE2 determinism and chain-specific differences for accurate cross-chain deployment.

What is the best way to cross-check token and DEX contract addresses before preparing a transaction?

The best way to cross-check contract addresses is by using a curated list verified via on-chain bytecode checks. This confirms token, DEX, lending, and oracle addresses before preparing transactions, satisfying strict verification requirements.

How do I get the checksummed Optimism address for USDC and confirm its verification status?

To get the checksummed Optimism address for USDC, request the verified address and confirm its on-chain verification status. This involves checking bytecode presence and validating documented protocol sources to ensure accurate deployment.

Why do I need on-chain verification for contract addresses during deployment and auditing?

On-chain verification is needed during deployment and auditing to validate bytecode presence and CREATE2 determinism. It ensures developers, auditors, and ops teams use accurate contract addresses across Mainnet and L2s, preventing interaction with spoofed contracts.