Skip to content

skills: v6.7.0 catch-up - #21

Draft
seidroid[bot] wants to merge 5 commits into
mainfrom
docs-bridge/release-v6.7.0
Draft

seidroid[bot] wants to merge 5 commits into
mainfrom
docs-bridge/release-v6.7.0

Conversation

@seidroid

@seidroid seidroid Bot commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

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.

source PR files touched summary
sei-protocol/sei-chain#3658 skill/references/contracts/performance-testing.md Adds a new standalone CLI tool evmonly-loadtest for feeding synthetic transfer/ERC20/snapshot-revert blocks to the EVM-only executor, with a large set of tunable flags and Prometheus metrics.

Reviewer notes

  • [codex] add evm-only executor load test harness sei-chain#3658 — The new evmonly-loadtest tool 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 no update for syntax corrections is needed elsewhere. A dedicated create skill 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.

⚠️ Possible contradictions or misplaced sections

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:

  • SSTORE cost contradiction: The inserted throughput-math/common-bottlenecks area is untouched, but the untouched "Common bottlenecks" table says "SSTORE costs 72k on both networks" — checking for a conflicting figure elsewhere: none found. (No contradiction.)

Let me check the specific flagged categories carefully.

  • Chain ID contradiction: The untouched anvil command uses --chain-id 1328 (Sei testnet), while the inserted harness section says the synthetic workload "defaults to local EVM chain ID 1337." 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.

… 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)
@seidroid seidroid Bot added the automated Automated PR from sei-docs-bridge label Nov 13, 2026
seidroid Bot added 4 commits November 13, 2026 06:35
…`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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated PR from sei-docs-bridge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants