I'm completely new to Sei. Where do I start?

Start with /learn/what-is-sei for the chain overview, then read /security to understand how Sei Wallet protects your funds, then download from /download and follow the in-app setup. The whole journey takes about 30 minutes including writing down your seed phrase carefully.

I'm migrating from another wallet. What do I read?

Start at /migration — it routes you to the right step-by-step guide based on which wallet you're coming from. Compass and Leap users have a hard May 28, 2026 deadline.

I'm an active SEI staker. What's relevant?

/staking/validators (validator evaluation), /staking/calculator (rewards math), /staking/unstaking (21-day unbonding), and /security/ledger if you want hardware-backed staking.

I'm a developer building on Sei. What's here?

/learn/sei-rpc for network configuration. For chain-level documentation see Sei's official docs at sei.io/docs — that's the canonical developer resource.

Where do I report bugs in Sei Wallet?

Either GitHub issues for non-security bugs, or security@seiwallet.net for security issues. See /security for the bug bounty program.

What's the difference between chain ID 1329 and chain ID pacific-1?

Different naming conventions for different execution layers. 1329 is the EVM chain ID (the integer chain ID Ethereum-style clients expect). pacific-1 is the Cosmos chain ID (a string identifier Cosmos clients expect). Both refer to the same chain — the chain knows which one your transaction is targeting based on the message format.

Is the official RPC reliable enough for production?

The official RPC is sufficient for low-to-medium traffic dApps and individual users. For production applications with high throughput, use a managed RPC provider (Alchemy, QuickNode, or similar) for SLAs and rate limits suitable for production use.

Do I need to add Sei testnet separately?

Yes — testnets have different chain IDs. Sei Atlantic-2 testnet: chain ID 1328, RPC https://evm-rpc-testnet.sei-apis.com. Sei Arctic-1 devnet: chain ID varies; for development only. Production transactions belong on chain ID 1329 (mainnet) only.

Is using a public RPC private?

No — RPCs by definition can see your queries (which addresses you check, which dApps you connect to). For privacy-sensitive work, run a local Sei full node or use a privacy-respecting provider. The same applies to all public RPCs across all chains.

Can the RPC operator censor my transactions?

Theoretically yes — an RPC operator could refuse to relay your transaction to validators. In practice, RPCs are run by entities with reputational reasons not to censor. If you're concerned, configure multiple RPCs in your wallet; if one fails, try another.

What chain ID does Sei Wallet use?

The same: 1329. Sei Wallet uses the official RPC by default and lets users override to a custom RPC in settings if they prefer. We don't manipulate chain ID; we connect to the chain like any other wallet.

Are these endpoints stable long-term?

Endpoint URLs occasionally change. Bookmark this page or chainlist.org for refresh. The chain ID 1329 is permanent — that won't change. The specific RPC URLs may rotate as infrastructure evolves.

Learn · Sei RPC Configuration

Sei RPC Endpoints — Chain ID and Network Configuration

Sei's chain ID is 1329. Public RPC endpoints are at evm-rpc.sei-apis.com. To use Sei from a custom wallet (MetaMask, Rabby, or anything that accepts a custom RPC), add Sei as a new network using the values below. Use these exact values — typos in chain ID can route transactions to the wrong network.

Skip the setup — download Sei Wallet

Download Sei Wallet

Open source
Free & open license
Independent audit
Signed builds

The values you need

Parameter	Value
Network name	Sei
Chain ID	1329
Currency symbol	SEI
RPC URL (official)	https://evm-rpc.sei-apis.com
Block explorer URL	https://seitrace.com
Cosmos legacy chain ID	pacific-1

The chain ID 1329 is what your wallet uses to confirm it's talking to the right network. Don't accept a custom RPC config that uses a different chain ID for "Sei" — that's a fake or test network.

Recommended approach: chainlist.org

The simplest way to add Sei to MetaMask, Rabby, or any chainlist-compatible wallet is via chainlist.org/chain/1329. Connect your wallet, click Add to MetaMask (or equivalent), approve the network add. Chainlist auto-fills all parameters with verified values — lower-risk than typing values manually. Or skip the setup entirely and download Sei Wallet, which ships with the network preconfigured.

Manual setup (if chainlist isn't available)

MetaMask

Open MetaMask → click the network dropdown at the top.
Click Add network → Add a network manually.
Enter Network name Sei, RPC https://evm-rpc.sei-apis.com, Chain ID 1329, Symbol SEI, Explorer https://seitrace.com.
Click Save.

Rabby

Open Rabby → network dropdown → Add Custom Network → enter the same values as above → Save.

Other EVM wallets

Most EVM wallets follow the same pattern. The key fields are chain ID (1329), RPC URL, and currency symbol (SEI). If your wallet doesn't have a "block explorer URL" field, that's optional.

Public RPC endpoints

Sei has multiple public RPC endpoints. The official one (run by Sei Labs) is the default chainlist publishes; community/redundant RPCs are useful under load.

Official: https://evm-rpc.sei-apis.com
Allnodes / PublicNode: https://sei-rpc.publicnode.com
Basement Nodes: https://evm-rpc.sei.basementnodes.ca
dRPC: https://sei.drpc.org
OmniaTech: https://endpoints.omniatech.io/v1/sei/mainnet/public

Verify current endpoints at sei.io/docs or chainlist.org. RPCs go in and out of service; the values above are accurate as of mid-2026 but treat them as "check before heavy use."

Archive RPCs (historical state)

For applications that need state at older block heights: Alchemy (alchemy.com/sei), QuickNode (quicknode.com/chains/sei), Blast API (blastapi.io). These are paid services for production applications.

Cosmos-side endpoints (legacy / pre-SIP-3)

For Cosmos-side tooling during the SIP-3 transition window:

Cosmos chain ID: pacific-1
Cosmos RPC: https://rpc.sei-apis.com
Cosmos REST: https://rest.sei-apis.com
Cosmos block explorer: https://www.mintscan.io/sei

These remain functional during SIP-3 transition but become read-only after the final cutover (mid-2026 target). For new development, target the EVM endpoints.

What to do if your transaction fails after RPC setup

"Wrong chain ID": Double-check chain ID is exactly 1329. Both number 1329 and string "1329" should work; 0x531 (hex) is also valid in some interfaces.
"RPC unreachable" / timeout: Switch to a community RPC. If multiple fail simultaneously, the chain may be undergoing an upgrade — check sei.io/status.
"Transaction reverted": Usually a smart-contract issue. Use seitrace.com to see the actual revert reason.
"Insufficient gas": Sei follows EIP-1559. Bump priority fee slightly and retry. Sei gas costs are generally low (~$0.0001).
Wallet shows wrong balance after RPC switch: Some wallets cache per RPC. Restart the wallet or refresh the network connection.

Adding Sei to a non-EVM tool

Cosmos SDK tooling (legacy): Use Cosmos endpoints above. EOL post-SIP-3 final cutover.
Generic chain indexers: The Graph (Sei subgraphs), Goldsky, Pyth oracle data via Pyth's standard EVM tooling.
dApp frameworks: Standard EVM frameworks work without modification — wagmi/viem, ethers.js, web3.js, Hardhat, Foundry.