Verified Ethereum Contract Addresses

Provide verified Ethereum contract addresses and cast commands for bytecode verification.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/andginja/ethskills --skill verified-ethereum-contract-addresses
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Verified Ethereum Contract Addresses
Source: https://github.com/andginja/ethskills/tree/main/skills/contract-addresses
Command: npx skills add https://github.com/andginja/ethskills --skill verified-ethereum-contract-addresses

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents catastrophic fund loss by providing verified, production-ready contract addresses for major Ethereum protocols, along with robust verification commands to ensure accuracy.

Core Features & Use Cases

  • Verified Addresses: Access a curated list of essential contract addresses across Ethereum mainnet and L2s.
  • Verification Commands: Includes cast commands to independently verify each address's bytecode and functionality.
  • Use Case: Before interacting with Uniswap V3 on Arbitrum, use the provided cast code command to confirm the correct SwapRouter02 address, preventing accidental interaction with a malicious contract.

Quick Start

Verify the mainnet WETH contract address using the provided cast code command.

Frequently Asked Questions about Verified Ethereum Contract Addresses

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

FAQPage Schema
How do I verify Ethereum contract addresses before interacting with DeFi protocols?

Confusing Uniswap V2 and V3 contract interfaces causes transaction reverts and failed swaps. Use verified contract addresses to identify the correct SwapRouter version and ensure your function calls match the specific V2 or V3 interface on Ethereum mainnet or L2s.

What is the difference between native and bridged token contract addresses on L2 networks?

Using bridged vs. native token contract addresses on L2 networks causes incorrect decimal handling and failed transactions. Verified address lists clarify these cross-chain discrepancies by providing the exact production token address for the specific Layer 2 network you are targeting.

How do I use cast commands to verify Uniswap V3 contract bytecode on Arbitrum?

Use `cast code` commands to independently verify Uniswap V3 contract bytecode on Arbitrum. Running the provided verification command confirms the SwapRouter02 address is legitimate, preventing accidental interaction with malicious or incorrect contracts.

Can I find verified Aave contract addresses for multiple Ethereum Layer 2 networks?

Yes, you can find verified Aave contract addresses across Ethereum mainnet and multiple Layer 2 networks. The curated list ensures you use the correct production address for your specific L2, avoiding cross-chain address discrepancies.

Why does my Ethereum transaction fail when using a mainnet contract address on an L2?

Ethereum transactions fail when using mainnet contract addresses on L2s due to cross-chain address discrepancies. You must use the specific verified L2 contract address, as mainnet and Layer 2 deployments have different addresses and bridged token variations.