permit2-addresses

Standardize Permit2 contract addresses per chain for multi-chain applications.

Updated Nov 5, 2025
One-click install
npx skills add https://github.com/cyotee/crane --skill permit2-addresses
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: permit2-addresses
Source: https://github.com/cyotee/crane/tree/main/.claude/skills/permit2-addresses
Command: npx skills add https://github.com/cyotee/crane --skill permit2-addresses

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical Permit2 contract addresses by chain are essential for multi-chain deployment and configuration of permit2-enabled workflows.

Core Features & Use Cases

  • Centralized canonical addresses: Provides canonical Permit2 addresses for all supported chains.
  • Per-chain lookups: Enables straightforward resolution of the correct address per chain ID in code and configs.
  • Frontend and backend integration: Guidance for importing and using the address in apps and SDKs.

Quick Start

Query the canonical address for a target chain and integrate it into your deployment or app configuration.

Frequently Asked Questions about permit2-addresses

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

FAQPage Schema
How do I resolve the correct Permit2 contract address for a specific chain ID in my multi-chain application?

Resolving the correct Permit2 contract address for a specific chain ID involves looking up the canonical addresses standardized per chain. This provides straightforward resolution for deployment and app configuration.

What are canonical Permit2 addresses and why are they needed for multi-chain deployments?

Canonical Permit2 addresses are the standardized contract addresses deployed across supported chains. They are essential for configuring multi-chain permit2-enabled workflows and ensuring correct code resolution.

How do I integrate canonical Permit2 addresses into my frontend and backend SDKs?

Integrating canonical Permit2 addresses into frontend and backend SDKs requires querying the target chain address and importing it into your app configuration. This ensures multi-chain deployment resolves correctly.

Does this Permit2 address lookup work for all Ethereum blockchain environments?

The Permit2 address lookup works for supported chains within Ethereum blockchain environments. It standardizes contract addresses by chain ID for deployment and configuration across multi-chain applications.

Can I use a single configuration file for Permit2 addresses across different chain IDs?

Yes, you can use a centralized configuration for Permit2 addresses across different chain IDs. This approach provides canonical addresses for all supported chains, streamlining multi-chain app configuration.