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.

Do I need to do address association?

Yes, if you have funds at both a sei1 and a 0x address that came from the same seed phrase but appear as separate accounts on the chain. After SIP-3 final cutover (target mid-2026), unlinked sei1 addresses become read-only.

What if I only ever used a 0x address?

Nothing required. You're already on the surviving format. Your seed phrase still has a sei1 address derived from it (it always does), but if you've never used or funded it, there's nothing to associate.

Can I associate after the SIP-3 cutover?

Yes, but it's harder. Sei Labs is building post-cutover recovery tooling specifically for this case. It's materially easier to associate now than to recover after cutover.

Are these addresses compatible with Ethereum?

The 0x address format is the same format Ethereum uses, and the underlying cryptography (secp256k1) is the same. But the chains are different — your Sei 0x address holds SEI, not ETH. Sending ETH to a Sei 0x address would lose it. For tokens that exist on both chains, bridge with a proper bridging tool — don't just copy-paste an address.

Why does my sei1 address differ from my 0x address?

Because they're derived from different cryptographic operations on the same underlying public key. Hash one way → bech32 → sei1. Hash a different way → keccak256 → 0x. Same key, two encodings.

Can I have multiple 0x addresses from one seed phrase?

Yes. The derivation path m/44'/60'/0'/0/ lets you derive addresses with different n values. By convention, most wallets expose only the first one (n=0); for power users, multiple addresses are supported. Each 0x address has its own private key derivation — they're independent in the chain's eyes.

How does this affect privacy?

Both addresses are public on-chain. Address association makes the link between your two formats public too — anyone querying the chain can see they're the same account. If you want unlinkability, use a separate seed phrase for separate accounts; don't try to keep your sei1 and 0x addresses unassociated.

Learn · Sei Addresses (sei1 vs 0x)

Sei Addresses: sei1 vs 0x Explained

Sei has two address formats: sei1... (the older Cosmos format) and 0x... (the EVM format). Both refer to keys on the same chain — what differs is how transactions sign and which execution layer the address can interact with. SIP-3 is in progress with completion target mid-2026; after the final cutover, sei1 becomes read-only.

Download Sei Wallet

Open source
Free & open license
Independent audit
Signed builds

At a glance

	sei1...	0x...
Format	Bech32, 41-43 chars, prefix sei1	Hex, 42 chars total, prefix 0x
Used by	Cosmos transactions, CosmWasm, IBC bridging	EVM transactions, Solidity, MetaMask-compatible flows
Status	Legacy — read-only after SIP-3 cutover (mid-2026 target)	Primary post-SIP-3
Generated from	Same BIP-39 seed phrase	Same BIP-39 seed phrase
Hardware wallet	Ledger Cosmos app (legacy)	Ledger Ethereum app (current)
Chain ID	pacific-1 (Cosmos)	1329 (EVM)

Why two formats exist

Sei mainnet launched August 2023 as a Cosmos SDK chain. Cosmos chains use the bech32 address format — a human-readable encoding designed to detect typos. Sei addresses started with the prefix sei1 (the chain identifier).

In late 2023, Sei added EVM compatibility via the Sei V2 upgrade. Adding EVM meant adding a new transaction format — the same one Ethereum uses. Ethereum addresses are 20-byte hex values prefixed with 0x, displayed in checksummed hex (mixed case).

Rather than force users to choose, Sei kept both. A single key pair (one private key, one public key) generates both: hash one way → get a sei1 bech32 address; hash a different way → get a 0x hex address. So a user who held SEI at a sei1 address pre-V2 also has a corresponding 0x address derived from the same key.

When each format is used

sei1 used for:

CosmWasm smart contracts (deprecated post-SIP-3, still functional during transition).
Inbound IBC transfers from other Cosmos chains (being disabled via governance proposal pending mid-2026).
Cosmos-specific tooling (Cosmostation, Keplr Cosmos UI).
Pre-V2 staking (now legacy; staking moved to EVM in v6.3, January 2026).

0x used for:

All EVM transactions (the dominant use case post-V2).
Solidity smart contract calls (DeFi, NFTs, gaming dApps).
MetaMask, Rabby, Trust Wallet, and any EVM-generic wallet via custom RPC (chain ID 1329).
Post-v6.3 staking (the EVM-native staking module).
Wormhole, LayerZero, and Circle CCTP bridging.

What if I send SEI to a sei1 address using my 0x wallet?

The transaction will fail. EVM wallets can't construct Cosmos-formatted transactions. To send between formats, the addresses need to be associated on-chain (next section).

Address association — linking sei1 ↔ 0x on-chain

Address association is a one-time on-chain operation that tells Sei "this sei1 address and this 0x address are the same account." After association: dApps show a unified balance; both addresses can receive transfers; staking and governance work the same across both formats.

How to associate (from Sei Wallet)

Open Sei Wallet with both your sei1 and 0x addresses visible (auto-derived from your seed phrase).
Go to the Address Association tool in the wallet.
Sei Wallet checks if your two addresses are already linked. If not, it prepares the association transaction.
Sign the transaction. Costs a small gas fee.
After confirmation (~400ms), the addresses are linked.

Common confusion: it's not a transaction redirect. Association doesn't say "send anything that arrives at sei1 to 0x". It says "these two addresses share the same account state".

Generating addresses from a seed phrase

A standard 12- or 24-word BIP-39 seed phrase generates both formats. The derivation paths are different:

sei1 (Cosmos): derivation path m/44'/118'/0'/0/0 (Cosmos Hub default).
0x (EVM): derivation path m/44'/60'/0'/0/0 (Ethereum default).

Different paths from the same seed produce different keys. So a wallet that supports both formats actually maintains two different keys from your one seed phrase. This is why association matters: the chain needs to know these two distinct keys belong to the same user.

Step-by-step migration tool

For the full sei1 → 0x walkthrough with a transaction preview, see /migrate-cosmos-to-evm. Background on why this is happening: /learn/sip-3-migration.