addresses

Retrieve verified smart contract addresses for Ethereum and L2 protocols.

7|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/Zodomo/DrandVerifier --skill addresses-zodomo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: addresses
Source: https://github.com/Zodomo/DrandVerifier/tree/main/.opencode/skills/ethskills/addresses
Command: npx skills add https://github.com/Zodomo/DrandVerifier --skill addresses-zodomo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents costly mistakes caused by guessing or hallucinating smart contract addresses, which can lead to lost funds and failed transactions.

Core Features & Use Cases

  • Verified EVM addresses across mainnet and L2s: Use only addresses confirmed as deployed and callable onchain.
  • Curated protocol coverage: Includes major DeFi, infrastructure, tokens, and cross-chain components (e.g., Uniswap, Aave, Compound, Safe, Chainlink CCIP, EigenLayer, Across, ENS).
  • Practical guidance and safety reminders: Emphasizes double-checking on a block explorer and highlights cases where addresses differ by chain.
  • Use Case: You want to integrate Permit2 or a protocol router on a target network, but you need the exact address for contract calls and transaction construction without relying on memory.

Quick Start

Ask for the verified address for a specific protocol contract on a specific network, for example: "Give me the verified Uniswap V3 SwapRouter02 address on Arbitrum."

Frequently Asked Questions about addresses

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

FAQPage Schema
How do I find verified smart contract addresses for DeFi protocols on Ethereum L2 networks?

You can retrieve verified smart contract addresses by specifying the protocol name and target network, ensuring you get confirmed onchain addresses for Ethereum mainnet and L2s to prevent transaction failures from guessed endpoints.

Why do protocol router addresses differ across EVM chains like Arbitrum and Base?

Protocol router addresses differ across EVM chains because contracts are deployed independently on each network, requiring per-network address differentiation to ensure correct contract calls and transaction construction on the specific chain you are targeting.

What is the safest way to get contract addresses for transaction building without hallucinations?

The safest way to get contract addresses without hallucinations is using curated verification guidance that provides confirmed deployed addresses for major protocols, supplemented by double-checking the specific contract on a block explorer before executing transactions.

Can I use this to find addresses for cross-chain infrastructure protocols like Chainlink CCIP and Across?

Yes, you can find addresses for cross-chain infrastructure protocols like Chainlink CCIP and Across, as the curated coverage includes major DeFi, infrastructure, tokens, and cross-chain components deployed across mainnet and various L2 networks.

What protocols are covered for integration planning and deployment scripting?

Covered protocols for integration planning and deployment scripting include major DeFi and infrastructure components like Uniswap, Aave, Compound, Safe, Chainlink CCIP, EigenLayer, Across, and ENS across networks such as mainnet, Arbitrum, Optimism, Base, and Polygon.

Does this provide the exact address for Permit2 on a target network?

Yes, it provides the exact address for Permit2 on a target network, supplying the precise contract address needed for integration planning and transaction construction without relying on memory or guessing the deployment endpoint.