create2-patterns

Determine deterministic Ethereum smart contract deployment addresses using CREATE2.

120|12|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ccashwell/evm-cortex --skill create2-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create2-patterns
Source: https://github.com/ccashwell/evm-cortex/tree/main/skills/create2-patterns
Command: npx skills add https://github.com/ccashwell/evm-cortex --skill create2-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Determine deterministic deployment addresses for Ethereum smart contracts using CREATE2, enabling predictable deployments and cross-chain consistency.

Core Features & Use Cases

  • Deterministic address prediction and verification with CREATE2.
  • Factory patterns, salt strategies, and cross-chain deployment considerations.
  • Quick-start examples for common deployment scenarios and safety checks.

Quick Start

Deploy a contract to a known deterministic address using CREATE2 by selecting a salt, preparing init code, and validating the resulting address.

Frequently Asked Questions about create2-patterns

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

FAQPage Schema
How do I calculate a deterministic Ethereum contract address using CREATE2?

Calculate a deterministic Ethereum contract address using CREATE2 by combining the factory contract address, a user-defined salt, and the contract's initialization bytecode. This formula yields a predictable deployment address before execution.

What is CREATE2 used for in smart contract deployment?

CREATE2 is used for deterministic smart contract deployment, enabling address precomputation and cross-chain consistency. It allows developers to deploy contracts to identical addresses across multiple networks when using the same salt and init code.

How do I maintain cross-chain address consistency when deploying contracts?

Maintain cross-chain address consistency by using CREATE2 factory patterns with identical salt values and initialization code across multiple networks. This deterministic deployment strategy ensures the same contract address is generated on every chain.

What are the best strategies for salt management in factory patterns?

Effective salt management in factory patterns involves selecting unique, predictable values to avoid address collisions. Strategies include using user addresses or specific nonces as the CREATE2 salt to ensure safe, predictable deployments without overriding existing contracts.

Can I generate vanity addresses with CREATE2 deterministic deployment?

Yes, you can generate vanity addresses using CREATE2 deterministic deployment. By iterating through different salt values, you can find a desired address prefix, though vanity-address considerations require balancing computational effort against deployment safety checks.

What are the limitations of using CREATE2 for address precomputation?

Limitations of CREATE2 address precomputation include strict dependency on the exact initialization code and factory address. Any change in the init code or salt alters the resulting address, requiring careful validation to avoid deployment failures.