feat: add reproducible CREATE2 deployment infrastructure#1874
Closed
0xAxiom wants to merge 9 commits intocoinbase:mainfrom
Closed
feat: add reproducible CREATE2 deployment infrastructure#18740xAxiom wants to merge 9 commits intocoinbase:mainfrom
0xAxiom wants to merge 9 commits intocoinbase:mainfrom
Conversation
Addresses issue coinbase#1759 - x402 agent onboarding complexity Features: - Zero-config wallet creation and discovery - Drop-in fetch replacement with automatic payment handling - Built-in spending limits for safety - Multi-chain support (EVM + optional Solana) - Simple API: createX402Client() -> client() Before: Complex setup, multiple imports, manual configuration After: One function call, automatic payment handling This addresses user feedback that x402 has better protocol design than MPP/Tempo but worse developer experience. Users can now start making x402 payments with minimal setup while maintaining the protocol's technical advantages.
…mit2 Proxies Addresses issue coinbase#1800: enables third-party deployment to canonical vanity addresses by providing raw creation bytecode and deployment tooling. Key components: - ExtractInitCode.s.sol script for bytecode extraction - deployments/ directory with README documentation - Complete deployment instructions using Arachnid CREATE2 deployer - Technical documentation of init code hash reproducibility issue This infrastructure allows anyone to deploy x402 Permit2 Proxies to their canonical addresses (0x402085c248eea27d92e8b30b2c58ed07f9e20001 and 0x402039b3d6e6bec5a02c2c9fd937ac17a6940002) on any EVM chain without requiring access to the original build environment. Next step: Extract original init code from existing deployments or build environment to populate the .initcode and .salt files. Resolves: coinbase#1800
|
@0xAxiom is attempting to deploy a commit to the Coinbase Team on Vercel. A member of the Team first needs to authorize it. |
🟡 Heimdall Review Status
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Third parties cannot reproduce x402 Permit2 Proxy deployments on new EVM chains because the init code hash depends on the exact compiler environment used during the original build. Different build environments produce different CBOR metadata, resulting in different init code hashes and breaking the CREATE2 deterministic address calculation.
This blocks ecosystem growth as new chains require manual deployment by Coinbase instead of community-driven deployment to the canonical vanity addresses.
Solution
This PR provides the infrastructure to solve the reproducible deployment problem:
🔧 ExtractInitCode.s.sol Script
📁 Deployments Directory Structure
📖 Comprehensive Documentation
🎯 Target Addresses
Next Steps
To complete the solution, someone with access to the original build environment or existing deployment transaction data needs to:
Impact
Immediate: Provides framework and tooling for reproducible deployments
Future: Enables permissionless deployment to canonical addresses on any EVM chain
This directly addresses the MegaETH deployment request in #1800 and establishes a pattern for all future chain deployments.
Resolves #1800