addresses

Retrieve verified contract addresses for EVM protocols across multiple networks.

1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/tawf-labs/zkt-hackathon --skill addresses-tawf-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: addresses
Source: https://github.com/tawf-labs/zkt-hackathon/tree/main/.agents/skills/ethskills/addresses
Command: npx skills add https://github.com/tawf-labs/zkt-hackathon --skill addresses-tawf-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents users from guessing or hallucinating on-chain contract addresses by providing a verified address registry that they can rely on before interacting with protocols, reducing the risk of failed transactions and lost funds.

Core Features & Use Cases

  • Protocol address registry: Centralizes verified contract addresses for major Ethereum and L2 protocols (tokens, routers, factories, infrastructure contracts).
  • Multi-network coverage: Includes per-network addresses (e.g., mainnet, Arbitrum, Optimism, Base, Polygon, zkSync Era) and notes where addresses differ vs are deterministic via CREATE2.
  • Safety-oriented verification guidance: Emphasizes never hallucinating addresses and instructs users to verify on a block explorer, aligning with practical operational security.
  • Use Case: If you are building a DeFi or trading integration and need the correct router, factory, or oracle addresses for a specific network, use this registry to fetch the right addresses and avoid deploying/txing against incorrect contracts.

Quick Start

Ask the Skill to list the verified contract address for the Uniswap V3 SwapRouter on Ethereum mainnet and confirm any network-specific notes.

Frequently Asked Questions about addresses

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

FAQPage Schema
How do I verify contract addresses before executing DeFi integration transactions?

Verify contract addresses by cross-referencing a root registry of verified addresses before transaction preparation. This prevents interacting with hallucinated on-chain contracts, requiring user-side confirmation against block explorers to avoid failed transactions and lost funds.

What's the best way to find protocol router and factory addresses across Ethereum L2 networks?

Finding protocol router and factory addresses across L2 networks requires a multi-network registry providing per-chain addresses for Arbitrum, Optimism, Base, Polygon, and zkSync Era. This centralizes verified infrastructure contracts to ensure accurate protocol integration.

Does this address registry support deterministic CREATE2 addresses across different EVM chains?

Yes, the address registry supports deterministic CREATE2 addresses across EVM networks. It explicitly notes where contract addresses differ versus where they are deterministically deployed via CREATE2, ensuring accurate protocol integration across specific chains.

How do I get the correct token contract addresses for a specific network integration?

Get correct token contract addresses by querying a centralized protocol address registry scoped to specific networks. This registry provides verified token contracts and mandates block explorer confirmation before transaction preparation to prevent fund loss.

Why should I not guess on-chain contract addresses for DeFi protocol integration?

Guessing on-chain contract addresses for DeFi protocol integration risks failed transactions and lost funds due to hallucinated contracts. Using a verified address registry prevents this by providing reliable references for routers, factories, and infrastructure components.

Can I use this registry to find infrastructure and oracle contract addresses for my trading integration?

Yes, you can use this registry to find infrastructure and oracle contract addresses for trading integrations. It centralizes verified addresses for major Ethereum and L2 protocols, ensuring you fetch the correct infrastructure components for specific networks.