contract-addresses

Consolidate canonical, checksummed EVM contract addresses across five networks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/labsaistudio/AABC-Labs --skill contract-addresses-labsaistudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contract-addresses
Source: https://github.com/labsaistudio/AABC-Labs/tree/main/backend/agent/skills/catalog/contract-addresses
Command: npx skills add https://github.com/labsaistudio/AABC-Labs --skill contract-addresses-labsaistudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical reference of verified, on-chain contract addresses for major EVM protocols across Ethereum, Arbitrum, Optimism, Base, and Polygon, ensuring that developers use the correct, checksummed addresses before integrating.

Core Features & Use Cases

  • Cross-chain address reference: Provides the canonical native and, where relevant, bridged contract addresses for tokens, DEX routers, lending pools, bridges, and infrastructure across Ethereum-compatible networks.
  • Safety and verification: Emphasizes on-chain verification via cast code and on-chain discovery to prevent misaddressing, spoofing, or proxy confusion in production integrations.
  • Use Case: Build wallets, dApps, or automation tools that require accurate contract addresses per chain to prevent failed transactions or asset loss.

Quick Start

Query the latest canonical, checksummed addresses for a given protocol and chain before deploying or integrating.

Frequently Asked Questions about contract-addresses

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

FAQPage Schema
How do I find the correct contract address for an EVM protocol across multiple chains?

To find the correct contract address across chains, you need a canonical reference that provides verified, checksummed addresses for major EVM networks like Ethereum, Arbitrum, Optimism, Base, and Polygon to ensure integration accuracy.

How do I verify a contract address on-chain before integrating it into my dApp?

Verify a contract address on-chain by using tools like `cast code` to confirm the deployed bytecode and check for proxy patterns, preventing misaddressing, spoofing, or proxy confusion in production wallet or dApp integrations.

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

Native and bridged token contract addresses differ by deployment origin; canonical address references distinguish these variants on L2 networks like Arbitrum and Optimism to prevent failed transactions and asset loss during cross-chain operations.

Why does my EVM transaction fail due to a checksummed contract address mismatch?

EVM transactions fail due to checksum mismatches when the address format is invalid; using a canonical reference of cross-chain, checksummed contract addresses ensures format correctness before deploying integrations.

Can I use a single contract address for a protocol across Ethereum, Arbitrum, and Base?

No, you cannot use a single contract address across Ethereum, Arbitrum, and Base because protocols deploy distinct native or bridged contracts per chain, requiring cross-chain awareness to identify the correct address.

What are the limitations of using hardcoded contract addresses for multichain EVM integrations?

Hardcoded contract addresses limit multichain EVM integrations because they fail to account for proxy pattern upgrades, bridged variants, and network-specific deployments, requiring on-chain verification and up-to-date canonical references.