AI Docs Review — 2026-04-13

[github-actions]

AI Documentation Review — 2026-04-13

Automated review of llms-full.txt by Claude Opus 4.6.

1. Section: Quick Reference / Divergence from Ethereum
   Quote: "Throughput: 100 MGas/s (~12,500 TPS)"
   Suggestion: Clarify that 12,500 TPS is an estimate for simple transfers (at ~8,000 gas each). Complex contract calls will yield significantly lower TPS. Consider stating "100 MGas/s (up to ~12,500 simple transfer TPS)".
   Why: Developers may assume 12,500 TPS applies to all transaction types, leading to incorrect capacity planning.

2. Section: Divergence from Ethereum
   Quote: "EVM Version: Pectra (w/o blobs) | Fusaka"
   Suggestion: Verify that Ethereum's current version is labeled correctly. As of mid-2025, Ethereum's latest upgrade is Pectra (Prague + Electra), not "Fusaka." The text body says "Ethereum has since upgraded to Fusaka (December 2025)" — confirm this is accurate or update to reflect the actual current Ethereum upgrade name.
   Why: Incorrect EVM version naming will confuse developers trying to understand opcode and feature compatibility between Sei and Ethereum.

3. Section: Block Explorers
   Quote: "### undefined\n\n### undefined"
   Suggestion: Replace the two ### undefined headings with the actual explorer names and links (e.g., "### Seiscan", "### SeiStream"). The content appears to be missing or failed to render.
   Why: This is a broken page — developers looking for block explorer information will find no useful content.

4. Section: Sei Branding
   Quote: "Sei Branding Please adhere to these guidelines when featuring Sei in marketing communications"
   Suggestion: Fix the description metadata to read "Please adhere to these guidelines when featuring Sei in marketing communications" (remove the duplicate "Sei Branding" prefix that appears in the link text on the Learn page).
   Why: The current description reads "Sei Branding Please adhere to these guidelines..." which is grammatically broken and looks like a concatenation error.

5. Section: Staking
   Quote: "When a validator misbehaves and gets jailed... Note that misbehaviors are currently not penalized in the system, so there are no slashing consequences for validator misconduct."
   Suggestion: Reconcile this with the "Slashing" subsection which states "There is no slashing of funds in Sei" and with the Technical Reference which lists "Slashing Conditions: Downtime: 0.01%, Double Sign: 5%". Either the slashing parameters in the Technical Reference are incorrect/aspirational, or the Staking page needs updating. Add a clear note explaining the current state.
   Why: Contradictory information about slashing across pages will confuse validators making operational decisions about risk.

6. Section: Bank Precompile
   Quote: "SEI Native: While reading from chain it is formatted to 6 decimal places (1 SEI = 1,000,000 usei) and while writing to chain it is parsed to 18 decimal places."
   Suggestion: This is confusing and potentially misleading. Clarify that sendNative() accepts msg.value in 18-decimal wei (like all EVM payable functions), but the underlying Cosmos bank module uses 6-decimal usei. The balance() function returns amounts in 6-decimal usei. Add a concrete example: "To send 1 SEI via sendNative(), pass ethers.parseEther('1') (18 decimals). To read 1 SEI from balance(), expect 1000000 (6 decimals)."
   Why: The current phrasing ("while reading...formatted to 6...while writing...parsed to 18") is ambiguous and will cause developers to use incorrect decimal conversions.

7. Section: Accounts on Sei EVM and Cosmos-SDK — "Deriving Addresses from the Public Key"
   Quote: "Sei Address Derivation: 1. Hash the public key using the keccak256 algorithm. 2. Extract the first 20 bytes..."
   Suggestion: This description is incorrect for standard Cosmos address derivation. Cosmos (Sei) bech32 addresses are typically derived using SHA-256 + RIPEMD-160 (as shown in the Python/TypeScript code examples further down the same page), not keccak256. Update the text to match the actual code examples, or clarify that Sei uses a non-standard keccak-based derivation.
   Why: The prose contradicts the code examples on the same page, which correctly use SHA-256 + RIPEMD-160. Developers reading only the summary will implement it incorrectly.

8. Section: Sei Giga Overview / Technical Specifications
   Quote: "200K+ TPS Simple transfers" and "5 Gigagas/s"
   Suggestion: Add a prominent note on the Sei Giga Developer Guide page that these are target specifications for an unreleased upgrade, not current network capabilities. The Developer Guide page currently says "Why Build on Sei Giga?" without clarifying it's not yet live.
   Why: Developers may build applications expecting 200K TPS today. The distinction between current (100 MGas/s) and future (5 Gigagas/s) capabilities needs to be unmistakable on every page that mentions Giga.

9. Section: Quick Reference / Prerequisites
   Quote: "Sei EVM uses the Pectra EVM version (without blob transactions)."
   Suggestion: Also mention that Sei supports EIP-7702 (SetCode transactions), as stated in the Divergence from Ethereum page. This is a notable feature developers will want to know about upfront.
   Why: EIP-7702 support is a significant differentiator and is mentioned deep in the docs but not in the quick reference where developers first look.

10. Section: Example — Deploy a contract with Hardhat
    Quote: solidity: "0.8.26"
    Suggestion: Update to "0.8.28" to match the version used consistently in the Hardhat and Foundry tutorial pages throughout the docs.
    Why: Inconsistent Solidity versions between the quick-start example and the detailed tutorials may cause confusion or compilation issues if developers mix code from different sections.

11. Section: PointerView Precompile — Import Precompile Components (JavaScript)
    Quote: "function getCW721Pointer(string) view returns (address, uint16, bool)"\n"function getCW1155Pointer(string) view returns (address, uint16, bool)"
    Suggestion: Add a missing comma between the getCW721Pointer and getCW1155Pointer ABI entries in the array. The current code will throw a JavaScript syntax error.
    Why: Copy-paste of this code will fail at runtime due to the missing comma in the ABI array.

12. Section: Governance Precompile Usage — Complete Integration Example
    Quote: console.log(\💰 Total deposited: ${ethers.formatEther(depositAmount.add(additionalDeposit))} SEI`);**Suggestion**: Replace.add()with the+operator:depositAmount + additionalDeposit. In ethers.js v6, BigInt values use native arithmetic operators, not .add(). **Why**: This code will throw a runtime error with ethers.js v6, which is the version used throughout the docs. The .add()` method was ethers.js v5 syntax.

13. Section: SIP-03 Migration
    Quote: "Holders of USDC.n must swap or migrate before end of March 2026."
    Suggestion: If this deadline has passed (or is approaching), add a status banner indicating whether the migration is complete, still in progress, or if the deadline has been extended. As documentation is read at different times, a static date without status context becomes stale.
    Why: Developers and users reading this after March 2026 won't know if the migration already happened or if they still need to act.

14. Section: Sei EVM Networks
    Quote: The networks table shows MetaMask integration buttons but the local development chain entry is missing.
    Suggestion: Add a "Local Development" row to the networks table with Chain ID 713714 (0xAE3F2), RPC URL http://localhost:8545 as shown on the homepage, to match the network info at the bottom of the documentation homepage.
    Why: The homepage lists a local devnet chain ID (713714) but the dedicated Networks page doesn't mention it, making it hard for developers to find local development configuration.

15. Section: Divergence from Ethereum
    Quote: "SSTORE Gas Cost... Currently, the SSTORE gas cost is set to the non-standard value of 72,000 gas."
    Suggestion: Add this critical information to the Gas page (/learn/dev-gas) as well, and mention it in the "Optimizing Contracts for Parallelization" best practices page. A 3.6× higher SSTORE cost than Ethereum (72k vs 20k) significantly impacts gas optimization strategies.
    Why: The SSTORE cost difference is buried in the Divergence page but is one of the most impactful cost differences for contract developers. Many developers will never read the Divergence page but will read the Gas and optimization pages.