docs(forge): explain scripting internals - #2083
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
figtracer
requested review from
mablr,
mattsse and
stevencartavia
as code owners
September 13, 2026 14:39
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 scripting quickstart shows how to run deployments but leaves sender selection and the execution stages implicit. Add a linked internals guide explaining script callers, transaction senders and signers, CREATE2 factory behavior, external library linking, nonce assignment, transaction simulation, and saved-sequence resume semantics. Include the limits of the existing sender protection and a runnable example that assigns ownership explicitly.
The quickstart and Forge sidebar link to the new guide. This is documentation only; it introduces no configuration errors or runtime behavior changes.
AI assistance: Codex helped trace the implementation, write the guide and example, and verify the documentation and local deployment workflow.