docs: clarify CREATE2 factory requirements - #2085
Merged
Merged
Conversation
figtracer
requested review from
mablr,
mattsse and
stevencartavia
as code owners
September 13, 2026 14:39
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
mattsse
approved these changes
Sep 13, 2026
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
2 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.
The CREATE2 guide implies that every salted deployment uses Foundry's factory and that create2_deployer can select any custom factory. Scope automatic routing to the script's broadcast depth, explain the constructor's factory caller, and document the runtime-bytecode requirement. Point other factory protocols to explicit ABI calls and place the configuration example under profile.default.
AI assistance: Codex helped check the execution path, write the correction, and validate the page.