Update Stylus best-practices pages for SDK 0.10.7#3407
Open
anegg0 wants to merge 2 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Jun 24, 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.
Stylus docs update — part of a small set of PRs (tagged
stylus) bringingdocs/stylus/in line with the current stack (stylus-sdk / cargo-stylus 0.10.7, Nitro v3.11.0).best-practices/security.mdx— rewrite examples to the 0.10.7 Host-trait API (#[public],self.vm().…); modernize reentrancy guidance (automatic cache-flush;deny_reentrantdeprecated).best-practices/gas-optimization.mdx— correct gas economics (EIP-3529 refund cap), remove non-existent CLI flags, restore a concrete sourced performance table.Examples verified against the live toolchain (compiled/deployed on a local Nitro dev node where relevant) and conceptual claims against the Nitro source. Builds clean (
yarn build, strictonBrokenLinks). Version strings are literals here; they are centralized intoglobalVars.jsin a follow-up PR.