Repository navigation
skills: v6.7.0 catch-up - #21
Draft
seidroid[bot] wants to merge 5 commits into
Draft
seidroid[bot] wants to merge 5 commits into
seidroid[bot] wants to merge 5 commits into
Conversation
… synthetic transfer/ERC20/snapshot-revert blocks to the EVM-only executor, with a large set of tunable flags and Prometheus metrics. (sei-protocol/sei-chain#3658)
…M RPC, returning a -32000 error instead of serving proofs. (sei-protocol/sei-chain#3926)
…`seid tx evm associate-address` CLI command; developers must switch to standard eth_* methods and `seid tx evm native-associate`. (sei-protocol/sei-chain#3927)
… removed from the sei_* namespace, leaving only sei_getSeiAddress, sei_getEVMAddress, and sei_getCosmosTx as available legacy methods. (sei-protocol/sei-chain#3945)
…tion capability, plus internal changelog/migration fixes. (sei-protocol/sei-chain#4294)
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
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.
Skill catch-up for v6.7.0.
1 source PR(s) produced changes across 1 commit(s). Each source PR is a separate commit, so this reviews commit-by-commit.
skill/references/contracts/performance-testing.mdevmonly-loadtestfor feeding synthetic transfer/ERC20/snapshot-revert blocks to the EVM-only executor, with a large set of tunable flags and Prometheus metrics.Reviewer notes
evmonly-loadtesttool is an internal protocol-level benchmarking harness for the EVM-only executor, which thematically overlaps with the existing 'sei-chain loadtest harness' subsection in performance-testing.md. That file already frames such harnesses as educational-but-not-end-user-packaged, so an update there (rather than a new skill file) is the right fit — the audience here is contract developers load-testing their own contracts, not operators running the internal harness. The huge list of flags (workload/economics, pipeline/concurrency, result-sink, observability) is operator-oriented minutiae; the skill should mention the tool exists, its basic usage, workload types, and metrics endpoints rather than reproducing every flag. No existing command syntax in the skill files changed (the go.mod sei-load bump and otel/golang.org/x upgrades are internal dependency changes with no CLI-facing impact), so noupdatefor syntax corrections is needed elsewhere. A dedicatedcreateskill file was considered but rejected — the tool is not a user-facing seid command or a general workflow, and sei-skill has no 'internal protocol tooling' category.Flagged by a review of every touched page's final text. Each source PR was analysed in isolation, so these were invisible to the per-PR checks. Verify before merging — the checker cannot tell which side of a contradiction is correct.
Looking for contradictions between inserted and untouched text:
Let me check the specific flagged categories carefully.
--chain-id 1328(Sei testnet), while the inserted harness section says the synthetic workload "defaults to local EVM chain ID1337." These describe different tools (anvil fork vs. evmonly harness), so not a direct contradiction of the same identifier.NONE
Generated by sei-docs-bridge. Every change is a proposal — verify against the source PRs before merging.