feat: add Benchmarking on Base / OP Stack skill#23
Open
okwn wants to merge 1 commit into
Open
Conversation
Teaches disciplined benchmarking methodology for Base and OP Stack chains, covering four measurement domains (RPC latency, transaction lifecycle, log queries, gas), environment tiers (local/testnet/mainnet/other OP Stack), fair comparison rules, input validation, security guards, and a reproducibility data capture template.
Collaborator
🟡 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
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.
This PR adds a new skill, Benchmarking on Base / OP Stack, to help developers benchmark apps, contracts, RPC behavior, and transaction workflows on Base and other OP Stack chains more rigorously.
It focuses on practical benchmarking methodology rather than performance claims, including:
what to measure
fair comparison rules
environment differences
reproducibility
common mistakes
safe and responsible benchmarking practices
The skill is designed as an onboarding and education-oriented addition to the repo, covering topics such as RPC latency, transaction lifecycle timing, contract read/write benchmarking, log query performance, and the caveats around public RPCs, caching, rate limits, retries, and chain state variability.
It also emphasizes avoiding misleading results and discourages abusive or unsafe benchmark patterns against third-party infrastructure.