docs(evm): fix broken viem import, migrate Hardhat guide to v3, add Python quickstart

docs.json

@@ -159,6 +159,7 @@
               "evm/evm-general",
               "evm/evm-hardhat",
               "evm/evm-foundry",
+              "evm/python-quickstart",
               "evm/evm-wizard",
               "evm/solidity-resources",
               {

evm/evm-parity/examples/deploy-verify.mdx

@@ -1,22 +1,22 @@
 ---
 title: 'Deploy and Verify'
 description: 'Deploying and verifying smart contracts on Sei with viem, ethers, Foundry, and Hardhat'
 ---
 
 # Deploy and Verify
 
 Sei is EVM-compatible — standard deployment tooling works without modification. This page covers deploying a contract and verifying its source on the Sei block explorer.
 
 For a deeper look at verification options (Remix, Sourcify UI, batch verification), see the [Verify Contracts](/evm/evm-verify-contracts) page.
 
 ## Deploying with viem or ethers
 
 <CodeGroup>
 
 ```ts viem
 import { createPublicClient, createWalletClient, http } from 'viem';
 import { privateKeyToAccount } from 'viem/accounts';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const account = privateKeyToAccount('0xYourPrivateKey');
 const publicClient = createPublicClient({ chain: sei, transport: http() });
@@ -49,7 +49,7 @@
 
 ## Deploying with Foundry
 
 Foundry works against Sei with the standard `--rpc-url` flag.
 
 ```bash
 forge create src/MyContract.sol:MyContract \
@@ -58,7 +58,7 @@
   --constructor-args arg1 arg2
 ```
 
 For testnet:
 
 ```bash
 forge create src/MyContract.sol:MyContract \
@@ -68,7 +68,7 @@
 
 ## Deploying with Hardhat
 
 Add Sei networks to your `hardhat.config.ts`:
 
 ```ts
 import { HardhatUserConfig } from 'hardhat/config';
@@ -99,7 +99,7 @@
 
 ## Verifying Contracts
 
 Sei's block explorer is [Seiscan](https://seiscan.io). The recommended verification method is [Sourcify](https://sourcify.dev/) — no API key required.
 
 ### Foundry
 
@@ -124,7 +124,7 @@
   --chain-id 1329
 ```
 
 For testnet, use `--chain-id 1328` and `--rpc-url https://evm-rpc-testnet.sei-apis.com`.
 
 ### Hardhat
 
@@ -134,7 +134,7 @@
 npm install --save-dev @nomicfoundation/hardhat-verify
 ```
 
 Add it to `hardhat.config.ts` — no additional Sourcify config block is needed:
 
 ```ts
 import '@nomicfoundation/hardhat-verify';
@@ -171,6 +171,6 @@
 
 | Network | Chain ID | RPC | Explorer |
 | --- | --- | --- | --- |
 | Mainnet | 1329 | `https://evm-rpc.sei-apis.com` | [seiscan.io](https://seiscan.io) |
 | Testnet | 1328 | `https://evm-rpc-testnet.sei-apis.com` | [testnet.seiscan.io](https://testnet.seiscan.io) |
 | Devnet | 713715 | `https://evm-rpc-arctic-1.sei-apis.com` | — |

evm/evm-parity/examples/erc1155.mdx

@@ -1,11 +1,11 @@
 ---
 title: 'ERC-1155 Interaction'
 description: 'Reading and writing ERC-1155 multi-token contracts on Sei with viem and ethers'
 ---
 
 # ERC-1155 Interaction
 
 ERC-1155 is the multi-token standard — a single contract can hold both fungible tokens (like gold coins in a game) and non-fungible tokens (like unique items), with efficient batch operations built in. Standard ERC-1155 contracts work on Sei without modification.
 
 ## Setup
 
@@ -14,7 +14,7 @@
 ```ts viem
 import { createPublicClient, createWalletClient, http, parseAbi } from 'viem';
 import { privateKeyToAccount } from 'viem/accounts';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const client = createPublicClient({ chain: sei, transport: http() });
 const account = privateKeyToAccount('0xYourPrivateKey');

evm/evm-parity/examples/erc20.mdx

@@ -1,11 +1,11 @@
 ---
 title: 'ERC-20 Interaction'
 description: 'Reading and writing ERC-20 tokens on Sei with viem and ethers'
 ---
 
 # ERC-20 Interaction
 
 Standard ERC-20 contracts work on Sei without modification. This page covers the common read and write operations using viem and ethers.
 
 ## Setup
 
@@ -14,7 +14,7 @@
 ```ts viem
 import { createPublicClient, createWalletClient, http, parseAbi } from 'viem';
 import { privateKeyToAccount } from 'viem/accounts';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const client = createPublicClient({ chain: sei, transport: http() });
 const account = privateKeyToAccount('0xYourPrivateKey');
@@ -227,4 +227,4 @@
 
 ## CosmWasm Token Compatibility
 
 CW20 tokens on Sei have ERC-20 pointer contracts that expose the standard ERC-20 interface. You can use all of the patterns above against a CW20 pointer address. See [Pointer Contracts](/evm/evm-parity/examples/pointer-contracts) for how to look up the pointer address.

evm/evm-parity/examples/erc721.mdx

@@ -1,11 +1,11 @@
 ---
 title: 'ERC-721 Interaction'
 description: 'Reading and writing ERC-721 NFTs on Sei with viem and ethers'
 ---
 
 # ERC-721 Interaction
 
 Standard ERC-721 contracts work on Sei without modification. This page covers reading token ownership, transferring NFTs, and managing approvals.
 
 ## Setup
 
@@ -14,7 +14,7 @@
 ```ts viem
 import { createPublicClient, createWalletClient, http, parseAbi } from 'viem';
 import { privateKeyToAccount } from 'viem/accounts';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const client = createPublicClient({ chain: sei, transport: http() });
 const account = privateKeyToAccount('0xYourPrivateKey');
@@ -221,4 +221,4 @@
 
 ## CosmWasm NFT Compatibility
 
 CW721 tokens on Sei have ERC-721 pointer contracts that expose the standard ERC-721 interface. You can use all of the patterns above against a CW721 pointer address. See [Pointer Contracts](/evm/evm-parity/examples/pointer-contracts) for how to look up the pointer address.

evm/evm-parity/examples/ethers-quickstart.mdx

@@ -1,11 +1,11 @@
 ---
 title: 'ethers v6 Quickstart'
 description: 'Using ethers v6 with Sei in a Node.js script or browser context'
 ---
 
 # ethers v6 Quickstart
 
 This example covers ethers v6 with Sei. The patterns apply whether you are writing a Node.js script, a CLI tool, or a browser app.
 
 ## Install
 
@@ -13,6 +13,12 @@
 npm install ethers
 ```
 
+These snippets are TypeScript. Run any of them with no separate build step using [`tsx`](https://www.npmjs.com/package/tsx) (Node 18+):
+
+```bash
+npx tsx script.ts
+```
+
 ## Read-Only Provider
 
 ```ts
@@ -26,13 +32,16 @@
 This is the first milestone — it needs no private key.
 
 ```ts
+// Any valid Sei EVM address — swap in your own
+const address = '0x0000000000000000000000000000000000000000';
+
 const blockNumber = await provider.getBlockNumber(); // number
 console.log('Block number:', blockNumber);
 
-const balance = await provider.getBalance('0xYourAddress'); // bigint, wei
+const balance = await provider.getBalance(address); // bigint, wei
 console.log('Balance (SEI):', ethers.formatEther(balance));
 
-const nonce = await provider.getTransactionCount('0xYourAddress'); // number
+const nonce = await provider.getTransactionCount(address); // number
 console.log('Nonce:', nonce);
 ```
 
@@ -44,7 +53,7 @@
 Nonce: 7
 ```
 
 The exact numbers are illustrative — your block number and balance will differ. `getBlockNumber()` and `getTransactionCount()` return a `number`, while `getBalance()` returns a `bigint` in wei (format it with `ethers.formatEther()`).
 
 ## Browser Provider
 
@@ -66,7 +75,7 @@
 
 ## Sending a Transaction
 
 Next step — this requires a funded account; get testnet SEI from the [faucet](/learn/faucet).
 
 ```ts
 const tx = await wallet.sendTransaction({
@@ -119,36 +128,9 @@
 contract.off('Transfer');
 ```
 
-## Using Python (web3.py)
-
-Sei is fully EVM-compatible, so any standard Ethereum client works — including Python's [web3.py](https://web3py.readthedocs.io).
-
-```bash
-pip install web3
-```
-
-```python
-from web3 import Web3
-
-w3 = Web3(Web3.HTTPProvider("https://evm-rpc.sei-apis.com"))
-
-print("Connected:", w3.is_connected())
-print("Latest block:", w3.eth.block_number)
-print("Chain ID:", w3.eth.chain_id)  # 1329
-```
-
-**You're done when you see:**
-
-```text
-Connected: True
-Latest block: 148203117
-Chain ID: 1329
-```
-
-The block number is illustrative; the chain ID is always `1329` on mainnet.
-
 ## Next Steps
 
+- [Python quickstart (web3.py)](/evm/python-quickstart) — the same first steps in Python
 - [ERC-20 interaction](/evm/evm-parity/examples/erc20) — full token read/write examples
 - [ERC-721 interaction](/evm/evm-parity/examples/erc721) — NFT ownership, transfers, and approvals
 - [Pointer contracts](/evm/evm-parity/examples/pointer-contracts) — interact with CosmWasm tokens via ERC interfaces

evm/evm-parity/examples/multicall.mdx

@@ -1,21 +1,21 @@
 ---
 title: 'Multicall'
 description: 'Batch multiple contract reads into a single RPC call using Multicall3 on Sei'
 ---
 
 # Multicall
 
 Multicall3 lets you batch multiple read calls into a single RPC round-trip, dramatically reducing latency for dashboards, portfolio pages, and any view that needs data from multiple contracts at once.
 
 Multicall3 is deployed at `0xcA11bde05977b3631167028862bE2a173976CA11` on Sei mainnet and testnet — the same address as Ethereum.
 
 ## Batching ERC-20 Reads with viem
 
 viem's `multicall` action wraps Multicall3 automatically:
 
 ```ts
 import { createPublicClient, http, parseAbi } from 'viem';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const client = createPublicClient({ chain: sei, transport: http() });
 
@@ -57,7 +57,7 @@
 
 ## Allowing Individual Call Failures
 
 By default, a single failed call causes the entire batch to revert. Use `allowFailure: true` (the default in viem) to get partial results instead:
 
 ```ts
 const results = await client.multicall({
@@ -77,9 +77,9 @@
 });
 ```
 
 ## Batching with ethers
 
 ethers doesn't have a built-in multicall action, but you can call the Multicall3 contract directly:
 
 ```ts
 import { ethers } from 'ethers';
@@ -116,7 +116,7 @@
 });
 ```
 
 ## Wagmi
 
 In React apps, `useReadContracts` handles batching automatically:
 

evm/evm-parity/examples/pointer-contracts.mdx

@@ -1,17 +1,17 @@
 ---
 title: 'Pointer Contracts'
 description: 'Looking up and interacting with pointer contracts that bridge CosmWasm and EVM tokens on Sei'
 ---
 
 # Pointer Contracts
 
 Sei runs two token execution environments side by side — EVM and CosmWasm. Pointer contracts are automatically deployed EVM contracts that proxy a CosmWasm token, and vice versa.
 
 | Token | Pointer type | EVM interface |
 | --- | --- | --- |
 | CW20 (CosmWasm fungible token) | ERC-20 pointer | Standard ERC-20 |
 | CW721 (CosmWasm NFT) | ERC-721 pointer | Standard ERC-721 |
 | Native Sei token (bank module) | ERC-20 pointer | Standard ERC-20 |
 
 Once you have the pointer address, you interact with it using the standard ERC-20 or ERC-721 interface — no Sei-specific code needed.
 
@@ -19,13 +19,13 @@
 
 ## Looking Up a Pointer Address
 
 The pointerview precompile resolves pointer addresses by CosmWasm contract address or native denom. Its ABI and address are exported from `@sei-js/precompiles`.
 
 <CodeGroup>
 
 ```ts viem
 import { createPublicClient, http } from 'viem';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 import {
   POINTERVIEW_PRECOMPILE_ABI,
   POINTERVIEW_PRECOMPILE_ADDRESS,

evm/evm-parity/examples/transaction-lifecycle.mdx

@@ -1,6 +1,6 @@
 ---
 title: 'Transaction Lifecycle'
 description: 'Send transactions, wait for receipts, and decode event logs on Sei'
 ---
 
 # Transaction Lifecycle
@@ -14,7 +14,7 @@
 ```ts viem
 import { createWalletClient, http, parseEther } from 'viem';
 import { privateKeyToAccount } from 'viem/accounts';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const account = privateKeyToAccount('0xYourPrivateKey');
 const walletClient = createWalletClient({ account, chain: sei, transport: http() });
@@ -136,7 +136,7 @@
 
 ## Checking for Revert
 
 A receipt with `status: 'reverted'` (viem) or `status: 0` (ethers) means the transaction was included but the execution failed. The gas was still consumed.
 
 ```ts viem
 const receipt = await client.waitForTransactionReceipt({ hash });

evm/evm-parity/examples/viem-quickstart.mdx

@@ -1,16 +1,22 @@
 ---
 title: 'viem Quickstart'
 description: 'Using viem with Sei in a Node.js script, CLI tool, or backend service'
 ---
 
 # viem Quickstart
 
 This example shows how to use viem with Sei outside of a React context — in a Node.js script, CLI tool, or backend service. For React apps, see [wagmi](https://wagmi.sh) and the [frontend guide](/evm/building-a-frontend).
 
 ## Install
 
 ```bash
-npm install viem @sei-js/precompiles
+npm install viem
+```
+
+These snippets are TypeScript. Run any of them with no separate build step using [`tsx`](https://www.npmjs.com/package/tsx) (Node 18+):
+
+```bash
+npx tsx script.ts
 ```
 
 ## Public Client
@@ -19,7 +25,7 @@
 
 ```ts
 import { createPublicClient, http } from 'viem';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const client = createPublicClient({
   chain: sei,
@@ -43,13 +49,16 @@
 ```ts
 import { formatEther } from 'viem';
 
+// Any valid Sei EVM address — swap in your own
+const address = '0x0000000000000000000000000000000000000000';
+
 const blockNumber = await client.getBlockNumber(); // bigint
 console.log('Block number:', blockNumber);
 
-const balance = await client.getBalance({ address: '0xYourAddress' }); // bigint, wei
+const balance = await client.getBalance({ address }); // bigint, wei
 console.log('Balance (SEI):', formatEther(balance));
 
-const nonce = await client.getTransactionCount({ address: '0xYourAddress' }); // number
+const nonce = await client.getTransactionCount({ address }); // number
 console.log('Nonce:', nonce);
 ```
 
@@ -70,7 +79,7 @@
 ```ts
 import { createWalletClient, http } from 'viem';
 import { privateKeyToAccount } from 'viem/accounts';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const account = privateKeyToAccount('0xYourPrivateKey');
 
@@ -85,7 +94,7 @@
 
 ## Sending a Transaction
 
 Next step — this requires a funded account; get testnet SEI from the [faucet](/learn/faucet).
 
 ```ts
 import { parseEther } from 'viem';
@@ -144,7 +153,7 @@
 
 ## Estimating Gas
 
 Always use `estimateGas` rather than hard-coding values. SSTORE costs on Sei are governance-adjustable.
 
 ```ts
 const gas = await client.estimateGas({
@@ -154,36 +163,9 @@
 });
 ```
 
-## Using Python (web3.py)
-
-Sei is fully EVM-compatible, so any standard Ethereum client works — including Python's [web3.py](https://web3py.readthedocs.io).
-
-```bash
-pip install web3
-```
-
-```python
-from web3 import Web3
-
-w3 = Web3(Web3.HTTPProvider("https://evm-rpc.sei-apis.com"))
-
-print("Connected:", w3.is_connected())
-print("Latest block:", w3.eth.block_number)
-print("Chain ID:", w3.eth.chain_id)  # 1329
-```
-
-**You're done when you see:**
-
-```text
-Connected: True
-Latest block: 148203117
-Chain ID: 1329
-```
-
-The block number is illustrative; the chain ID is always `1329` on mainnet.
-
 ## Next Steps
 
+- [Python quickstart (web3.py)](/evm/python-quickstart) — the same first steps in Python
 - [ERC-20 interaction](/evm/evm-parity/examples/erc20) — full token read/write examples
 - [ERC-721 interaction](/evm/evm-parity/examples/erc721) — NFT ownership, transfers, and approvals
 - [Pointer contracts](/evm/evm-parity/examples/pointer-contracts) — interact with CosmWasm tokens via ERC interfaces

evm/evm-parity/examples/wagmi-react.mdx

@@ -1,11 +1,11 @@
 ---
 title: 'Wagmi + React'
 description: 'Connect wallets, read chain state, and write transactions in a React app on Sei using Wagmi'
 ---
 
 # Wagmi + React
 
 [Wagmi](https://wagmi.sh) is the standard React library for EVM wallet connections and contract interactions. This page covers the essential patterns for a Sei frontend: configuration, wallet connect/disconnect, reading balances, and writing to contracts.
 
 For Node.js scripts and backend services, see the [viem Quickstart](/evm/evm-parity/examples/viem-quickstart) instead.
 
@@ -17,13 +17,13 @@
 
 ## Configuration
 
 Configure Wagmi with the Sei chain and your preferred wallet connectors:
 
 ```ts
 // wagmi.config.ts
 import { createConfig, http } from 'wagmi';
 import { injected, walletConnect } from 'wagmi/connectors';
-import { sei, seiTestnet } from '@sei-js/precompiles/viem';
+import { sei, seiTestnet } from 'viem/chains';
 
 export const config = createConfig({
   chains: [sei, seiTestnet],
@@ -183,7 +183,7 @@
 
 ```tsx
 import { useChainId, useSwitchChain } from 'wagmi';
-import { sei, seiTestnet } from '@sei-js/precompiles/viem';
+import { sei, seiTestnet } from 'viem/chains';
 
 export function NetworkSwitcher() {
   const chainId = useChainId();

evm/evm-parity/finality.mdx

@@ -1,29 +1,29 @@
 ---
 title: 'Finality and Block Tags'
 description: 'How Sei instant finality affects block tag behavior and pending state'
 ---
 
 # Finality and Block Tags
 
 Sei uses Twin Turbo Consensus, which provides instant finality. Every committed block is final immediately — there is no period where a block could be reorganized away.
 
 This changes how block tags behave compared to Ethereum.
 
 ## Block Tags
 
 On Ethereum, `latest`, `safe`, and `finalized` refer to different points in the chain:
 
 - `latest` — the most recent block, possibly not yet safe
 - `safe` — a block unlikely to be reorganized
 - `finalized` — a block that is permanently committed
 
 On Sei, all three tags resolve to the same block. There is no reorg risk at any point after a block is committed, so the distinction does not exist.
 
 <CodeGroup>
 
 ```ts viem
 import { createPublicClient, http } from 'viem';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const client = createPublicClient({ chain: sei, transport: http() });
 
@@ -66,9 +66,9 @@
 
 ## Pending State
 
 Sei does not expose Ethereum-style pending state. Do not rely on:
 
 - Reading pending transactions from the mempool
 - `eth_getBlockByNumber` with `'pending'`
 - Pending nonce differing from the confirmed nonce
 
@@ -76,9 +76,9 @@
 
 ## Practical Impact
 
 | Pattern | On Ethereum | On Sei |
 | --- | --- | --- |
 | Wait for `finalized` tag | Waits ~13 minutes | Returns immediately |
 | Check `safe` vs `latest` | Different blocks | Same block |
 | Read pending mempool | Supported | Not reliable |
 | Confirmation count | Meaningful | 1 is sufficient |

evm/evm-parity/gas-and-fees.mdx

@@ -1,15 +1,15 @@
 ---
 title: 'Gas and Fees'
 description: 'Sei gas price floor, EIP-1559 fee model differences, and SSTORE cost'
 ---
 
 # Gas and Fees
 
 Sei supports both legacy and EIP-1559 transactions, but the fee model differs from Ethereum in three ways that affect how you estimate and set gas.
 
 ## Legacy Gas Price Floor
 
 Legacy transactions (type 0) on Sei must meet a minimum gas price set by on-chain governance. This floor can change via governance proposals — do not hard-code a specific value.
 
 Use `eth_gasPrice` to read the current minimum:
 
@@ -17,7 +17,7 @@
 
 ```ts viem
 import { createPublicClient, http } from 'viem';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const client = createPublicClient({ chain: sei, transport: http() });
 const gasPrice = await client.getGasPrice();
@@ -35,7 +35,7 @@
 
 ## EIP-1559 Fee Model
 
 Sei supports EIP-1559 transactions (type 2), but does not burn the base fee. Fees go entirely to validators rather than being partially burned as on Ethereum.
 
 This does not affect how you construct or send transactions — `maxFeePerGas` and `maxPriorityFeePerGas` work as expected. It is relevant only if your application models token supply or displays fee-burn information to users.
 
@@ -84,9 +84,9 @@
 
 ## Summary
 
 | Behavior | Ethereum | Sei |
 | --- | --- | --- |
 | Legacy gas floor | Protocol minimum | Governance-set, can change |
 | Base fee | Burned | Paid to validators |
 | SSTORE cost | Fixed by EIP | Governance-adjustable |
 | `estimateGas` | Always correct to use | Required — do not hard-code storage costs |

evm/evm-parity/signing.mdx

@@ -1,15 +1,15 @@
 ---
 title: 'Signing'
 description: 'Wallet signing method support and EIP-712 typed data on Sei'
 ---
 
 # Signing
 
 Signing on Sei works through standard EVM libraries and wallet standards. The methods available depend on which wallet the user has connected.
 
 ## Wallet Signing Support
 
 | Method | Standard | Sei Global Wallet | MetaMask | WalletConnect wallets |
 | --- | --- | --- | --- | --- |
 | `personal_sign` | EIP-191 | Supported | Supported | Wallet-dependent |
 | `eth_signTypedData_v4` | EIP-712 | Supported | Supported | Wallet-dependent |
@@ -24,7 +24,7 @@
 
 ```ts viem
 import { createWalletClient, custom } from 'viem';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const client = createWalletClient({
   chain: sei,
@@ -138,7 +138,7 @@
 
 ## EIP-1271 Contract Signatures
 
 Smart contract wallets on Sei can validate signatures via EIP-1271 (`isValidSignature`). Use viem's `verifyMessage` with a contract address — it automatically uses EIP-1271 when the address is a contract.
 
 ```ts viem
 const valid = await verifyMessage({

evm/evm-parity/state-proofs.mdx

@@ -1,29 +1,29 @@
 ---
 title: 'State Proofs'
 description: 'How eth_getProof differs on Sei due to IAVL tree storage'
 ---
 
 # State Proofs
 
 Sei supports `eth_getProof` but returns a different proof format from Ethereum. If your application verifies proofs on-chain or off-chain, you need to account for this difference.
 
 ## The Difference
 
 Ethereum stores state in a Merkle Patricia Trie (MPT) and `eth_getProof` returns MPT inclusion proofs. Sei stores state in an IAVL tree and returns IAVL proofs instead.
 
 The RPC method exists and responds correctly, but the proof data structure is not compatible with Ethereum MPT proof verifiers.
 
 ## What This Affects
 
 Most applications do not call `eth_getProof` directly. It is primarily used by:
 
 - Light clients verifying state without trusting an RPC node
 - Cross-chain bridges proving inclusion of state on Sei
 - Applications verifying contract storage values trustlessly
 
 If you are doing standard contract reads, event queries, or transaction lookups, this difference does not affect you.
 
 ## Calling eth_getProof
 
 The call works through standard libraries:
 
@@ -31,7 +31,7 @@
 
 ```ts viem
 import { createPublicClient, http } from 'viem';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const client = createPublicClient({ chain: sei, transport: http() });
 
@@ -62,6 +62,6 @@
 
 ## Verifying Proofs
 
 To verify Sei state proofs, use an IAVL-compatible verifier. Standard Ethereum MPT verifier libraries (e.g. those used in Solidity or in Ethereum bridge contracts) will reject Sei proofs.
 
 Refer to the [Sei RPC reference](/evm/reference) for the exact proof schema returned.

evm/evm-parity/transaction-types.mdx

@@ -1,15 +1,15 @@
 ---
 title: 'Transaction Types'
 description: 'Which Ethereum transaction types are supported on Sei'
 ---
 
 # Transaction Types
 
 Sei supports most Ethereum transaction types. The one notable exception is blob transactions.
 
 ## Supported Types
 
 | Type | EIP | Name | Sei support |
 | --- | --- | --- | --- |
 | 0 | — | Legacy | Supported — governance-set minimum gas price applies |
 | 1 | EIP-2930 | Access list | Supported |
@@ -20,24 +20,24 @@
 
 | Type | EIP | Name | Notes |
 | --- | --- | --- | --- |
 | 3 | EIP-4844 | Blob | Not supported — Sei runs Pectra without blob transactions |
 
 ## Blob Transactions
 
 Sei runs the Pectra hardfork without blob transaction support. Attempting to send a type 3 transaction will be rejected at the RPC level.
 
 If you are porting code from Ethereum that uses blob transactions (e.g. rollup data availability), that path does not apply to Sei.
 
 ## Sending Transactions
 
 Standard library defaults work correctly. viem, wagmi, and ethers all default to type 2 (EIP-1559) transactions on chains that support it, which Sei does.
 
 <CodeGroup>
 
 ```ts viem
 import { createWalletClient, http, parseEther } from 'viem';
 import { privateKeyToAccount } from 'viem/accounts';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const account = privateKeyToAccount('0xYourPrivateKey');
 const client = createWalletClient({ account, chain: sei, transport: http() });

evm/evm-parity/websocket.mdx

@@ -1,19 +1,19 @@
 ---
 title: 'WebSocket Connections'
 description: 'Connecting to Sei via WebSocket for real-time block and event subscriptions'
 ---
 
 # WebSocket Connections
 
 Sei supports `eth_subscribe` over WebSocket. You can subscribe to new blocks, event logs, and pending transactions using standard library WebSocket transports.
 
 ## Endpoints
 
 | Network | WebSocket endpoint |
 | --- | --- |
 | Mainnet | `wss://evm-ws.sei-apis.com` |
 | Testnet | `wss://evm-ws-testnet.sei-apis.com` |
 | Devnet | `wss://evm-ws-arctic-1.sei-apis.com` |
 
 ## Connecting
 
@@ -21,7 +21,7 @@
 
 ```ts viem
 import { createPublicClient, webSocket } from 'viem';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 const client = createPublicClient({
   chain: sei,
@@ -112,5 +112,5 @@
 
 ## Notes
 
 - Sei's instant finality means every block emitted over WebSocket is already final — no need to wait for additional confirmations before acting on an event.
 - Pending transaction subscriptions (`newPendingTransactions`) are supported at the RPC level but Sei does not guarantee Ethereum-style pending state visibility.

evm/networks.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Sei EVM Networks"
 sidebarTitle: 'Network Information'
 description: "Discover network information for Sei EVM across all environments including mainnet and testnet. Access RPC endpoints, chain IDs, and blockchain explorers."
 keywords: ["sei evm", "network information", "chain ids", "rpc endpoints", "blockchain explorers"]
 ---
 
@@ -11,3 +11,8 @@
   loading="lazy"
   title="Sei EVM chain information"
 />
+
+The panel above is interactive. For plain-text endpoints you can copy directly — plus additional provider options — see:
+
+- [Chains & endpoints](/learn/dev-chains) — RPC URLs and chain IDs in plain text
+- [RPC providers](/learn/rpc-providers) — additional public and commercial RPC endpoints

evm/precompiles/example-usage.mdx

@@ -1,18 +1,18 @@
 ---
 title: 'Precompile Example Usage'
 sidebarTitle: 'Example Usage'
 description: "Learn how to interact with Sei's precompiles through viem and ethers, covering all available precompiles with quick examples and common patterns for seamless integration between EVM and Sei-native functionality."
 keywords: ['precompile usage', 'viem', 'ethers.js', 'sei precompiles', 'evm integration', 'quick start guide']
 ---
 
 Sei precompiles are special smart contracts deployed at fixed addresses that expose native Sei functionality to EVM applications. They can be called like any standard smart contract using viem, ethers, or wagmi.
 
 <Info>
 **Available Precompiles:**
 
 | Precompile | Address | Description |
 | --- | --- | --- |
 | Bank | `0x1001` | Query native denom balances (usei, factory tokens) |
 | JSON | `0x1003` | Parse JSON data within contracts |
 | Staking | `0x1005` | Delegation and staking operations |
 | Governance | `0x1006` | Proposal voting |
@@ -30,7 +30,7 @@
 
 ```ts viem
 import { createPublicClient, createWalletClient, http, custom } from 'viem';
-import { sei } from '@sei-js/precompiles/viem';
+import { sei } from 'viem/chains';
 
 // Read-only
 const client = createPublicClient({ chain: sei, transport: http() });
@@ -54,9 +54,9 @@
 
 </CodeGroup>
 
 ## Bank Precompile
 
 `eth_getBalance` only returns the EVM-side SEI balance. The Bank precompile lets you query any native denom — including factory tokens — from any address:
 
 <CodeGroup>
 
@@ -92,9 +92,9 @@
 
 </CodeGroup>
 
 ## Staking Precompile
 
 Delegate, undelegate, and query staking state:
 
 <CodeGroup>
 
@@ -149,7 +149,7 @@
 
 </CodeGroup>
 
 ## Governance Precompile
 
 Vote on an active governance proposal:
 
@@ -179,9 +179,9 @@
 
 </CodeGroup>
 
 ## Distribution Precompile
 
 Claim staking rewards from a validator:
 
 <CodeGroup>
 
@@ -211,9 +211,9 @@
 
 </CodeGroup>
 
 ## JSON Precompile
 
 Parse JSON data within EVM contracts or dApps — useful for processing oracle responses, NFT metadata, and structured payloads:
 
 <CodeGroup>
 
@@ -265,7 +265,7 @@
 
 ### Error Handling
 
 Wrap precompile calls in try/catch and check for specific error codes:
 
 ```ts
 try {
@@ -285,7 +285,7 @@
 
 ### Batch Read Operations
 
 Fetch multiple precompile values in parallel:
 
 ```ts
 const [delegation1, delegation2, rewards] = await Promise.all([
@@ -297,7 +297,7 @@
 
 ### Gas Limits
 
 Precompile calls that write state need enough gas. Use `estimateGas` rather than hard-coding:
 
 ```ts viem
 const gas = await client.estimateGas({
@@ -355,7 +355,7 @@
 
 ## Next Steps
 
 For full ABI reference and all available functions on each precompile:
 
 - [Staking Precompile →](/evm/precompiles/staking)
 - [Governance Precompile →](/evm/precompiles/governance)