docs: post-#27 follow-up — correctness fixes + Vale prose cleanup

.github/styles/Sei/Terminology.yml

@@ -11,7 +11,9 @@ swap:
   'the Sei blockchain': Sei
   'Sei [Cc]hain': Sei
   'gas fees?': gas
-  '\bCW\b': CosmWasm
+  # Bare 'CW' is accepted shorthand for CosmWasm here — the standard names
+  # CW20/CW721/CW1155 plus phrases like "CW pointer", "CW-based", and "CW NFT".
+  # CosmWasm casing is still enforced by the rule below, so we don't flag bare CW.
   '[Cc]osmwasm': CosmWasm
   '[Mm]etamask': MetaMask
   'Sei-?[Jj][Ss]': sei-js

ai/cambrian-agent-kit.mdx

@@ -51,7 +51,7 @@ This tutorial guides you through:
 - Node.js & npm installed
 - SEI wallet private key
 - OpenAI API key (for AI integrations)
-- **Minimum SEI balance**: Ensure you have sufficient SEI for gas fees
+- **Minimum SEI balance**: Ensure you have sufficient SEI for gas
 
 ### 2. Project Setup
 

ai/x402.mdx

@@ -6,20 +6,20 @@
 ---
 x402 Protocol brings HTTP micro payments to Sei, enabling you to monetize APIs, premium content, and digital services with instant, low-cost payments. Whether you're building AI APIs, data feeds, or premium content platforms, x402 makes it simple to add payment gates to any HTTP endpoint.
 
-**Works with Sei's advantages:** Sei's fast finality, low gas fees, and EVM compatibility make it perfect for micro payments. x402 leverages these features to enable seamless payment flows that complete in milliseconds.
+**Works with Sei's advantages:** Sei's fast finality, low gas, and EVM compatibility make it perfect for micro payments. x402 leverages these features to enable seamless payment flows that complete in milliseconds.
 
 
 <Info>
 
 **Why x402 on Sei?**
 
-- **Fast & Cheap Payments**: Sei's 400ms finality and low gas fees make micropayments practical. Perfect for pay-per-request APIs and streaming content.
+- **Fast & Cheap Payments**: Sei's 400ms finality and low gas make micropayments practical. Perfect for pay-per-request APIs and streaming content.
 - **EVM Compatible**: Use familiar tools like Viem, Ethers.js, and Hardhat. All existing Ethereum tooling works seamlessly on Sei.
 - **Built-in Wallet Support**: Integrates with Sei wallets, MetaMask, and any EIP-6963 compatible wallet for smooth user experiences.
 
 </Info>
 
 ## Use Cases on Sei
 
 The x402 protocol enables a wide range of monetization strategies for web services and APIs:
 
@@ -32,14 +32,14 @@
 
 The `sei-js` library provides a suite of packages to simplify working with x402 on Sei. You can find more details in the [sei-js x402 repository](https://github.com/sei-protocol/sei-x402).
 
 ### Core Concepts
 
 - [**Protocol Overview**](https://github.com/sei-protocol/sei-x402/blob/main/docs/core-concepts/client-server.md): Learn about the architecture of x402.
 - [**Quickstart Guide**](https://github.com/sei-protocol/sei-x402/blob/main/docs/getting-started/quickstart-for-sellers.md): Build your first paid API.
 - [**Facilitators**](https://github.com/sei-protocol/sei-x402/blob/main/docs/core-concepts/facilitator.md): Understanding payment facilitators.
 - [**Client Integration**](https://github.com/sei-protocol/sei-x402/blob/main/docs/getting-started/quickstart-for-buyers.md): How to integrate x402 in your frontend.
 
 ### Available Packages
 
 - [**x402**](https://www.npmjs.com/package/@sei-js/x402): The core protocol implementation.
 - [**x402-fetch**](https://www.npmjs.com/package/@sei-js/x402-fetch): A fetch wrapper for making x402-compliant requests.
@@ -52,7 +52,7 @@
 
 ---
 
 ## Axiom Kit Integration
 
 While you can build x402 integrations using standard tools and the libraries mentioned above, you can also optionally use Axiom Kit for a more agent-centric approach. This guide demonstrates an end-to-end x402 (HTTP 402 Payment Required) micropayment flow on the Sei testnet using AxiomKit.
 
@@ -60,7 +60,7 @@
 
 x402 is an open standard protocol for internet-native payments that enables users to send and receive payments globally in a simple, secure, and interoperable manner. The protocol leverages the HTTP 402 status code ("Payment Required") to facilitate blockchain-based micropayments directly through HTTP requests.
 
 #### Key Features of x402:
 
 - **HTTP-Native**: Uses standard HTTP status codes and headers
 - **Blockchain Integration**: Supports multiple blockchain networks
@@ -68,7 +68,7 @@
 - **Interoperable**: Works across different payment schemes and networks
 - **Micropayment Support**: Designed for small, frequent transactions
 
 ### Protocol Overview
 
 The x402 protocol follows a specific flow:
 
@@ -82,18 +82,18 @@
 
 Axiom is a blockchain interaction framework that provides tools and libraries for building decentralized applications. In this implementation, Axiom integrates with x402 to enable seamless blockchain payments within Sei network applications.
 
 #### Axiom Components Used:
 
 - **@axiomkit/core**: Core framework for building blockchain agents
 - **@axiomkit/sei**: Sei blockchain integration
 - **AxiomSeiWallet**: Wallet management for Sei transactions
 - **Context and Actions**: Framework for building interactive blockchain agents
 
 ### Sei Blockchain Implementation
 
 This implementation uses the Sei testnet for x402 payments with the following configuration:
 
 #### Network Configuration
 
 ```typescript
 export const X402_CONFIG = {
@@ -107,11 +107,11 @@
 };
 ```
 
 ### Technical Architecture
 
 The x402 implementation consists of several key components:
 
 #### 1. Payment Challenge Generation
 
 ```typescript
 function generatePaymentChallenge() {
@@ -142,7 +142,7 @@
 }
 ```
 
 #### 2. Payment Verification
 
 ```typescript
 async function verifyPayment(paymentHeader: string) {
@@ -163,7 +163,7 @@
 }
 ```
 
 #### 3. Axiom Agent Integration
 
 The Axiom agent handles the complete x402 flow:
 
@@ -201,16 +201,16 @@
 });
 ```
 
 ### Payment Flow
 
 #### 1. Initial Request
 
 ```
 Client → GET /api/weather
 Server → 402 Payment Required + Payment Challenge
 ```
 
 #### 2. Payment Challenge Response
 
 ```json
 {
@@ -236,7 +236,7 @@
 }
 ```
 
 #### 3. Payment Execution
 
 The Axiom agent executes a USDC transfer on Sei testnet:
 
@@ -264,16 +264,16 @@
 });
 ```
 
 #### 4. Payment Proof Submission
 
 ```
 Client → GET /api/weather + X-Payment Header (base64 encoded payment proof)
 Server → Verifies payment + Returns weather data
 ```
 
 ### Code Examples
 
 #### Complete Weather API Implementation
 
 ```typescript
 export async function GET(req: NextRequest) {
@@ -309,7 +309,7 @@
 }
 ```
 
 #### Axiom Agent Weather Action
 
 ```typescript
 action({
@@ -392,29 +392,29 @@
 });
 ```
 
 ### Security Considerations
 
 #### Payment Verification
 
 - **On-chain Verification**: All payments are verified against the Sei blockchain.
 - **Transaction Receipt Validation**: Ensures transaction success and proper recipient.
 - **Payment Caching**: Prevents double-spending by caching verified payments.
 - **Reference Validation**: Unique payment references prevent replay attacks.
 
 #### Network Security
 
 - **HTTPS Required**: All API communications use secure connections.
 - **Base64 Encoding**: Payment proofs are base64 encoded for safe transmission.
 - **Timeout Handling**: Payment challenges include timeout mechanisms.
 - **Error Handling**: Comprehensive error handling prevents information leakage.
 
 #### Wallet Security
 
 - **Private Key Management**: Private keys are stored securely in environment variables.
 - **Transaction Signing**: All transactions are properly signed before submission.
 - **Balance Validation**: Sufficient balance checks before payment execution.
 
 ### Tutorials & Resources
 
 - **[Sei-js X402 Repository](https://github.com/sei-protocol/sei-x402)**: Comprehensive guide on using the x402 protocol with the sei-js library, including package details and examples.
 - **[AxiomKit X402 Demo Repository](https://github.com/AxiomKit/axiomkit-showcase)**: The complete source code for the Axiom integration demo used in this guide, including installation and configuration instructions.

evm/ai-tooling/cambrian-agent-kit.mdx

@@ -8,7 +8,7 @@
 
 Cambrian Agent Kit is a developer SDK for building powerful, autonomous AI agents and agentic chatbots on the SEI blockchain. It lets you interact with DeFi protocols (Takara, Silo, Citrex, Symphony), manage SEI tokens and NFTs, and seamlessly integrate AI workflows. In this tutorial, you'll learn how to set up the kit, run your first agent, and use it for real DeFi use cases—customized for your needs. To understand more and deep dive into how it works under the hood, please refer to the [Cambrian Agent Kit Documentation](https://deepwiki.com/CambrianAgents/sei-agent-kit/1-overview).
 
 ## Supported Features
 
 The SEI Agent Kit supports a comprehensive set of features for blockchain agent development:
 
@@ -44,16 +44,16 @@
 
 </Info>
 
 ## Hands-on Tutorial
 
 ### 1. Prerequisites
 
 - Node.js & npm installed
 - SEI wallet private key
 - OpenAI API key (for AI integrations)
-- **Minimum SEI balance**: Ensure you have sufficient SEI for gas fees
+- **Minimum SEI balance**: Ensure you have sufficient SEI for gas
 
 ### 2. Project Setup
 
 ```bash
 git clone https://github.com/CambrianAgents/sei-agent-kit.git
@@ -77,7 +77,7 @@
 
 </Warning>
 
 ### 3. Running Your First Agent
 
 ```bash
 npm run test
@@ -167,9 +167,9 @@
 
 </Info>
 
 ### 4. Explore Core Features & Protocols
 
 #### a) Check Token Balance with Error Handling
 
 ```typescript
 import { SeiAgentKit } from './src/agent';
@@ -199,7 +199,7 @@
 }
 ```
 
 #### b) Safe Token Swapping with Symphony
 
 ```typescript
 async function safeSwap() {
@@ -250,7 +250,7 @@
 
 </Warning>
 
 #### c) Liquid Staking with Silo Protocol
 
 ```typescript
 async function stakingWithSilo() {
@@ -292,7 +292,7 @@
 
 </Info>
 
 #### d) Lending/Borrowing with Takara Protocol
 
 ```typescript
 async function takaraLending() {
@@ -332,7 +332,7 @@
 }
 ```
 
 #### e) Perpetual Trading with Citrex Markets
 
 ```typescript
 async function citrexTrading() {
@@ -370,9 +370,9 @@
 
 <Info>See `/tools/` for more advanced protocol integrations!</Info>
 
 ## Error Handling & Troubleshooting
 
 ### Common Error Types
 
 <Info>
 **Comprehensive Error Handling Examples:**
@@ -416,7 +416,7 @@
 
 </Info>
 
 ### Transaction Monitoring
 
 ```typescript
 async function monitorTransaction(txHash: string) {
@@ -450,7 +450,7 @@
 }
 ```
 
 ### Troubleshooting Guide
 
 | Issue | Cause | Solution |
 | --- | --- | --- |
@@ -473,9 +473,9 @@
 # Use Seiscan: https://seiscan.io/
 ```
 
 ### 5. Advanced Features & Customization
 
 #### Multi-Protocol Strategy Example
 
 ```typescript
 async function deFiStrategy() {
@@ -507,7 +507,7 @@
 }
 ```
 
 #### Monitoring & Alerts:
 
 ```typescript
 // Set up monitoring for your agent
@@ -531,6 +531,6 @@
 }
 ```
 
 #### Custom Protocol Integration
 
 To extend the Cambrian Agent Kit for your own protocol, please follow this repository which explains how to add plugins to the agent kit so that it can support your protocol: [Cambrian Agents Plugin Guide](https://github.com/CambrianAgents/cambrian-plugin)

evm/bridging/layerzero.mdx

@@ -8,7 +8,7 @@
 
 This guide provides a comprehensive, step-by-step tutorial for integrating LayerZero V2 with the SEI blockchain. By the end of this guide, you will understand how to create, deploy, and manage omnichain tokens that can seamlessly move between SEI and any other LayerZero-supported blockchain.
 
 ### What This Guide Covers
 
 - **Understanding LayerZero**: Core concepts and architecture
 - **Project Setup**: Creating a LayerZero-enabled project from scratch
@@ -20,21 +20,21 @@
 
 - Basic knowledge of Solidity and smart contracts
 - Node.js and npm installed
-- A wallet with SEI and other chain tokens for gas fees
+- A wallet with SEI and other chain tokens for gas
 - Familiarity with Hardhat or Foundry
 
 ## What is LayerZero?
 
 LayerZero is an **omnichain interoperability protocol** that enables secure, permissionless communication between different blockchains. Think of it as a universal translator that allows blockchains to talk to each other.
 
 ### Core Concepts
 
 - **Endpoints**: Immutable smart contracts deployed on each blockchain that serve as entry/exit points for messages
 - **Messages**: Data packets sent between blockchains containing instructions or information
 - **Security Stack**: Customizable verification system ensuring message authenticity
 - **Omnichain Applications**: Smart contracts that can operate across multiple blockchains
 
 ### Key Applications
 
 - **Omnichain Fungible Tokens (OFT)**: Tokens that exist across multiple chains with unified supply
 - **Omnichain NFTs (ONFT)**: NFTs that can move between blockchains
@@ -42,7 +42,7 @@
 - **Unified Governance**: DAOs that function across chains
 - **Message Passing**: Send arbitrary data between blockchains
 
 ## SEI Network Information
 
 <Info>
 **SEI Mainnet Configuration**
@@ -56,7 +56,7 @@
 
 </Info>
 
 ### Contract Deployments
 
 The following are the official LayerZero V2 protocol contract addresses deployed on Sei networks.
 
@@ -108,7 +108,7 @@
 
 </Accordion>
 
 ## Step 1: Project Setup
 
 ### Project scaffold
 
@@ -130,7 +130,7 @@
 
 At a minimum, you need to have the `PRIVATE_KEY`. RPC URLs are optional, but strongly recommended. If you don't provide them, public RPCs will be used, but public RPCs can be unreliable or slow, leading to long waiting times for transactions to be confirmed or, at worst, cause your transactions to fail.
 
 ## Step 2: Configure Networks
 
 ### Hardhat network config
 
@@ -154,7 +154,7 @@
 }
 ```
 
 ### LayerZero wiring config
 
 Modify your `layerzero.config.ts` file to include the chains and channel security settings you want for each connection:
 
@@ -228,11 +228,11 @@
 
 </Info>
 
 ## Step 3: Create Utility Tasks
 
 Before deployment, let's create a utility task for minting tokens that we'll need later.
 
 ### Create Minting Task
 
 Create `tasks/mint.ts`:
 
@@ -267,7 +267,7 @@
   });
 ```
 
 ### Update Hardhat Configuration
 
 Now update your `hardhat.config.ts` to import the mint task:
 
@@ -349,7 +349,7 @@
 
 <Warning>**Important**: You must create and import the mint task before deployment, otherwise Hardhat will throw an error when trying to resolve the task dependencies during compilation.</Warning>
 
 ## Step 4: Smart Contract Development
 
 ### The token contract
 
@@ -391,7 +391,7 @@
 
 </Warning>
 
 ### Understanding OFT Functions
 
 Key inherited functions from the OFT contract:
 
@@ -403,7 +403,7 @@
 | `_lzReceive()` | Internal function that receives messages |
 
 
 ## Step 5: Deployment Process
 
 ### Deploy
 
@@ -415,7 +415,7 @@
 
 <Warning>Fund your deployer with native gas tokens beforehand.</Warning>
 
 ## Step 6: Wire the Contracts
 
 After deployment, contracts need to be connected:
 
@@ -425,7 +425,7 @@
 npx hardhat lz:oapp:wire --oapp-config layerzero.config.ts
 ```
 
 ### Verify Configuration
 
 Verify peers:
 
@@ -435,7 +435,7 @@
 
 This command will show you the current LayerZero wiring configuration, including the connected chains and their peer addresses.
 
 ## Step 7: Mint Initial Tokens
 
 Before transferring, you need tokens to send. Let's mint some tokens on SEI:
 
@@ -444,13 +444,13 @@
 npx hardhat mint --to 0xYourAddress --amount 10000 --network sei-mainnet
 ```
 
 ## Step 8: Transfer Tokens Cross-Chain
 
 ### Calling send
 
 Since the `send` logic has already been defined, we'll instead view how the function should be called.
 
 #### Option 1: Hardhat Task
 
 Create `tasks/sendOFT.ts`:
 
@@ -554,7 +554,7 @@
   --network sei-mainnet
 ```
 
 #### Option 2: Foundry Script
 
 Create `script/SendOFT.s.sol`:
 
@@ -630,11 +630,11 @@
 forge script script/SendOFT.s.sol:SendOFT --rpc-url $RPC_URL_SEI --broadcast
 ```
 
 ## Step 9: Done!
 
 You've issued an omnichain token and bridged it from Sei Mainnet to Optimism. Customize supply logic, fees, or add more chains by applying changes to the core contract, redeploying, and repeating the wiring step.
 
 ### Track Your Transaction
 
 1. Visit https://layerzeroscan.com/tx/YOUR_TX_HASH
 2. You'll see:
@@ -646,7 +646,7 @@
 
 ## Troubleshooting
 
 ### Common Issues and Solutions
 
 <Danger>
 **Quote Send Reverts**
@@ -699,14 +699,14 @@
 
 </Tip>
 
 ## Next Steps
 
 - **Add More Chains**: Expand to Arbitrum, Base, Polygon, etc.
 - **Advanced Features**: Implement rate limiting, pausable transfers, fee collection
 - **Composed Messages**: Execute actions after token arrival
 - **Build a UI**: Create a frontend for easy transfers
 
 ### Learn More
 
 - See the [Configuring Pathways](https://docs.layerzero.network/v2/get-started/create-lz-oapp/configuring-pathways) section to learn more about managing your OFTs across the entire network mesh.
 - See the [Available DVNs](https://docs.layerzero.network/v2/deployments/dvn-addresses?chains=sei) and [Executor](https://docs.layerzero.network/v2/deployments/deployed-contracts?chains=sei) to configure between.

evm/differences-with-ethereum.mdx

@@ -47,7 +47,7 @@
   - User accounts on Sei have [two addresses](/learn/accounts) derived from the same public key (Cosmos Bech32 and EVM-compatible 0x…)
   - Interoperability between EVM and Cosmos-SDK modules is governed and navigated via [precompiles](/evm/precompiles/example-usage) and [pointer contracts](/learn/pointers)
 
 ## Sei EVM Release
 
 Sei EVM was originally deployed at the following block heights and versions:
 
@@ -63,7 +63,7 @@
 - **Height:** `79123881`
 - **Changelog:** https://github.com/sei-protocol/sei-chain/blob/main/CHANGELOG.md#v552
 
 ## Opcode Differences
 
 | Opcode | Sei EVM | Ethereum | Notes |
 | --- | --- | --- | --- |
@@ -77,10 +77,10 @@
 | Blob‑related opcodes | Not supported (Pectra without blobs) | Supported post‑Cancun (EIP‑4844) | Blob transactions are not enabled on Sei. |
 
 
 ### PREVRANDAO
 
 Since Sei doesn't rely on the same pseudo‑randomness way of determining the next
-validator like Proof of Stake (PoS) Ethereum does, it doesn't really have the
+validator like Proof of Stake (PoS) Ethereum does, it doesn't have the
 "randomness" artifact that can be set as `PREVRANDAO`'s return value. On Sei,
 `PREVRANDAO` returns a value derived from the current block time. For strong
 randomness needs in contract logic, use a verifiable randomness oracle (as is
@@ -91,19 +91,19 @@
 Coinbase address on Sei is always set to (the EVM address of) the global fee
 collector.
 
 ## State Root
 
 Since Sei uses AVL-tree instead of Merkle Patricia Trie (MPT) for data storage,
 Sei doesn't have per-account state root. The global state root is the AVL-tree
 root which is also not equivalent to Ethereum's overall state root (which is a
 MPT root)
 
 ## Block Hash
 
 The block hash on Sei is computed based on the block header in Tendermint data
 format, and is different from Ethereum's block Hash as a result.
 
 ## Base Fee & Tips
 
 Sei supports all non‑blob transaction types, including the Pectra `SetCode` transaction (EIP‑7702). However for a legacy (non EIP‑1559) type
 transaction, you must specify a gas price at or above Sei's governance-set minimum gas price (currently `50 gwei` on mainnet). Query the live value with `eth_gasPrice` rather than hard-coding it. In addition to this, excess
@@ -128,7 +128,7 @@
 value: '"0.007500000000000000"'
 ```
 
 ## Non-EVM Transactions
 
 On Sei there exists non-EVM transactions which may update states accessible by
 EVM transactions. The simplest example would be bank balances, which may be
@@ -142,7 +142,7 @@
 committed (~400 ms) — meaning that commitment levels of "safe", "latest",
 "justified", and "finalized" on Ethereum are all the same thing on Sei.
 
 ## Pending State
 
 On Ethereum the block proposer would execute its proposed block first (and
 update its local state) before broadcasting the proposal to others (the updated
@@ -150,10 +150,10 @@
 
 However, on Sei, the block proposer would broadcast first and only execute the
 proposal if it's accepted (i.e. every node would execute the block at roughly
-the same time), so Sei does not really have a window when "pending state"
+the same time), so Sei does not have a window when "pending state"
 exists.
 
 ## Gas Model & Fees
 
 Sei does not implement base‑fee burning. There is no base‑fee burn; all transaction fees accrue to validators. Fees are calculated as:
 
@@ -175,7 +175,7 @@
 
 </Info>
 
 ## SSTORE Gas Cost
 
 On Sei, the `SSTORE` opcode gas cost is configurable as an on-chain parameter, meaning it can be adjusted via governance proposal without requiring a chain upgrade.
 
@@ -185,7 +185,7 @@
 
 <Info>Since `SSTORE` is a governance-controlled parameter, this value may change in the future through a governance proposal.</Info>
 
 ## ERC Token Standards Compatibility
 
 Sei’s EVM fully supports the common token standards:
 
@@ -195,7 +195,7 @@
 
 Existing OpenZeppelin contracts and tools work unchanged.
 
 ## Testing & Migration Checklist
 
 - ✅ Re‑deploy your Solidity code to Sei testnet; most contracts need no changes.
 - ✅ If you used SELFDESTRUCT, refactor to a soft‑close pattern.

evm/evm-foundry.mdx

@@ -16,7 +16,7 @@
 
 </Tip>
 
 ## Table of Contents
 
 - [Prerequisites](#prerequisites)
 - [Setting Up Your Development Environment](#setting-up-your-development-environment)
@@ -33,10 +33,10 @@
 
 - [Foundry](https://book.getfoundry.sh/) installed on your system
 - A basic understanding of Solidity and smart contract development
-- A wallet with SEI tokens for gas fees
+- A wallet with SEI tokens for gas
 - [Node.js](https://nodejs.org/) (v18.0.0 or later) for ethers.js interactions
 
 ## Setting Up Your Development Environment
 
 First, let's install Foundry if you haven't already. Follow the [installation guide](https://book.getfoundry.sh/getting-started/installation) or use the quick install command:
 
@@ -90,7 +90,7 @@
 
 <Warning>Add `.env` to your `.gitignore` file to prevent committing sensitive information such as your `PRIVATE_KEY` and potentially lose funds.</Warning>
 
 ## Using OpenZeppelin Contracts
 
 OpenZeppelin provides a library of secure, tested smart contract components. Let's install OpenZeppelin contracts:
 
@@ -104,7 +104,7 @@
 forge remappings > remappings.txt
 ```
 
 ## Creating and Deploying Smart Contracts
 
 Let's create different types of smart contracts. Choose from the tabs below based on what you want to build:
 
@@ -349,7 +349,7 @@
   </Tab>
 </Tabs>
 
 ## Testing Your Smart Contracts
 
 Foundry provides excellent testing capabilities. Let's create comprehensive tests for our contracts.
 
@@ -552,11 +552,11 @@
 forge test -vvv
 ```
 
 ## Deploying to Sei Testnet and Mainnet
 
 Now let's deploy our contracts to the Sei networks. You can use either Forge scripts or direct deployment commands.
 
 ### Using Forge Scripts (Recommended)
 
 Deploy to Sei testnet:
 
@@ -570,7 +570,7 @@
 forge script script/DeployCounter.s.sol --rpc-url $SEI_MAINNET_RPC --private-key $PRIVATE_KEY --broadcast
 ```
 
 ### Using Direct Forge Create Commands
 
 Alternatively, you can deploy directly:
 
@@ -595,11 +595,11 @@
 Transaction hash: 0xYOUR_TX_HASH
 ```
 
 ## Interacting with Deployed Contracts
 
 Once deployed, you can interact with your contracts using Foundry's `cast` tool or ethers.js.
 
 ### Using Cast Commands
 
 ```bash
 # Query the counter value

evm/evm-hardhat.mdx

@@ -16,7 +16,7 @@
 
 </Tip>
 
 ## Table of Contents
 
 - [Prerequisites](#prerequisites)
 - [Setting Up Your Development Environment](#setting-up-your-development-environment)
@@ -34,7 +34,7 @@
 - [npm](https://www.npmjs.com/) (v7.0.0 or later) or [yarn](https://yarnpkg.com/)
 - A code editor (VS Code recommended)
 
 ## Setting Up Your Development Environment
 
 Let's create a new project and set up Hardhat:
 
@@ -123,11 +123,11 @@
 
 <Warning>Use a dedicated, throwaway deploy key funded with only what you need — never a personal wallet holding real funds.</Warning>
 
 ## Using OpenZeppelin Contracts
 
 OpenZeppelin provides a library of secure, tested smart contract components that you can use to build your applications. The `@openzeppelin/contracts` package was already installed during setup, so you're ready to import its contracts directly.
 
 ## Creating and Deploying an ERC20 Token, ERC721 NFT or an Upgradeable UUPS Token
 
 <Tabs>
   <Tab title="ERC20">
@@ -283,7 +283,7 @@
 import { network } from 'hardhat';
 
 // Hardhat 3 exposes ethers through a network connection rather than a global import
-const { ethers } = await network.getOrCreate();
+const { ethers } = await network.create();
 
 const [deployer] = await ethers.getSigners();
 console.log('Deploying contracts with the account:', deployer.address);
@@ -395,7 +395,7 @@
 ```typescript title="scripts/deploy-upgradeable-token.ts"
 import { network } from 'hardhat';
 
-const { ethers } = await network.getOrCreate();
+const { ethers } = await network.create();
 
 const [deployer] = await ethers.getSigners();
 console.log('Deploying contracts with the account:', deployer.address);
@@ -459,7 +459,7 @@
 ```typescript title="scripts/upgrade-token.ts"
 import { network } from 'hardhat';
 
-const { ethers } = await network.getOrCreate();
+const { ethers } = await network.create();
 
 // !! REPLACE WITH YOUR PROXY ADDRESS from the deploy step !!
 const PROXY_ADDRESS = '0xYOUR_PROXY_CONTRACT_ADDRESS_HERE';
@@ -492,7 +492,7 @@
 </Tab>
 </Tabs>
 
 ## Testing Your Smart Contracts
 
 Hardhat makes it easy to test your contracts before deploying them. Create a test file `test/sei-token-test.ts`:
 
@@ -509,7 +509,7 @@
 
   beforeEach(async function () {
     // Hardhat 3 exposes ethers through a network connection
-    ({ ethers } = await network.getOrCreate());
+    ({ ethers } = await network.create());
 
     // Get signers
     [owner, addr1, addr2] = await ethers.getSigners();
@@ -576,11 +576,11 @@
 npx hardhat test
 ```
 
 ## Deploying to Sei Testnet and Mainnet
 
 Once you've tested your contracts, you can deploy them to the Sei testnet or mainnet. To deploy, you'll need:
 
-1. SEI tokens in your wallet for gas fees
+1. SEI tokens in your wallet for gas
 2. Your private key stored in the encrypted keystore (`npx hardhat keystore set SEI_PRIVATE_KEY`) — or exported as a `SEI_PRIVATE_KEY` environment variable in CI
 
 Deploy to the testnet:

evm/indexer-providers/moralis.mdx

@@ -7,7 +7,7 @@
 
 Moralis provides a comprehensive Backend-as-a-Service (BaaS) platform specifically designed for developers. By abstracting away the complexity of blockchain integration and offering a suite of APIs, SDKs, and scalable infrastructure, Moralis allows developers to focus on building the core functionality of their applications.
 
 ## What You'll Learn
 
 By the end of this tutorial, you'll understand:
 
@@ -26,7 +26,7 @@
 3. **Package Manager**: npm, yarn, or pnpm
 4. **TypeScript**: Basic knowledge (optional but recommended)
 
 ### Sei Network Configuration
 
 <Info>Following is the configuration details of Sei for Moralis integration:</Info>
 
@@ -40,7 +40,7 @@
 - Chain ID: 1328 (0x530)
 - RPC URL: https://evm-rpc-testnet.sei-apis.com
 
 ## Moralis APIs Overview
 
 Moralis offers several powerful APIs that work seamlessly across multiple blockchains:
 
@@ -51,9 +51,9 @@
 - **Price API**: Retrieve real-time and historical crypto token prices
 - **DeFi API**: Query DeFi protocol data including pools, positions, and yields
 
 ## Setting Up Your Project
 
 ### Install Moralis SDK
 
 First, create a new project and install the Moralis SDK:
 
@@ -73,13 +73,13 @@
 npm install typescript ts-node @types/node --save-dev
 ```
 
 ### Get Your API Key
 
 1. Sign up at [moralis.io](https://moralis.io)
 2. Navigate to "Project Settings"
 3. Copy your API key from the dashboard
 
 ### Basic Configuration
 
 Create a `.env` file in your project root:
 
@@ -89,7 +89,7 @@
 SEI_TESTNET_CHAIN_ID=0x530
 ```
 
 ## Initialize Moralis
 
 Create an `index.ts` or `index.js` file:
 
@@ -108,7 +108,7 @@
 initMoralis();
 ```
 
 ## Wallet Transactions API
 
 ```typescript
 // Get wallet transactions for Sei mainnet
@@ -132,7 +132,7 @@
 getWalletTransactions(walletAddress);
 ```
 
 ## NFT Holders API
 
 ```typescript
 // Get NFTs owned by wallet address
@@ -168,7 +168,7 @@
 };
 ```
 
 ## Transaction Details API
 
 ```typescript
 // Get detailed transaction information
@@ -256,7 +256,7 @@
 };
 ```
 
 ## Complete Integration Example
 
 Here's a comprehensive example that brings everything together:
 
@@ -334,9 +334,9 @@
 main();
 ```
 
 ## Working with Testnet
 
-<Warning>To switch to Sei testnet, simply change the chain ID in your API calls.</Warning>
+<Warning>To switch to Sei testnet, change the chain ID in your API calls.</Warning>
 
 ```typescript
 // Testnet configuration

evm/indexer-providers/the-graph.mdx

@@ -9,7 +9,7 @@
 infrastructure relies on a decentralized network of indexers, enabling your dapp
 to become truly decentralized.
 
 ## Quick Start
 
 These subgraphs only take a few minutes to set up. To get started, follow these
 three steps:
@@ -26,7 +26,7 @@
 
 ## 1. Initialize your subgraph project
 
 ### Create a subgraph on Subgraph Studio⁠
 
 Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your
 wallet. Once your wallet is connected, you can begin by clicking "Create a
@@ -42,7 +42,7 @@
 ![CLI commands](/assets/ecosystem/resources/the-graph/cli_commands.png)
 *CLI Commands*
 
 ### Install the Graph CLI⁠
 
 On your local machine run the following:
 
@@ -50,7 +50,7 @@
 npm install -g @graphprotocol/graph-cli
 ```
 
 ### Initialize your Subgraph⁠
 
 You can copy this directly from your subgraph page to include your specific
 subgraph slug:
@@ -64,13 +64,13 @@
 ![CLI sample](/assets/ecosystem/resources/the-graph/cli_sample.png)
 *CLI*
 
-Simply have your contract verified on the block explorer and the CLI will
+Have your contract verified on the block explorer and the CLI will
 automatically obtain the ABI and set up your subgraph. The default settings will
 generate an entity for each event.
 
 ## 2. Deploy & Publish
 
 ### Deploy to Subgraph Studio⁠
 
 First run these commands:
 
@@ -100,7 +100,7 @@
 ![Playground](/assets/ecosystem/resources/the-graph/playground.png)
 *Run your graphql query in Studio*
 
 ### Publish Your Subgraph to The Graph's Decentralized Network
 
 Once your subgraph is ready to be put into production, you can publish it to the
 decentralized network. On your subgraph's page in Subgraph Studio, click on the
@@ -124,7 +124,7 @@
 
 <Warning>**Note:** The Graph's smart contracts are all on Arbitrum One, even though > your subgraph is indexing data from Ethereum, BSC or any other > [supported chain](https://thegraph.com/docs/en/developing/supported-networks/).</Warning>
 
 ## 3. Query your Subgraph
 
 Congratulations! You can now query your subgraph on the decentralized network!
 
@@ -142,7 +142,7 @@
 The query URL for this subgraph is:
 `https://gateway-arbitrum.network.thegraph.com/api/`**[api-key]**`/subgraphs/id/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK`
 
-Now, you simply need to fill in your own API Key to start sending GraphQL
+Now, you need to fill in your own API Key to start sending GraphQL
 queries to this endpoint.
 
 ### Getting your own API Key
@@ -155,7 +155,7 @@
 
 ## Appendix
 
 ### Sample Query
 
 This query shows the most expensive CryptoPunks sold.
 

evm/precompiles/cosmwasm-precompiles/addr.mdx

@@ -10,7 +10,7 @@
 
 <Info> **What is a precompile?** A precompile is a special smart contract deployed at a fixed address by the Sei protocol itself, that exposes custom native chain logic to EVM-based applications. It acts like a regular contract from the EVM's perspective, but executes privileged, low-level logic efficiently. </Info>
 
 ## How Does the Address Precompile Work?
 
 The Address precompile at address `0x0000000000000000000000000000000000001004` exposes functions like `associate()`, `associatePubKey()`, `getSeiAddr()`, and `getEvmAddr()`.
 
@@ -18,14 +18,14 @@
 - **Native Execution:** Operations are executed at the Cosmos SDK level for maximum efficiency and security.
 - **Seamless Bridge:** No need for separate wallet integrations or complex cross-chain interactions.
 
 ## Use Cases
 
 - **Cross-Chain Identity:** Link EVM and Cosmos addresses for unified user experiences across both execution environments.
 - **Address Resolution:** Build applications that can seamlessly work with both EVM and Cosmos address formats.
 - **Wallet Integration:** Enable users to associate their addresses once and use both EVM and native Sei functionality.
 - **DeFi Applications:** Create protocols that can interact with users regardless of their preferred address format.
 
 ## What You'll Learn in This Guide
 
 By the end of this guide, you'll be able to:
 
@@ -39,7 +39,7 @@
 
 The Address precompile exposes the following functions:
 
 ### Transaction Functions
 
 ```solidity
 /// Associates an account given it's signature of any custom message.
@@ -65,7 +65,7 @@
 ) external returns (string memory seiAddr, address evmAddr);
 ```
 
 ### Query Functions
 
 ```solidity
 /// Queries the corresponding Sei Address for some EVM address.
@@ -83,7 +83,7 @@
 ) external view returns (address response);
 ```
 
 ## Using the Precompile
 
 ### Setup
 
@@ -94,10 +94,10 @@
 - **Node.js** (v18 or higher)
 - **npm** or **yarn** package manager
 - **EVM-compatible wallet**
-- **SEI tokens** for gas fees
+- **SEI tokens** for gas
 - **Hardhat** development environment set up
 
 #### Install Dependencies
 
 Install the required packages for interacting with Sei precompiles:
 
@@ -112,7 +112,7 @@
 npm install @sei-js/precompiles@2.1.2
 ```
 
 #### Setup Hardhat Environment
 
 Create a `hardhat.config.ts` file with the following content:
 
@@ -140,7 +140,7 @@
 npx hardhat keystore set PRIVATE_KEY
 ```
 
 #### Import Precompile Components
 
 <Tabs>
 <Tab title="JavaScript">
@@ -208,7 +208,7 @@
 </Tab>
 </Tabs>
 
 #### When Does Association Happen?
 
 Address association between EVM and Cosmos addresses occurs automatically in most cases:
 
@@ -219,7 +219,7 @@
 | **Manual (PubKey)** | associatePubKey() function | Compressed public key |
 
 
 ### How Association Works
 
 **Automatic Association:**
 
@@ -233,7 +233,7 @@
 - Use `associatePubKey()` for public key-based association
 - Useful for advanced applications or when automatic association hasn't occurred
 
 ### Address Format Requirements
 
 **EVM Addresses:**
 
@@ -246,9 +246,9 @@
 - Validator addresses use `seivaloper1...` prefix
 - Bech32 encoding format
 
 ## Step-by-Step Guide: Using the Address Precompile
 
 ### Associate Address with Signature
 
 <Tabs>
 <Tab title="JavaScript">
@@ -309,7 +309,7 @@
 </Tab>
 </Tabs>
 
 ### Associate Address with Public Key
 
 <Tabs>
 <Tab title="JavaScript">
@@ -352,7 +352,7 @@
 </Tab>
 </Tabs>
 
 ### Query Sei Address from EVM Address
 
 <Tabs>
 <Tab title="JavaScript">
@@ -398,7 +398,7 @@
 </Tab>
 </Tabs>
 
 ### Query EVM Address from Sei Address
 
 <Tabs>
 <Tab title="JavaScript">
@@ -444,7 +444,7 @@
 </Tab>
 </Tabs>
 
 ### Complete Integration Example
 
 <Tabs>
 <Tab title="JavaScript">
@@ -695,24 +695,24 @@
 </Tab>
 </Tabs>
 
 ## Security Considerations & Risks
 
 ### Association Permanence
 
 - **Permanent Mapping:** Once addresses are associated, the mapping cannot be changed or removed
 - **Single Association:** Each address can only be associated with one counterpart
 - **Verification:** Always verify associations before depending on them in critical operations
 
 ### Signature Security
 
 - **Custom Messages:** Use unique, timestamped messages to prevent replay attacks
 - **Message Format:** Follow exact Ethereum Signed Message format for compatibility
 
 ## Troubleshooting
 
 ### Common Issues and Solutions
 
 #### Gas-Related Issues
 
 ```typescript
 // Set appropriate gas limits for different operations
@@ -725,7 +725,7 @@
 });
 ```
 
 ### Error Code Reference
 
 | Error | Cause | Solution |
 | --- | --- | --- |
@@ -736,29 +736,29 @@
 | `invalid address format` | Wrong address format | Use proper EVM (0x...) or Sei (sei1...) format |
 
 
 ## Important Notes
 
 <Info> Remember: Address associations are permanent and cannot be changed once created! </Info>
 
 ### Address Formats
 
 - **EVM Addresses:** Use standard Ethereum format with `0x` prefix
 - **Sei Addresses:** Use Cosmos format with `sei1` prefix for regular addresses
 - **Case Sensitivity:** EVM addresses are case-insensitive, Sei addresses are case-sensitive
 
 ### Association Timing
 
 - **Automatic:** Most users get associated automatically on their first transaction
 - **Manual:** Use precompile functions for programmatic association or when automatic association hasn't occurred
 - **Verification:** Always verify associations exist before depending on them
 
 ### Signature Requirements
 
 - **Message Format:** Must include Ethereum Signed Message prefix for `associate()` function
 - **Component Format:** v, r, s must be properly formatted hex strings
 - **Replay Protection:** Use unique messages to prevent signature replay attacks
 
 ### Gas Considerations
 
 - **Association operations:** ~200,000 gas limit recommended
 - **Query operations:** Standard view function gas usage

evm/precompiles/cosmwasm-precompiles/bank.mdx

@@ -10,7 +10,7 @@
 
 <Info> **What is a precompile?** A precompile is a special smart contract deployed at a fixed address by the Sei protocol itself, that exposes custom native chain logic to EVM-based applications. It acts like a regular contract from the EVM's perspective, but executes privileged, low-level logic efficiently. </Info>
 
 ## How Does the Bank Precompile Work?
 
 The bank precompile at address `0x0000000000000000000000000000000000001001` exposes functions like `send()`, `sendNative()`, `balance()`, `all_balances()`, and token metadata queries.
 
@@ -20,13 +20,13 @@
 
 **When to use `send` vs `sendNative`:** `send` moves an arbitrary `denom` (any IBC or factory token) between two EVM addresses (`0x...`) by reading the balance directly from the bank module — no `msg.value` is attached. It is gated to the registered ERC20 native pointer for that denom, so it is typically invoked from the auto-deployed pointer contract rather than from arbitrary user code. `sendNative` is for sending native SEI (the attached `msg.value`) from the EVM caller to a Cosmos bech32 (`sei1...`) destination, which is useful for crossing the EVM→Cosmos boundary when the recipient has no associated EVM address (for example, paying a Cosmos-only contract or account).
 
 ## Use Cases
 
 - **DeFi Applications:** Build decentralized finance protocols that can handle native SEI and Cosmos assets.
 - **Portfolio Management:** Build tools to track and manage multi-asset portfolios across Cosmos and EVM.
 - **Token Information Services:** Query comprehensive token metadata for UI display and analytics.
 
 ## What You'll Learn in This Guide
 
 By the end of this guide, you'll be able to:
 
@@ -38,7 +38,7 @@
 
 The bank precompile exposes the following functions:
 
 ### Transaction Functions
 
 ```solidity
 /// Sends non-native tokens from one address to another. Callable only by the
@@ -64,7 +64,7 @@
 ) payable external returns (bool success);
 ```
 
 ### Query Functions
 
 ```solidity
 /// Queries the balance of the given account for the specified denom.
@@ -112,7 +112,7 @@
 ) external view returns (uint256 response);
 ```
 
 ## Using the Precompile
 
 ### Setup
 
@@ -123,10 +123,10 @@
 - **Node.js** (v18 or higher)
 - **npm** or **yarn** package manager
 - **EVM-compatible wallet**
-- **SEI tokens** for gas fees and testing transfers
+- **SEI tokens** for gas and testing transfers
 - **Hardhat** for development and testing
 
 #### Install Dependencies
 
 Install the required packages for interacting with Sei precompiles:
 
@@ -141,7 +141,7 @@
 npm install @sei-js/precompiles@2.1.2
 ```
 
 #### Setup Hardhat Environment
 
 Create a `hardhat.config.ts` file with the following content:
 
@@ -169,7 +169,7 @@
 npx hardhat keystore set PRIVATE_KEY
 ```
 
 #### Import Precompile Components
 
 <Tabs>
 <Tab title="JavaScript">
@@ -263,7 +263,7 @@
 </Tab>
 </Tabs>
 
 ### Native SEI vs Custom Tokens
 
 **Native SEI Transfers:**
 
@@ -277,9 +277,9 @@
 - Requires prior token approval or ownership
 - Support various decimal configurations
 
 ## Step-by-Step Guide: Using the Bank Precompile
 
 ### Send Native SEI Tokens
 
 <Tabs>
 <Tab title="JavaScript">
@@ -300,7 +300,7 @@
   });
 
   const receipt = await tx.wait();
-  console.log('Native SEI transfer successful:', receipt.transactionHash);
+  console.log('Native SEI transfer successful:', receipt.hash);
   console.log(`Sent ${amountInSei} SEI to ${recipientAddress}`);
 } catch (error) {
   console.error('Native SEI transfer failed:', error);
@@ -330,7 +330,7 @@
 </Tab>
 </Tabs>
 
 ### Send Custom Tokens
 
 <Tabs>
 <Tab title="JavaScript">
@@ -357,7 +357,7 @@
 );
 
 const receipt = await tx.wait();
-console.log('Custom token transfer successful:', receipt.transactionHash);
+console.log('Custom token transfer successful:', receipt.hash);
 console.log(`Sent ${amount} ${tokenDenom} from ${fromAddress} to ${toAddress}`);
 ```
 
@@ -407,7 +407,7 @@
 </Tab>
 </Tabs>
 
 ### Query Account Balance
 
 <Tabs>
 <Tab title="JavaScript">
@@ -464,7 +464,7 @@
 </Tab>
 </Tabs>
 
 ### Query All Balances
 
 <Tabs>
 <Tab title="JavaScript">
@@ -539,7 +539,7 @@
 </Tab>
 </Tabs>
 
 ### Query Token Metadata
 
 <Tabs>
 <Tab title="JavaScript">
@@ -622,7 +622,7 @@
 </Tab>
 </Tabs>
 
 ### Complete Integration Example
 
 <Tabs>
 <Tab title="JavaScript">
@@ -643,16 +643,16 @@
   // Send native SEI tokens
   async sendSei(recipientAddress: string, amountInSei: string) {
     try {
-      const amountInUsei = ethers.parseUnits(amountInSei, 18);
+      const amountInWei = ethers.parseUnits(amountInSei, 18);
       const tx = await this.bank.sendNative(recipientAddress, {
-        value: amountInUsei,
+        value: amountInWei,
         gasLimit: 100000
       });
 
       const receipt = await tx.wait();
       return {
         success: true,
-        transactionHash: receipt.transactionHash,
+        transactionHash: receipt.hash,
         amount: amountInSei,
         recipient: recipientAddress
       };
@@ -715,7 +715,7 @@
       const receipt = await tx.wait();
       return {
         success: true,
-        transactionHash: receipt.transactionHash,
+        transactionHash: receipt.hash,
         from: fromAddress,
         to: toAddress,
         denom,
@@ -1103,15 +1103,15 @@
 </Tab>
 </Tabs>
 
 ## Security Considerations & Risks
 
 ### Transaction Security
 
 - **Amount Validation:** Always validate transfer amounts and ensure sufficient balances
 - **Address Verification:** Verify recipient addresses are valid before sending tokens
 - **Reentrancy Protection:** Be aware of potential reentrancy when combining with other contracts
 
 ### Permission Management
 
 ```solidity
 // Example of secure permission patterns
@@ -1129,9 +1129,9 @@
 
 ## Troubleshooting
 
 ### Common Issues and Solutions
 
 #### Transaction Failures
 
 ```typescript
 // Handle common transfer errors
@@ -1149,7 +1149,7 @@
 }
 ```
 
 #### Balance Query Issues
 
 ```typescript
 // Safe balance checking with error handling
@@ -1166,7 +1166,7 @@
 }
 ```
 
 ### Error Code Reference
 
 | Error | Cause | Solution |
 | --- | --- | --- |
@@ -1177,7 +1177,7 @@
 | `metadata not found` | Token metadata not available | Handle missing metadata gracefully |
 
 
 ## Important Notes
 
 <Info>
 
@@ -1189,13 +1189,13 @@
 
 </Info>
 
 ### Gas Optimization
 
 - **Batch Operations:** Use batch functions for multiple operations to save gas
 - **Query Efficiency:** Cache frequently accessed token metadata
 - **Error Handling:** Implement proper error handling to avoid failed transaction costs
 
 ### Integration Best Practices
 
 - **Balance Checks:** Always verify sufficient balance before transfers
 - **Error Recovery:** Implement retry logic for failed transactions

evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx

@@ -20,7 +20,7 @@
 
 <Info> **What is a precompile?** A precompile is a special smart contract deployed at a fixed address by the Sei protocol itself, that exposes custom native chain logic to EVM-based applications. It acts like a regular contract from the EVM's perspective, but executes privileged, low-level logic efficiently. </Info>
 
 ## How Does the CosmWasm Precompile Work?
 
 The CosmWasm precompile at address `0x0000000000000000000000000000000000001002` exposes functions like `execute()`, `execute_batch()`, and `query()`.
 
@@ -28,7 +28,7 @@
 - **Native Execution:** Operations are executed at the Cosmos SDK level for maximum efficiency and security.
 - **Seamless Bridge:** No need for separate wallet integrations or complex cross-chain interactions.
 
 ## What You'll Learn in This Guide
 
 By the end of this guide, you'll be able to:
 
@@ -41,7 +41,7 @@
 
 The CosmWasm precompile exposes the following functions:
 
 ### Transaction Functions
 
 <Warning>The `instantiate()` function has been disabled by [Prop 115](https://www.mintscan.io/sei/proposals/115) and will revert. It is omitted from this reference. The ABI in `@sei-js/precompiles` may still expose it for backwards compatibility, but calling it on-chain will fail.</Warning>
 
@@ -71,7 +71,7 @@
 ) payable external returns (bytes[] memory responses);
 ```
 
 ### Query Functions
 
 ```solidity
 /// Queries a CosmWasm contract.
@@ -84,7 +84,7 @@
 ) external view returns (bytes memory response);
 ```
 
 ## Using the Precompile
 
 ### Setup
 
@@ -95,9 +95,9 @@
 - **Node.js** (v18 or higher)
 - **npm** or **yarn** package manager
 - **EVM-compatible wallet**
-- **SEI tokens** for gas fees and contract operations
+- **SEI tokens** for gas and contract operations
 
 #### Install Dependencies
 
 Install the required packages for interacting with Sei precompiles:
 
@@ -109,7 +109,7 @@
 npm install @sei-js/precompiles@2.1.2
 ```
 
 #### Import Precompile Components
 
 ```typescript
 // Import CosmWasm precompile address and ABI
@@ -134,11 +134,11 @@
 const cosmwasm = new ethers.Contract(WASM_PRECOMPILE_ADDRESS, WASM_PRECOMPILE_ABI, signer);
 ```
 
 ## Critical: Understanding Message Formats
 
 One of the most important concepts to understand when working with the Sei CosmWasm precompile:
 
 ### CosmWasm Message Structure
 
 The CosmWasm precompile requires **JSON-encoded messages** that conform to each contract's specific schema:
 
@@ -148,7 +148,7 @@
 | `query()` | req parameter (input) | JSON bytes | `ethers.toUtf8Bytes(jsonString)` |
 | **All functions** | response (output) | JSON bytes | `JSON.parse(ethers.toUtf8String(response))` |
 
 ### How Message Encoding Works
 
 **All CosmWasm functions require JSON-encoded byte arrays:**
 
@@ -160,7 +160,7 @@
 - Use `msg.value` for SEI amounts
 - Use `coins` parameter for other denominations (encoded as JSON bytes)
 
 ### Best Practice: Message Encoding Helpers
 
 When working with CosmWasm messages, use proper JSON encoding:
 
@@ -203,7 +203,7 @@
 });
 ```
 
 ## Message Format Helpers
 
 Use these helper functions to handle CosmWasm message formatting:
 
@@ -251,9 +251,9 @@
 const coins = CosmWasmHelper.createCoins([{ denom: 'uusdc', amount: '1000000' }]);
 ```
 
 ## Step-by-Step Guide: Using the CosmWasm Precompile
 
 ### Execute a CosmWasm Contract
 
 <Tabs>
 <Tab title="JavaScript">
@@ -311,7 +311,7 @@
 </Tab>
 </Tabs>
 
 ### Execute Batch Operations
 
 <Tabs>
 <Tab title="JavaScript">
@@ -382,7 +382,7 @@
 </Tab>
 </Tabs>
 
 ### Query a CosmWasm Contract
 
 <Tabs>
 <Tab title="JavaScript">
@@ -451,9 +451,9 @@
 
 <Warning> **Query Limitations:** CosmWasm queries are read-only operations and don't consume gas, but parsing JSON responses in Solidity is complex. Consider handling response parsing off-chain. </Warning>
 
 ## Advanced Usage Examples
 
 ### Cross-Runtime DeFi Integration
 
 ```typescript
 async function crossRuntimeDeFiOperation(cosmwasmDexContract: string, evmTokenContract: string, amount: string) {
@@ -492,7 +492,7 @@
 }
 ```
 
 ### Complete Integration Example
 
 <Tabs>
 <Tab title="JavaScript">
@@ -730,9 +730,9 @@
 
 ## Troubleshooting
 
 ### Common Issues and Solutions
 
 #### Message Encoding Issues
 
 ```typescript
 // Ensure proper JSON encoding for messages
@@ -750,7 +750,7 @@
 const incorrectMsg = ethers.toUtf8Bytes('invalid json');
 ```
 
 ### Error Code Reference
 
 | Error | Cause | Solution |
 | --- | --- | --- |
@@ -761,23 +761,23 @@
 | `unauthorized` | Insufficient permissions | Check admin/owner permissions |
 | `query parsing failed` | Invalid query message format | Match contract's query schema |
 
 ## Important Notes
 
 <Info> Remember the key rule: All CosmWasm messages must be properly JSON-encoded as bytes, and contract schemas vary by implementation! </Info>
 
 ### Message Format Requirements
 
 - **JSON Encoding:** All messages must be valid JSON encoded as UTF-8 bytes, invalid JSON will cause transaction failures
 - **Schema Compliance:** Messages must match the contract's expected format
 - **Type Safety:** Use proper data types as expected by the contract
 
 ### Contract Address Format
 
 - Use valid Sei contract addresses with `sei1...` prefix
 - These are Cosmos-format addresses, not EVM addresses
 - **Contract Existence:** Verify contracts exist before calling
 
 ### Cross-Runtime Considerations
 
 - **State Isolation:** CosmWasm and EVM contracts have separate state
 - **Gas Estimation:** CosmWasm operations may require different gas calculations
@@ -785,7 +785,7 @@
 - **Native Token Handling:** Use `msg.value` for SEI, `coins` for other denominations
 - **Batch Limitations:** Large batches may hit gas limits
 
 ### Best Practices
 
 - Always validate JSON messages before sending
 - Handle response parsing carefully, especially for complex data structures

evm/precompiles/governance.mdx

@@ -10,7 +10,7 @@
 
 <Info>**What is a precompile?** A precompile is a special smart contract deployed at a fixed address by the Sei protocol itself, that exposes custom native chain logic to EVM-based applications. It acts like a regular contract from the EVM's perspective, but executes privileged, low-level logic efficiently.</Info>
 
 ## How Does the Governance Precompile Work?
 
 The governance precompile at address `0x0000000000000000000000000000000000001006` exposes functions like `vote()`, `voteWeighted()`, `deposit()`, and `submitProposal()`.
 
@@ -18,17 +18,17 @@
 - **Native Execution:** Governance operations are executed at the chain level for maximum efficiency.
 - **Seamless:** No need for separate wallet integrations.
 
 ## Use Cases
 
 - **Voting Interfaces:** Create user-friendly governance participation tools.
 - **Automated Governance:** Smart contracts that vote based on predetermined strategies.
 - **Governance Aggregators:** Build platforms that aggregate and simplify governance participation.
 
 ## Sei Governance Overview
 
 Sei governance operates on a structured timeline with specific parameters:
 
 ### Governance Process
 
 1. **Proposal Submission:** Submit proposal with minimum 3,500 SEI deposit
 2. **Deposit Period:** 2 days to accumulate minimum deposit or reach expedited threshold
@@ -53,7 +53,7 @@
 
 The governance precompile exposes the following functions:
 
 ### Transaction Functions
 
 ```solidity
 /// Cast a vote on the specified proposal.
@@ -101,7 +101,7 @@
 ) payable external returns (uint64 proposalID);
 ```
 
 ## Using the Contract
 
 ### Setup
 
@@ -112,9 +112,9 @@
 - **Node.js** (v18 or higher)
 - **npm** or **yarn** package manager
 - **MetaMask** or compatible EVM wallet configured for Sei Mainnet
-- **SEI tokens** for gas fees and governance deposits (minimum 3,500 SEI for proposals)
+- **SEI tokens** for gas and governance deposits (minimum 3,500 SEI for proposals)
 
 #### Install Dependencies
 
 Install the required packages for interacting with Sei precompiles:
 
@@ -129,7 +129,7 @@
 npm install dotenv
 ```
 
 #### Import Precompile Components
 
 ```typescript
 // Import Governance precompile address and ABI
@@ -140,7 +140,7 @@
 
 <Info>**Precompile Address:** The governance precompile is deployed at `0x0000000000000000000000000000000000001006`</Info>
 
 #### Get SEI Tokens
 
 Purchase SEI tokens from supported exchanges:
 
@@ -148,7 +148,7 @@
 - **Decentralized Exchanges:** Astroport, Dragonswap (on Sei)
 - **Bridge Options:** Various cross-chain bridges support SEI
 
-<Warning>**Minimum Requirements:** You need at least 3,500 SEI to submit a governance proposal, plus additional tokens for gas fees and potential additional deposits.</Warning>
+<Warning>**Minimum Requirements:** You need at least 3,500 SEI to submit a governance proposal, plus additional tokens for gas and potential additional deposits.</Warning>
 
 ### Contract Initialization
 
@@ -168,7 +168,7 @@
 const governance = new ethers.Contract(GOVERNANCE_PRECOMPILE_ADDRESS, GOVERNANCE_PRECOMPILE_ABI, signer);
 ```
 
 ## Vote Options
 
 The governance system uses the following vote options:
 
@@ -180,7 +180,7 @@
 | NoWithVeto | 4 | Vote against with veto | Opposes Proposal & burns deposit if > 33.4% |
 
 
 ### Voting Power
 
 Your voting power is determined by:
 
@@ -190,7 +190,7 @@
 
 <Info>**Important:** Only staked SEI provides voting power. You must delegate your tokens to validators to participate in governance voting.</Info>
 
 ## Validation Functions
 
 Before making governance transactions, use these helper functions to validate inputs:
 
@@ -246,9 +246,9 @@
 }
 ```
 
 ## Step-by-Step Guide: Using the Governance Precompile
 
 ### Submit a Proposal
 
 <Info>
 **Important Deposit Requirements:**
@@ -383,7 +383,7 @@
 await submitGovernanceProposal(proposalTitle, proposalDescription, depositAmount, false);
 ```
 
 ### Vote on a Proposal
 
 ```typescript
 // Simple voting with comprehensive validation
@@ -448,7 +448,7 @@
 await voteOnProposal(proposalID, 4);
 ```
 
 ### Weighted Voting
 
 <Danger>**Critical Requirement:** Weighted vote options MUST sum to exactly 1.0 or the transaction will fail. The Sei governance module enforces this strictly - even small rounding errors will cause rejection.</Danger>
 
@@ -562,7 +562,7 @@
 // await castWeightedVote(proposalID, badVote); // Don't run this!
 ```
 
 ### Deposit to a Proposal
 
 ```typescript
 // Add deposit to help proposal reach minimum threshold
@@ -617,7 +617,7 @@
 await addDepositToProposal(proposalID, additionalDeposit);
 ```
 
 ## Complete Integration Example
 
 Create a comprehensive governance interaction script:
 
@@ -872,7 +872,7 @@
 main().catch(console.error);
 ```
 
 ### Running the Example
 
 1. **Create a new directory and initialize npm:**
 
@@ -900,7 +900,7 @@
 5. **Ensure you have sufficient SEI:**
 
    - Minimum 3,500 SEI for proposal deposit
-   - Additional SEI for gas fees and optional additional deposits
+   - Additional SEI for gas and optional additional deposits
    - Staked SEI for voting power
 
 6. **Run the script:**
@@ -909,7 +909,7 @@
 node governance-mainnet-demo.js
 ```
 
 ### Expected Output
 
 ```
 🌐 Connecting to Sei Mainnet...
@@ -960,9 +960,9 @@
 
 ## Troubleshooting
 
 ### Common Issues and Solutions
 
 #### Insufficient Deposit
 
 ```typescript
 // Check minimum deposit requirement based on proposal type
@@ -981,7 +981,7 @@
 }
 ```
 
 #### No Voting Power
 
 ```typescript
 // Check if user has staked SEI for voting power
@@ -998,7 +998,7 @@
 }
 ```
 
 #### Invalid Vote Option
 
 ```typescript
 // Validate vote option with descriptive error
@@ -1020,7 +1020,7 @@
 }
 ```
 
 #### Weighted Vote Validation
 
 ```typescript
 // Comprehensive weighted vote validation with helpful errors
@@ -1082,7 +1082,7 @@
 }
 ```
 
 ### Error Code Reference
 
 | Error | Cause | Solution |
 | --- | --- | --- |

evm/precompiles/json.mdx

@@ -10,7 +10,7 @@
 
 <Info>**What is a precompile?** A precompile is a special smart contract deployed at a fixed address by the Sei protocol itself, that exposes custom native chain logic to EVM-based applications. It acts like a regular contract from the EVM's perspective, but executes privileged, low-level logic efficiently.</Info>
 
 ## How Does the JSON Precompile Work?
 
 The JSON precompile at address `0x0000000000000000000000000000000000001003` exposes functions like `extractAsBytes()`, `extractAsBytesList()`, and `extractAsUint256()`.
 
@@ -18,7 +18,7 @@
 - **Native Execution:** JSON parsing is executed at the native level for maximum efficiency.
 - **Seamless Bridge:** No need for complex workarounds or external libraries for JSON handling.
 
 ## Use Cases
 
 - **Oracle Integration:** Parse complex oracle responses containing multiple data points.
 - **DeFi Applications:** Process structured price feeds and market data.
@@ -30,7 +30,7 @@
 
 The JSON precompile exposes the following functions:
 
 ### Query Functions
 
 ```solidity
 /// Extracts data as bytes from the input using the specified key.
@@ -61,7 +61,7 @@
 ) external view returns (uint256 response);
 ```
 
 ## Using the Precompile
 
 ### Setup
 
@@ -72,9 +72,9 @@
 - **Node.js** (v18 or higher)
 - **npm** or **yarn** package manager
 - **MetaMask** or compatible EVM wallet configured for Sei Mainnet
-- **SEI tokens** for gas fees
+- **SEI tokens** for gas
 
 #### Install Dependencies
 
 Install the required packages for interacting with Sei precompiles:
 
@@ -89,7 +89,7 @@
 npm install dotenv
 ```
 
 #### Import Precompile Components
 
 ```typescript
 // Import JSON precompile address and ABI
@@ -118,11 +118,11 @@
 const jsonPrecompile = new ethers.Contract(JSON_PRECOMPILE_ADDRESS, JSON_PRECOMPILE_ABI, signer);
 ```
 
 ## Data Type Handling
 
 The JSON precompile has specific limitations for different data types:
 
 ### Supported Data Types
 
 | Function | Supports | Limitations |
 | --- | --- | --- |
@@ -131,7 +131,7 @@
 | extractAsBytesList | Arrays of strings/objects | Each element returned as bytes |
 
 
 ### Data Type Conversion Strategies
 
 ```typescript
 // For decimal numbers - store as integers with known precision
@@ -151,7 +151,7 @@
 const userObject = JSON.parse(userString);
 ```
 
 ## Error Handling Utilities
 
 Create comprehensive error handling for all extraction functions:
 
@@ -193,9 +193,9 @@
 }
 ```
 
 ## Step-by-Step Guide: Using the JSON Precompile
 
 ### Extract String Data
 
 ```typescript
 // JSON data with string values
@@ -216,7 +216,7 @@
 }
 ```
 
 ### Extract Numeric Data
 
 ```typescript
 // JSON data with numbers (integers only)
@@ -234,7 +234,7 @@
 console.log('Rate:', actualRate);
 ```
 
 ### Extract Array Data
 
 ```typescript
 // JSON data with array
@@ -253,7 +253,7 @@
 console.log('Mixed values:', valuesArray); // Output: [42, "test", 100]
 ```
 
 ### Extract Nested Data
 
 <Warning>**Important:** The JSON precompile does not support dot notation for nested objects. Instead, extract the parent object and parse it manually.</Warning>
 
@@ -286,7 +286,7 @@
 console.log('Wallet data:', walletData); // Output: { balance: 1000, currency: "SEI" }
 ```
 
 ## Complete Integration Example
 
 Create a comprehensive JSON parsing application for mainnet:
 
@@ -489,7 +489,7 @@
 main().catch(console.error);
 ```
 
 ### Running the Mainnet Example
 
 1. **Create a new directory and initialize npm:**
 
@@ -518,7 +518,7 @@
 
 5. **Ensure you have SEI tokens:**
 
-   - SEI for gas fees (small amounts needed for view functions)
+   - SEI for gas (small amounts needed for view functions)
 
 6. **Run the script:**
 
@@ -526,7 +526,7 @@
 node json-precompile-mainnet.js
 ```
 
 ### Expected Output
 
 ```
 🌐 Connecting to Sei Mainnet...
@@ -602,9 +602,9 @@
 🎉 === JSON Precompile Demo Completed Successfully! ===
 ```
 
 ## Advanced Usage Examples
 
 ### Oracle Price Feed Integration
 
 ```typescript
 // Advanced oracle integration with comprehensive error handling
@@ -656,9 +656,9 @@
 
 ## Troubleshooting
 
 ### Common Issues and Solutions
 
 #### Key Not Found
 
 ```typescript
 // Comprehensive error handling for missing keys
@@ -680,7 +680,7 @@
 }
 ```
 
 ### Error Code Reference
 
 | Error | Cause | Solution |
 | --- | --- | --- |
@@ -691,7 +691,7 @@
 | `out of gas` | Insufficient gas for large JSON | Use `calculateGasLimit()` for dynamic estimation |
 
 
 ## Key Considerations and Tricks
 
 <Info>
 

evm/precompiles/staking.mdx

@@ -12,7 +12,7 @@
 
 <Info> **What is a precompile?** A precompile is a special smart contract deployed at a fixed address by the Sei protocol itself, that exposes custom native chain logic to EVM-based applications. It acts like a regular contract from the EVM's perspective, but executes privileged, low-level logic efficiently. </Info>
 
 ## How Does the Staking Precompile Work?
 
 The staking precompile at address `0x0000000000000000000000000000000000001005` exposes a comprehensive set of staking functions including `delegate()`, `undelegate()`, `redelegate()`, `createValidator()`, `editValidator()`, and various query functions like `validators()`, `delegatorDelegations()`, `pool()`, and `params()`.
 
@@ -21,14 +21,14 @@
 - **Seamless Bridge:** No need for separate wallet integrations or complex cross-chain interactions.
 - **Event Emission:** All staking operations emit events (`Delegate`, `Undelegate`, `Redelegate`, `ValidatorCreated`, `ValidatorEdited`) for easy tracking and indexing.
 
 ## Use Cases
 
 - **DeFi Integration:** Build liquid staking protocols and yield farming strategies.
 - **Delegation Services:** Create user-friendly interfaces for staking operations.
 - **Portfolio Management:** Automate staking strategies and delegation rebalancing.
 - **Validator Management:** Create and manage validators programmatically.
 
 ## What You'll Learn in This Guide
 
 By the end of this guide, you'll be able to:
 
@@ -104,7 +104,7 @@
 );
 ```
 
 ### Listening for Events
 
 You can listen for these events in your dApp to track staking operations:
 
@@ -139,7 +139,7 @@
 
 The staking precompile exposes the following functions:
 
 ### Transaction Functions
 
 ```solidity
 /// Delegates Sei to the specified validator.
@@ -205,7 +205,7 @@
 ) external returns (bool success);
 ```
 
 ### Query Functions
 
 ```solidity
 struct Delegation {
@@ -446,7 +446,7 @@
 
 </Warning>
 
 ## Using the Precompile
 
 ### Setup
 
@@ -457,9 +457,9 @@
 - **Node.js** (v18 or higher)
 - **npm** or **yarn** package manager
 - **EVM-compatible wallet**
-- **SEI tokens** for gas fees and staking operations
+- **SEI tokens** for gas and staking operations
 
 #### Install Dependencies
 
 Install the required packages for interacting with Sei precompiles:
 
@@ -471,7 +471,7 @@
 npm install @sei-js/precompiles@2.1.2
 ```
 
 #### Import Precompile Components
 
 ```typescript
 // Import Staking precompile address and ABI
@@ -496,11 +496,11 @@
 const staking = new ethers.Contract(STAKING_PRECOMPILE_ADDRESS, STAKING_PRECOMPILE_ABI, signer);
 ```
 
 ## Critical: Understanding Decimal Precision
 
 One of the most important concepts to understand when working with the Sei staking precompile:
 
 ### Mixed Decimal Precision System
 
 The staking precompile operates with **different decimal precision for different operations** due to bridging EVM and Cosmos standards:
 
@@ -530,7 +530,7 @@
 
 </Warning>
 
 ### How This Works in Practice
 
 **delegate() Function (Uses 18 decimals):**
 
@@ -546,13 +546,13 @@
 - `delegation()` - returns `balance.amount` in 6-decimal `uSEI` and `delegation.shares` in 18-decimal precision
 - Rewards are handled by the **Distribution precompile**: `rewards()` query returns 18-decimal `DecCoins`, while withdrawn amounts (events) are 6-decimal `uSEI`
 
 ### Why This Mixed System Exists
 
 1. **delegate() EVM Compatibility:** Uses standard 18-decimal wei format for EVM `msg.value` consistency
 2. **Other Operations Cosmos Integration:** `undelegate()` and `redelegate()` use 6-decimal uSEI precision to match native Cosmos operations
 3. **Staking Query Consistency:** Staking precompile query balances use 6-decimal `uSEI` (while `shares` is 18-decimal) for consistent reading
 
 ### Best Practice: Different Conversion for Different Functions
 
 When working with user inputs, use the appropriate conversion for each function:
 
@@ -579,7 +579,7 @@
 const undelegateAmount = prepareAmountForUndelegateRedelegate(userInputAmount); // 6 decimals
 ```
 
 ### Normalization Guidelines (Clients and Indexers)
 
 - **Normalize to a single unit** for analytics and reconciliation:
   - Display: convert to `SEI` (`wei / 1e18`, `uSEI / 1e6`)
@@ -604,7 +604,7 @@
 }
 ```
 
 ## Decimal Conversion Helpers
 
 Use these helper functions to avoid precision errors:
 
@@ -638,9 +638,9 @@
 const redelegateAmount = SeiAmountConverter.seiToUsei(2); // For redelegate() - 6 decimals
 ```
 
 ## Step-by-Step Guide: Using the Staking Precompile
 
 ### Delegate Tokens
 
 <Tabs>
 <Tab title="JavaScript">
@@ -817,7 +817,7 @@
 
 </Tabs>
 
 ### Create a Validator
 
 <Warning> Creating a validator requires significant SEI for self-delegation and proper validator infrastructure setup. Only proceed if you understand the responsibilities of running a validator node. </Warning>
 
@@ -876,7 +876,7 @@
 </Tab>
 </Tabs>
 
 ### Edit a Validator
 
 ```typescript
 // Update validator parameters
@@ -892,7 +892,7 @@
 
 <Info>**Edit Validator Constraints:** - Commission can only be changed once every 24 hours - `minSelfDelegation` can only be increased, never decreased - Pass empty string `""` for `commissionRate` to keep current rate - Pass `0` for `minSelfDelegation` to keep current value</Info>
 
 ### Query Validators
 
 ```typescript
 // Get all bonded validators
@@ -910,7 +910,7 @@
 }
 ```
 
 ### Query a Specific Validator
 
 ```typescript
 const validatorAddress = 'seivaloper1xyz...';
@@ -925,7 +925,7 @@
 });
 ```
 
 ### Query All Delegations for an Address
 
 ```typescript
 const delegator = await signer.getAddress();
@@ -940,7 +940,7 @@
 }
 ```
 
 ### Query Unbonding Delegations
 
 ```typescript
 const delegator = await signer.getAddress();
@@ -962,7 +962,7 @@
 const specificUnbonding = await staking.unbondingDelegation(delegator, validatorAddress);
 ```
 
 ### Query Redelegations
 
 ```typescript
 // Get all redelegations for a specific delegator
@@ -986,7 +986,7 @@
 }
 ```
 
 ### Query Staking Pool and Parameters
 
 ```typescript
 // Get staking pool totals
@@ -1006,7 +1006,7 @@
 });
 ```
 
 ### Query Historical Validator Info
 
 ```typescript
 // Get validator set at a specific block height
@@ -1019,9 +1019,9 @@
 }
 ```
 
 ## Advanced Usage Examples
 
 ### Portfolio Rebalancing
 
 ```typescript
 async function rebalanceStaking(
@@ -1046,7 +1046,7 @@
 }
 ```
 
 ### Complete Integration Example
 
 <Tabs>
 <Tab title="JavaScript">
@@ -1356,20 +1356,20 @@
 </Tab>
 </Tabs>
 
 ## Security Considerations & Risks
 
 ### Unbonding Period
 
 - **21-day lock:** Undelegated tokens cannot be transferred or earn rewards for 21 days
 - **No exceptions:** This cannot be canceled once initiated
 - **Planning:** Consider this when managing liquidity needs
 
 ### Validator Selection Criteria
 
 - **Commission Rate:** Lower commission means more rewards for you (typically 1-10%)
 - **Uptime:** Check for validators with high uptime (99%+)
 
 ### Redelegation Complexity
 
 - **7-transaction limit:** You can only redelegate from the same validator to the same destination validator 7 times in 21 days
 - **Serial blocking:** After redelegating A→B, you cannot redelegate B→C for 21 days
@@ -1377,9 +1377,9 @@
 
 ## Troubleshooting
 
 ### Common Issues and Solutions
 
 #### Gas-Related Issues
 
 ```typescript
 // Set appropriate gas limits for different operations
@@ -1389,7 +1389,7 @@
 });
 ```
 
 ### Error Code Reference
 
 | Error | Cause | Solution |
 | --- | --- | --- |
@@ -1402,7 +1402,7 @@
 | `too many redelegations` | Exceeded 7 redelegation limit | Wait for earliest redelegation to expire |
 
 
 ## FAQ: Precision and Normalization
 
 - **What are the base units and precision standards defined for SEI across operations?**
   - `delegate()`: accepts `msg.value` in wei (18 decimals), but is internally truncated to 6-decimal `uSEI`. Effective granularity is 1 uSEI = `1e12` wei.
@@ -1415,11 +1415,11 @@
 - **Why multiple decimal precisions on one chain?**
   - To bridge EVM conventions (18-decimal `msg.value`) with the Cosmos staking module’s native 6-decimal accounting while keeping queries and non-`delegate()` writes consistent at 6 decimals.
 
 ## Important Notes
 
 <Info> Remember the key rule: delegate() uses 18 decimals, undelegate()/redelegate() use 6 decimals, delegation() returns 6 decimals! </Info>
 
 ### Decimal Precision
 
 - **delegate()** uses 18 decimals (wei) for msg.value
 - **undelegate() and redelegate()** use 6 decimals (uSEI) for amount parameters
@@ -1428,17 +1428,17 @@
 - **Rewards/claims (Distribution precompile):** `rewards()` query returns 18-decimal `DecCoins`; withdrawn amounts (events) are 6-decimal `uSEI`
 - **Granularity:** `delegate()` `msg.value` must be a multiple of `1e12` wei (last 12 digits zero) because the precompile truncates to 6 decimals internally
 
 ### Validator Addresses
 
 - Use valid Sei validator addresses with `seivaloper1...` prefix
 - These are Cosmos-format addresses, not EVM addresses
 
 ### Staking Risks
 
 - **Unbonding:** 21-day waiting period for undelegated tokens
 - **Redelegation limits:** Complex rules around frequency and serial operations
 
 ### Commission and Rewards
 
 - Validators keep a commission percentage
 - Rewards are distributed proportionally to delegation amounts

evm/sei-global-wallet.mdx

@@ -8,13 +8,13 @@
 
 Sei Global Wallet is a cross-application embedded crypto wallet powered by [Dynamic Global Wallets](https://www.dynamic.xyz/docs/react/global-wallets/overview). It gives users a persistent wallet experience across any integrated app within the Sei ecosystem, allowing them to authenticate and interact using familiar login methods like Google, Twitter, or Telegram—no browser extension or prior crypto knowledge required.
 
-<Info>Additional auth methods such as existing wallet apps (Metamask, ..) are possible through Dynamic, but are not currently enabled</Info>
+<Info>Additional auth methods such as existing wallet apps (MetaMask, ..) are possible through Dynamic, but are not currently enabled</Info>
 
 ## What is Sei Global Wallet?
 
 Unlike traditional browser extension wallets, Sei Global Wallet is built directly into web applications and allows users to authenticate using familiar methods like Google, Twitter, Telegram, or email—no downloads or crypto knowledge required.
 
 ## Why Use Sei Global Wallet?
 
 **For Users:**
 
@@ -29,7 +29,7 @@
 - **Zero Configuration:** Pre-configured and ready to use
 - **Universal Compatibility:** Works with RainbowKit, ConnectKit, Web3-React, and more
 
 ## How to Create a Sei Global Wallet Account
 
 1. Visit [dashboard.sei.io](https://dashboard.sei.io) or any Sei ecosystem application
 2. Click "Connect Wallet" and select "Sei Global Wallet"
@@ -37,7 +37,7 @@
 4. Complete the authentication flow
 5. Your wallet is automatically created and ready to use across all integrated Sei apps
 
 ## How to Integrate Sei Global Wallet
 
 ### Prerequisites
 
@@ -65,11 +65,11 @@
 import '@sei-js/sei-global-wallet/eip6963';
 ```
 
-<Warning>**Important:** Simply importing the package registers the wallet for discovery, but you'll need to ensure your application's provider stack is properly configured to interact with it. Most wallet connection libraries that support EIP-6963 will automatically detect the wallet after import.</Warning>
+<Warning>**Important:** Importing the package registers the wallet for discovery, but you'll need to ensure your application's provider stack is properly configured to interact with it. Most wallet connection libraries that support EIP-6963 will automatically detect the wallet after import.</Warning>
 
 ---
 
 ## Integration Examples
 
 Below are integration examples for different frameworks and wallet provider libraries to properly integrate the pre-configured Sei Global Wallet package.
 
@@ -1004,7 +1004,7 @@
 
 </Accordion>
 
 ## Troubleshooting & FAQ
 
 <Tabs>
 
@@ -1046,7 +1046,7 @@
 chainId: '0x530'; // for Sei Testnet (1328)
 ```
 
 ### Debugging Commands
 
 ```javascript
 // Check if EIP-6963 events are firing
@@ -1061,7 +1061,7 @@
 window.dispatchEvent(new Event('eip6963:requestProvider'));
 ```
 
 ### Testing Tips
 
 1. **Test with multiple browsers** to ensure cross-browser compatibility
 2. **Clear browser cache** if wallets aren't appearing
@@ -1069,7 +1069,7 @@
 4. **Test both testnet and mainnet** connections
 5. **Verify social login methods** work across different auth providers
 
 ### Security Considerations
 
 - Sei Global Wallet is **self-custodial** - users control their private keys
 - All communications between app and wallet are **encrypted**
@@ -1085,7 +1085,7 @@
 
 Sei Global Wallet is an embedded wallet experience for the Sei network, enabling wallet creation and authentication through social logins. Unlike traditional embedded wallets, Sei Global Wallet offer greater flexibility by allowing users to carry their wallets across different apps within the Sei ecosystem.
 
 #### Q: What are the key benefits of Sei Global Wallet for developers and users?
 
 **For Developers:**
 
@@ -1112,19 +1112,19 @@
 - **Trusted Execution Environments (TEEs):** Operations occur within secure environments
 - **Verified origins:** Only verified origins can interact with Sei Global Wallet
 
 #### Q: Is Sei Global Wallet self-custodial or custodial?
 
 Sei Global Wallet is self-custodial, giving full control to end-users. Users can export their keys at any time and import them into other wallets, such as MetaMask.
 
 #### Q: Do Sei Global Wallet require browser extensions?
 
 No, they operate as embedded wallets that work directly in the browser without requiring extensions.
 
 #### Q: Can I link my existing external wallet to my Sei Global Wallet?
 
 Not currently. In the future, you will be able to link external wallets to a Sei global account.
 
 #### Q: What extra protections can I add to my Sei Global Wallet?
 
 While Global Wallets are non-custodial, good security practices include:
 
@@ -1133,7 +1133,7 @@
 - **Always have backup methods** - link additional email or social login methods
 - **Never store authentication keys digitally** - keep private keys secure offline
 
 #### Q: Have Sei Global Wallet been audited?
 
 Yes, the Dynamic Global Wallets product has been audited by Cure53.
 
@@ -1149,7 +1149,7 @@
 </Tab>
 </Tabs>
 
 ## References and Links
 
 - [Dynamic Global Wallet Documentation](https://www.dynamic.xyz/docs/react/global-wallets/overview)
 - [EIP-6963 Standard](https://eips.ethereum.org/EIPS/eip-6963)

evm/sei-js/index.mdx

@@ -14,9 +14,9 @@
 
 - **Complete TypeScript support** — Full type safety for every function, contract interaction, and API response. Catch errors at compile time.
 - **Production ready** — Battle-tested components used by major applications in the Sei ecosystem.
-- **Optimized for Sei** — Take advantage of Sei's fast finality, low gas fees, and native features.
+- **Optimized for Sei** — Take advantage of Sei's fast finality, low gas, and native features.
 
 ## Package Ecosystem
 
 ### [@sei-js/precompiles](/evm/precompiles)
 
@@ -34,7 +34,7 @@
 npx @sei-js/create-sei app
 ```
 
 ### [@sei-js/sei-global-wallet](/evm/sei-global-wallet)
 
 Connect to any Sei-compatible wallet using the EIP-6963 standard. Provides a cross-application embedded wallet experience with social login.
 
@@ -42,7 +42,7 @@
 npm install @sei-js/sei-global-wallet
 ```
 
 ### [@sei-js/ledger](/evm/sei-js/ledger)
 
 Secure transaction signing with Ledger hardware wallets. Provides TypeScript helper functions for address derivation and offline Amino signing via the SEI Ledger app.
 
@@ -66,7 +66,7 @@
 npx @sei-js/mcp-server
 ```
 
 ## Quick Start
 
 Generate a new Sei application using the CLI tool:
 
@@ -122,7 +122,7 @@
   </Card>
 </CardGroup>
 
 ## Community & Support
 
 - [Discord](https://discord.gg/sei) — Join the Sei developer community
 - [GitHub Issues](https://github.com/sei-protocol/sei-js/issues) — Report bugs and request features

evm/transactions-with-seid.mdx

@@ -13,7 +13,7 @@
 
 If you don't already have keys configured, you'll need to either generate a new key or import an existing one into your local keyring. Refer to this guide on [how to create a key](/evm/installing-seid-cli) for more details.
 
 ## Network Configuration
 
 If the machine you run these commands from are not a node of the network, you'd need to append the following to your commands:
 
@@ -25,7 +25,7 @@
 
 <Info>Most commands support `--evm-rpc` flag to specify custom RPC endpoints. The default is `http://localhost:8545`.</Info>
 
 ## Common Transaction Flags
 
 All transaction commands support these common flags:
 
@@ -35,9 +35,9 @@
 - `--evm-rpc=<url>` - EVM RPC endpoint URL (default: `http://localhost:8545`)
 - `--nonce=<nonce>` - Nonce override for the transaction (-1 means auto-calculate)
 
 ## Address Management Commands
 
 ### Associate Address
 
 Associates the Sei address and EVM address on-chain for the sending key. This is required for cross-layer interactions.
 
@@ -61,9 +61,9 @@
 Response: {"jsonrpc":"2.0","result":null,"id":"associate_addr"}
 ```
 
 ## Token Transfer Commands
 
 ### Send Native Tokens
 
 Sends native tokens (usei) to the target EVM address.
 
@@ -93,7 +93,7 @@
 Transaction hash: 0x...
 ```
 
 ### Send ERC20 Tokens
 
 Sends ERC20 tokens from a specific contract to a recipient.
 
@@ -124,9 +124,9 @@
 Transaction hash: 0x...
 ```
 
 ## Contract Deployment Commands
 
 ### Deploy Contract
 
 Deploys an EVM contract from a binary file.
 
@@ -157,9 +157,9 @@
 Transaction hash: 0x...
 ```
 
 ## Contract Interaction Commands
 
 ### Call Contract
 
 Calls an EVM contract with a specific payload. You can generate payload by taking a look at docs [here](/evm/querying-the-evm#payload-generation).
 
@@ -190,7 +190,7 @@
 Transaction hash: 0x...
 ```
 
 ### Call Precompile
 
 Calls a method on a precompiled contract. Precompiles provide EVM access to Cosmos-SDK functionality.
 
@@ -233,9 +233,9 @@
 Transaction hash: 0x...
 ```
 
 ## Advanced Usage
 
 ### Custom Gas Settings
 
 You can customize gas settings for any transaction:
 
@@ -246,7 +246,7 @@
   --from=mykey
 ```
 
 ### Nonce Management
 
 Override automatic nonce calculation:
 
@@ -256,19 +256,19 @@
   --from=mykey
 ```
 
 ## Error Handling
 
 <Warning>
 **Common Issues:**
 
-- Insufficient balance for transaction + gas fees
+- Insufficient balance for transaction + gas
 - Incorrect address formats (use 0x prefix for EVM addresses)
 - Gas limit too low for complex operations
 - Nonce conflicts in rapid successive transactions
 
 </Warning>
 
 ## Best Practices
 
 1. **Gas Estimation**: Start with default gas limits and adjust based on transaction complexity
 2. **Address Validation**: Always verify addresses before sending transactions
@@ -276,10 +276,10 @@
 4. **Network Verification**: Confirm you're connected to the correct network
 5. **Transaction Monitoring**: Save transaction hashes for tracking purposes
 
 ## Transaction Requirements
 
 - **Key Configuration**: Local keyring must contain the signing key
-- **Sufficient Balance**: Account must have enough tokens for transaction amount + gas fees
+- **Sufficient Balance**: Account must have enough tokens for transaction amount + gas
 - **Address Formats**: Use proper formats (0x... for EVM, seivaloper... for validators)
 - **Network Access**: Ensure connectivity to the specified RPC endpoint
 - **Gas Limits**: Set appropriate gas limits for transaction complexity

evm/transactions.mdx

@@ -7,7 +7,7 @@
 
 Sei supports EVM transactions, allowing compatibility with Ethereum-based tools and contracts. Transactions are signed messages originating from an externally owned account (EOA) that trigger state changes on the blockchain.
 
 ## Transaction Lifecycle
 
 | Stage             | Description                                                                                                          |
 | ----------------- | -------------------------------------------------------------------------------------------------------------------- |
@@ -24,7 +24,7 @@
   Unlike other EVM chains where you need to wait for multiple confirmations, Sei's consensus mechanism provides immediate transaction finality. Once a transaction is included in a block, it cannot be reversed.
 </Info>
 
 ## Gas Mechanics
 
 Gas is a unit of computational work in the EVM that helps prevent spam and allocate resources efficiently:
 
@@ -44,7 +44,7 @@
   - Always estimate gas before sending transactions using `eth_estimateGas`
 </Warning>
 
 ## Transaction Structure
 
 EVM transactions in Sei follow the Ethereum transaction format with standard properties:
 
@@ -58,7 +58,7 @@
     | `nonce` | A sequentially incrementing counter that indicates the transaction number from the account. This prevents replay attacks and ensures transaction ordering. |
     | `data` | The input data (also called 'input' or 'calldata') for contract execution. For simple transfers, this is usually empty. For contract interactions, this contains the function selector and encoded arguments. |
     | `value` | Amount of SEI to transfer from sender to recipient (denominated in WEI, where 1 SEI equals 1e+18 WEI). |
-    | `gasLimit` | The maximum amount of gas units that can be consumed by the transaction. Often referred to simply as 'gas' in transaction objects. |
+    | `gasLimit` | The maximum amount of gas units that can be consumed by the transaction. Often referred to as 'gas' in transaction objects. |
     | `maxPriorityFeePerGas` | The maximum price of the consumed gas to be included as a tip to the validator (denominated in WEI). Used in EIP-1559 transactions. |
     | `maxFeePerGas` | The maximum fee per unit of gas willing to be paid for the transaction (inclusive of baseFeePerGas and maxPriorityFeePerGas). Used in EIP-1559 transactions. |
     | `gasPrice` | The price per unit of gas the sender is willing to pay (denominated in WEI). Used in legacy transactions. |
@@ -266,7 +266,7 @@
   </Tab>
 </Tabs>
 
 ## Transaction Guidelines
 
 <Info>
   **Transaction Best Practices:**
@@ -285,7 +285,7 @@
 | Out of Gas | Gas limit too low for the operation | Use `eth_estimateGas` to set appropriate limit |
 | Contract Execution Failed | Contract function reverted | Test with `eth_call` before sending transaction |
 
 ## Additional Resources
 
 <CardGroup cols={3}>
   <Card horizontal title="RPC Reference" icon="circle-info" href="/evm/reference">

evm/wallet-integrations/pimlico.mdx

@@ -6,7 +6,7 @@
 ---
 [Pimlico](https://pimlico.io) is an Account Abstraction infrastructure provider that enables developers to easily integrate smart accounts and gasless transactions into their Sei applications. This guide will walk you through creating a smart account and sending your first gasless transaction on Sei Testnet using Pimlico's infrastructure.
 
 ## Getting Started
 
 ### Dependencies
 
@@ -18,7 +18,7 @@
 
 <Info>permissionless.js is an AA SDK that works with any account, paymaster, or bundler implementation - no vendor lock-in.</Info>
 
 ### Setting up Pimlico Dashboard
 
 Before starting the integration:
 
@@ -30,7 +30,7 @@
 PIMLICO_API_KEY='pim_xxxxxxxxxxxxxxxxxxxxxx'
 ```
 
 ## Configuring Pimlico Client
 
 First, let's set up the necessary clients and configurations.
 
@@ -71,7 +71,7 @@
 });
 ```
 
 ## Creating a Smart Account
 
 Now let's create a simple smart account instance. This account will be controlled by a single EOA signer:
 
@@ -88,7 +88,7 @@
 
 <Info>For a full list of all supported smart account types in permissionless.js see [here](https://docs.pimlico.io/permissionless/how-to/accounts/comparison)</Info>
 
 ## Setting up the Smart Account Client
 
 To interact with the smart account, we need to create a SmartAccountClient:
 
@@ -108,7 +108,7 @@
 });
 ```
 
 ## Sending a Gasless Transaction
 
 With everything set up, we can now send a gasless transaction from our smart account:
 
@@ -123,7 +123,7 @@
 return txHash;
 ```
 
 ## Complete Example
 
 Here's a complete example that puts everything together:
 
@@ -199,7 +199,7 @@
 main().catch(console.error);
 ```
 
 ## What's Happening Under the Hood?
 
 When you send a transaction using the smart account client:
 
@@ -219,7 +219,7 @@
 - Create a smart account
 - Send gasless transactions
 
-This implementation enables a seamless user experience where end users don't need to worry about gas fees or managing native tokens to interact with your dApp.
+This implementation enables a seamless user experience where end users don't need to worry about gas or managing native tokens to interact with your dApp.
 
 For more information about Pimlico and its features, check out:
 

evm/wallet-integrations/thirdweb.mdx

@@ -8,7 +8,7 @@
 
 This guide provides a comprehensive, step-by-step tutorial for integrating thirdweb's Account Abstraction SDK on Sei. By the end of this guide, you will understand how to create seamless wallet connectivity with social logins and build decentralized applications with sponsored gas transactions.
 
 ## What This Guide Covers
 
 - Core concepts and benefits for user experience
 - Creating a React application with thirdweb SDK and Vite
@@ -26,11 +26,11 @@
 
 <Warning>**For Mainnet**: An active thirdweb Pay As You Go subscription ($5/month minimum) is required for gas sponsorship on mainnet.</Warning>
 
 ## What is Account Abstraction?
 
 Account Abstraction (AA) is a paradigm that transforms how users interact with blockchain applications. Instead of traditional externally-owned accounts (EOAs), users get smart contract wallets that enable advanced features.
 
 ### Core Concepts
 
 - **Smart Wallets**: Contract-based accounts with programmable logic
 - **Gas Sponsorship**: Dapps pay transaction fees on behalf of users
@@ -39,7 +39,7 @@
 
 ## Network Information
 
 ### SEI Mainnet Configuration
 
 - **Network Name**: SEI EVM
 - **Chain ID**: 1329
@@ -48,11 +48,11 @@
 - **Currency**: SEI
 - **thirdweb RPC**: `https://1329.rpc.thirdweb.com/{YOUR_CLIENT_ID}`
 
 ### Step 1: Deploy a Storage Contract
 
 Before integrating the SDK, deploy a simple Storage contract on SEI. This contract will store and retrieve a number.
 
 #### Storage Contract (Solidity)
 
 ```solidity title="Storage.sol"
 // SPDX-License-Identifier: MIT
@@ -73,9 +73,9 @@
 
 Deploy this contract using [Remix](https://remix.ethereum.org/) on Sei. Note down the contract address - you'll need it in the code.
 
 ### Step 2: Project Setup
 
 #### Create a New Project
 
 ```bash
 npm create vite@latest sei-thirdweb-app -- --template react-ts
@@ -83,13 +83,13 @@
 npm install
 ```
 
 #### Install Dependencies
 
 ```bash
 npm install thirdweb@^5
 ```
 
 #### Configure Environment Variables
 
 Create a `.env` file in your project root:
 
@@ -99,7 +99,7 @@
 
 Get your Client ID from [thirdweb Dashboard](https://thirdweb.com/dashboard) → Settings → API Keys.
 
 #### Enable Gas Sponsorship
 
 If you want to sponsor gas on mainnet:
 
@@ -107,7 +107,7 @@
 2. Subscribe to the **Pay As You Go** plan ($5/month)
 3. Without this, sponsored transactions will fail on mainnet
 
 ### Step 3: Configure thirdweb Client
 
 Create `src/client.ts`:
 
@@ -119,7 +119,7 @@
 });
 ```
 
 ### Step 4: Smart Contract Integration
 
 Replace `src/App.tsx`:
 
@@ -302,7 +302,7 @@
 export default App;
 ```
 
 #### Understanding Key Components
 
 | Component | Description |
 | --- | --- |
@@ -313,7 +313,7 @@
 | `inAppWallet` | Smart wallet with social login capabilities |
 
 
 ### Step 5: Package Configuration
 
 Ensure your `package.json` includes:
 
@@ -342,20 +342,20 @@
 }
 ```
 
 ### Step 6: Run the Application
 
 #### Start Development Server
 
 ```bash
 npm run dev
 ```
 
 #### Test the Application
 
 1. Open your browser and navigate to `http://localhost:5173`
 2. Click "Connect to Sei Network"
 3. Choose your preferred login method (Google, email, etc.)
-4. A smart wallet is automatically created for you (no gas fees!)
+4. A smart wallet is automatically created for you (no gas!)
 5. After connecting, you'll see three interaction buttons
 6. Try storing number 37 or a custom number
 7. Retrieve the stored value - all transactions are gasless!
@@ -363,11 +363,11 @@
 
 <Info>Gas fees are automatically sponsored when using Account Abstraction, so users don't need SEI tokens to interact with the contract.</Info>
 
 ### Step 7: Done!
 
 You've successfully integrated thirdweb's Account Abstraction SDK with Sei! Users can now connect with social logins and interact with your contracts without needing to hold SEI tokens for gas.
 
 ## What You've Accomplished
 
 - Created a React application with thirdweb SDK v5
 - Configured Account Abstraction for SEI network
@@ -378,7 +378,7 @@
 
 ## Troubleshooting
 
 ### Common Issues and Solutions
 
 | Error | Problem | Solution |
 | --- | --- | --- |
@@ -389,7 +389,7 @@
 | `Gas estimation failed` | Contract method issue | Verify contract ABI and function signature |
 
 
 ### Network Connection Issues
 
 <Danger>
 

learn/accounts.mdx

@@ -1,4 +1,4 @@
 ---
 title: 'Sei Network Accounts: Dual Address System Explained'
 sidebarTitle: 'Account Linking'
 description: "Understand how Sei's unified account system works with both EVM (0x) and Cosmos (sei1) addresses, including association methods, security considerations, and cross-environment interactions."
@@ -32,9 +32,9 @@
 
 Both addresses for a single account are derived from the same **public key**, but the chain can only determine their association **after the public key is known by the chain** via association.
 
 ## Key Points
 
 ### Before Linking
 
 - The Bech32 (`sei...`) and EVM (`0x...`) addresses are treated as **separate
   accounts**.
@@ -44,12 +44,12 @@
   linking.
 - Some types of transactions will **not be possible** (see table below).
 
 ### After Linking
 
 - Balances are reflected consistently across both addresses.
 - Applications can query either address format seamlessly.
 
 ## Wallet Association and Transfer Limitations
 
 Certain actions are **not possible** before wallets are associated:
 
@@ -58,7 +58,7 @@
 - Transfers of **ERC-based tokens** (e.g., ERC20/721/1155) from an EVM wallet to
   an **unassociated Cosmos address**.
 
 ## Methods of Association
 
 | Method | Security Risk | User Action Required |
 | --- | --- | --- |
@@ -74,7 +74,7 @@
 Constants for the `addr` precompile can also be found in the repo
 [Sei-Chain/precompiles](https://github.com/sei-protocol/sei-chain/tree/main/precompiles/addr):
 
 ## Method 1: Broadcast a Transaction
 
 - When an account **broadcasts a transaction** (e.g., sending tokens), its
   public key is recorded on-chain.
@@ -83,7 +83,7 @@
 - This ensures balances and transactions are accessible across both address
   formats.
 
 ## Method 2: Direct Private Key Association
 
 <Danger>**Security Risk**: **High** – Requires the private key to be directly available. Exposing the private key can compromise the wallet.</Danger>
 
@@ -93,7 +93,7 @@
 import { createPublicClient, createWalletClient, http } from 'viem';
 import { privateKeyToAccount } from 'viem/accounts';
 import { seiTestnet } from 'viem/chains';
-import { ADDRESS_PRECOMPILE_ABI, ADDRESS_PRECOMPILE_ADDRESS } from '@sei-js/evm';
+import { ADDRESS_PRECOMPILE_ABI, ADDRESS_PRECOMPILE_ADDRESS } from '@sei-js/precompiles';
 
 const PRIVATE_KEY = '<replace_with_private_key>';
 
@@ -116,7 +116,7 @@
 console.log(response);
 ```
 
 ## Method 3: Associate via Signed Message
 
 <Warning>**Security Risk**: **Medium** – Requires signing a specific message using the private key.</Warning>
 
@@ -127,7 +127,7 @@
 import { createWalletClient, http, parseSignature, toHex } from 'viem';
 import { privateKeyToAccount, generatePrivateKey } from 'viem/accounts';
 import { seiTestnet } from 'viem/chains';
-import { ADDRESS_PRECOMPILE_ABI, ADDRESS_PRECOMPILE_ADDRESS } from '@sei-js/evm';
+import { ADDRESS_PRECOMPILE_ABI, ADDRESS_PRECOMPILE_ADDRESS } from '@sei-js/precompiles';
 
 const client = createWalletClient({ chain: seiTestnet, transport: http() });
 
@@ -155,7 +155,7 @@
 associate();
 ```
 
 ## Method 4: Associate via Public Key
 
 <Info>**Security Risk**: **Low** – Involves using the public key, which is less sensitive than the private key.</Info>
 
@@ -166,7 +166,7 @@
 import { createWalletClient, http } from 'viem';
 import { privateKeyToAccount, generatePrivateKey } from 'viem/accounts';
 import { seiTestnet } from 'viem/chains';
-import { ADDRESS_PRECOMPILE_ABI, ADDRESS_PRECOMPILE_ADDRESS } from '@sei-js/evm';
+import { ADDRESS_PRECOMPILE_ABI, ADDRESS_PRECOMPILE_ADDRESS } from '@sei-js/precompiles';
 
 const client = createWalletClient({ chain: seiTestnet, transport: http() });
 
@@ -192,11 +192,11 @@
 associateViaPubkey();
 ```
 
 ## Query Linked Addresses
 
 Resolve either side of an existing association by calling the `addr` precompile at `0x0000000000000000000000000000000000001004` over a standard `eth_call`. The precompile is universally available on every Sei RPC.
 
 ### Fetch Bech32 Address for an EVM Address
 
 ```bash
 curl -X POST $SEIEVM -H "Content-Type: application/json" -d '{
@@ -238,7 +238,7 @@
 });
 ```
 
 ### Fetch EVM Address for a Sei Address
 
 ```ts
 const evmAddr = await client.readContract({
@@ -251,7 +251,7 @@
 
 The precompile reverts if the address has never been associated; surface this as "not linked" rather than re-throwing.
 
 ## Deriving Addresses from the Public Key
 
 Both address formats come from the same secp256k1 public key, but they use
 **different hashing schemes**: the bech32 (`sei1…`) side follows the standard
@@ -259,7 +259,7 @@
 the EVM (`0x…`) side follows the standard Ethereum derivation (`keccak256` of
 the **uncompressed** pubkey without its `0x04` prefix byte).
 
 ### Sei Address Derivation
 
 The Cosmos address is derived from the public key using the following steps:
 
@@ -284,7 +284,7 @@
 }
 ```
 
 ### EVM Address Derivation
 
 The EVM-compatible address is derived as follows:
 
@@ -313,7 +313,7 @@
 - **EVM Address**: `'0x' + keccak256(uncompressedPubKey[1:])[-20:]` — last 20 bytes of the keccak256 hash, Ethereum-standard derivation.
 - The two formats share an account because the chain stores the **public key** itself on association; either format can be derived from it deterministically.
 
 ### Why It Works
 
 Both formats are deterministic, public-key-derived address schemes. Once the
 public key is on-chain (via any of the four association methods above, or
@@ -328,14 +328,14 @@
 - Linking enables dApps and tools to access balances consistently across both
   address formats.
 
 ## HD Paths and Coin Types
 
 When deriving a private key from a mnemonic phrase, the hierarchical
 deterministic (HD) path involves multiple parameters, including the coin type.
 The coin type determines the blockchain ecosystem for which the key is derived,
 making it crucial when dealing with different wallets and blockchains.
 
 ### Coin Type Parameter
 
 The second parameter in the HD path specifies the coin type, which is defined by
 the BIP-44 standard. This parameter identifies the blockchain ecosystem
@@ -355,7 +355,7 @@
 different set of keys for each coin type, meaning the derived addresses will
 differ.
 
 ### Private Key Export
 
 Users can export their private key from MetaMask (derived using coin type 60)
 and import it into any Cosmos wallet. This works because the private key, once
@@ -363,12 +363,12 @@
 receiving wallet supports the import function. This allows users to manage their
 assets across various blockchains using the same underlying cryptographic key.
 
 ### Example HD Paths
 
 - **Traditional Cosmos Path**: `m/44'/118'/0'/0/0`
 - **Traditional EVM Path**: `m/44'/60'/0'/0/0`
 
 ## Generating Wallets
 
 ### Deriving bech32 and hex addresses from pubkey
 

learn/general-governance.mdx

@@ -7,22 +7,22 @@
 
 Sei employs an on-chain governance system that enables SEI holders to participate in the decision-making process for the network. This system is built on the Cosmos SDK governance module with several enhancements specific to Sei's architecture.
 
 ## How Governance Works
 
 1. **Proposal Submission** — Anyone can submit a governance proposal with an initial deposit.
 2. **Deposit Period** — Community members can contribute to the proposal deposit.
 3. **Voting Period** — Once minimum deposit is reached, voting begins.
 4. **Execution** — Approved proposals are automatically executed.
 
 ### Governance Logic
 
 - **Quorum Requirement** — A minimum percentage of bonded tokens must participate in voting for a proposal to be valid.
 - **Approval Threshold** — A proposal must receive more than 50% approval (excluding abstain votes) to pass, or 66.7% for expedited proposals.
 - **Veto Protection** — If more than 33.4% of votes are "NoWithVeto", the proposal is vetoed regardless of other vote counts.
 
 ## Network Parameters
 
 ### Production Network (Mainnet)
 
 Live network parameters for pacific-1
 
@@ -39,7 +39,7 @@
 | Expedited Threshold | 66.7% | Fast-track proposals |
 | Veto Threshold | 33.4% | Maximum veto votes allowed |
 
 ### Development Networks (Testnet)
 
 Changed testing parameters for atlantic-2
 
@@ -50,9 +50,9 @@
 | Voting Period | 12 hours | Fast testing cycles |
 | Expedited Voting Period | 6 hours | Fast testing cycles |
 
 ## Vote Types
 
 ### Voting Options
 
 Understand the different voting options available.
 
@@ -61,7 +61,7 @@
 3. **Abstain** — Neutral position. Counts toward quorum but not approval threshold.
 4. **NoWithVeto** — Strong opposition. Can veto a proposal if threshold is exceeded.
 
 ## Weighted Voting
 
 **Advanced Voting**
 
@@ -70,7 +70,7 @@
 - **Flexibility** — Distribute voting power across different options based on preference strength.
 - **Precision** — Express nuanced positions on complex proposals with percentage allocations.
 
 ## Proposal Outcomes
 
 | Outcome | Conditions |
 | --- | --- |
@@ -79,13 +79,13 @@
 | Failed (No Quorum) | Less than 33.4% of bonded tokens participated · Proposal automatically fails |
 | Vetoed | More than 33.4% of votes were "NoWithVeto" · Indicates strong community opposition |
 
 ## Best Practices
 
 ### Community Engagement
 
 Guidelines for effective governance participation.
 
-- **Research Thoroughly** — Read proposals completely and understand their implications before voting.
+- **Research Thoroughly** — Read proposals and understand their implications before voting.
 - **Engage in Discussion** — Participate in community forums and discussions to better understand different perspectives.
 - **Vote Responsibly** — Consider the long-term implications of proposals for the network and ecosystem.
 - **Stay Informed** — Follow governance updates and participate actively in the democratic process.

learn/general-staking.mdx

@@ -1,4 +1,4 @@
 ---
 title: 'Sei Blockchain Staking Guide'
 sidebarTitle: 'Staking'
 description: "Participate in Sei's proof-of-stake consensus by staking tokens with validators, with detailed explanations of delegation, rewards, slashing risks, and the unbonding process."
@@ -21,11 +21,11 @@
 own stake.
 
 The Sei protocol incentivizes validators and delegators with staking rewards
-from gas fees and genesis token unlocks. All rewards are distributed
+from gas and genesis token unlocks. All rewards are distributed
 to delegators proportional to their delegation, and the validator keeps a percentage of this as commission.
 Users can view a validator's commission rate on the Sei Dashboard, or by querying the validator information on-chain.
 
 ## How to Stake
 
 Staking on Sei can be done through the Sei Dashboard, via the `seid` CLI, or even
 through API calls.
@@ -34,7 +34,7 @@
 - **seid CLI**: `seid tx staking [command] [flags]`
 - **REST/RPC**: `GET/POST /staking/*`
 
 ## Key Concepts
 
 ### Delegation
 
@@ -71,7 +71,7 @@
 done through delegation. The tokens are locked and contribute to the validator's
 stake, starting to earn rewards immediately.
 
 ### Un-Bonding
 
 Delegators can un-bond or un-stake their Sei tokens, initiating a 21-day period
 during which the tokens do not earn rewards and cannot be transferred. After
@@ -93,7 +93,7 @@
 
 There is no slashing of funds in Sei.
 
 ## Common Questions
 
 ### How are staking rewards calculated?