multichain-deployment

Deploy identical protocol addresses across multiple blockchains using deterministic CREATE2 factories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying the same protocol across multiple blockchains at a single address is error-prone and labor-intensive. This Skill provides a repeatable pattern using CREATE2, deployment registries, and per-chain configuration to ensure identical deployment outcomes across chains.

Core Features & Use Cases

  • Deterministic cross-chain deployment using CREATE2
  • Per-chain configuration via initialize patterns
  • Deployment registry for tracking across chains
  • Multi-chain testing workflows to verify address equivalence
  • Guidance on chain-specific config and initialization

Quick Start

Configure your deployment script to use a deterministic CREATE2 factory, provide per-chain configuration, and execute the multi-chain deployment workflow.

Frequently Asked Questions about multichain-deployment

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

FAQPage Schema
How do I deploy the same protocol address across multiple blockchains?

You can deploy the same protocol address across multiple blockchains using deterministic CREATE2 deployment. This approach applies per-chain configuration and a deployment registry to ensure identical deployment outcomes across chains without manual address tracking.

What is deterministic deployment and how does CREATE2 work for cross-chain deployments?

Deterministic deployment uses the CREATE2 opcode to generate identical contract addresses across multiple blockchains. It requires a deterministic factory and per-chain initialization logic to ensure the same protocol address is deployed repeatably across testnets and mainnets.

How do I configure per-chain initialization logic for multi-chain deployment?

You configure per-chain initialization logic using initialize patterns that accept chain-specific configuration. This allows the deployment script to apply unique parameters per blockchain while maintaining the same deterministic contract address through the CREATE2 factory.

Do I need a deployment registry to track blockchain addresses across chains?

Yes, a deployment registry is required to track blockchain addresses and provide auditable deployment records across chains. It records the deployed addresses for cross-chain deployments, ensuring you can verify address equivalence across testnets and mainnets.

How do I verify address equivalence during multi-chain testing workflows?

You verify address equivalence by executing multi-chain testing workflows after configuring your deterministic CREATE2 factory. These workflows check that the per-chain configuration and initialization logic produce the identical protocol address across the targeted blockchains.