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.

Did SIP-3 already happen?

Approved May 2025; partially implemented through 2026; not yet fully complete. Multiple network releases (v6.3, v6.4, v6.5) shipped pieces of the transition. The final EVM-only cutover is the mid-2026 target with no specific date announced.

Will my SEI tokens disappear?

No. SEI tokens persist through the transition. Your balance is tied to your address (whether sei1 or 0x), and the address persists. What changes is which address formats can originate new transactions.

Will I lose my staking rewards?

No. Pending rewards persist through the transition. Staking continues earning rewards on EVM-native staking (since v6.3). Address association preserves your delegation; the validator and delegated amount carry over.

Is this the same as Compass and Leap shutting down?

No — different events. Compass and Leap (two specific wallets) are shutting down on May 28, 2026 due to their teams' operational decisions. SIP-3 is a chain-level upgrade affecting all wallets. Compass/Leap users need to migrate to a different wallet regardless of SIP-3 status.

Can I still bridge ETH or USDC onto Sei after IBC disable?

Yes — those use EVM-native bridges (Wormhole for ETH, Circle CCTP V2 for native USDC, LayerZero for various tokens). EVM bridging is unaffected by SIP-3. Only Cosmos IBC bridging is being disabled.

Will the final cutover affect chain finality or block times?

Probably not — if anything, removing the dual-VM overhead allows some optimizations. Sub-400ms finality continues. The user-visible chain behavior is essentially unchanged from the pre-cutover state.

Where do I track the actual cutover date?

Sei Labs blog (blog.sei.io), Sei docs (docs.sei.io/learn/sip-03-migration), the Sei governance forum, and major chain announcements. The canonical source is Sei Labs' official channels.

Learn · SIP-3 Migration · In progress, completion target mid-2026

SIP-3 Migration: What Sei Users Need to Know

SIP-3 transitions Sei from a dual-stack chain to an EVM-only chain. Approved by community vote in May 2025, the changes are rolling out across multiple network releases through 2026, with full completion targeted for mid-2026. As of mid-2026, the transition is in progress — most user-facing changes have happened, but the final cutover (Cosmos message handling fully removed) has not yet been executed.

Download Sei Wallet

Open source
Free & open license
Independent audit
Signed builds

The 60-second version

What SIP-3 does: removes Sei's original Cosmos execution layer, leaving the parallelized EVM as the only execution environment.
Why: simplifying to one VM lets Sei focus performance work on a single execution layer. Sets up the next major upgrade (Sei Giga, targeting 200,000+ TPS).
Status as of mid-2026: in progress. v6.3 (EVM-native staking) shipped January 2026. v6.4 (IBC-disable mechanism) shipped mid-April 2026. v6.5 (oracle replacement) shipped early-2026. Final cutover targeted mid-2026 with specific date not yet announced.
What you need to do: depends on what you hold. Most users with 0x SEI need to do nothing. Users with stranded sei1 holdings or specific IBC tokens need to migrate.

The release timeline

Release	Approximate date	What it does
Pre-v6	mid-2025	SIP-3 proposal approved by Sei governance, May 2025.
v6.3	January 2026	EVM-native staking module ships — staking now routes through EVM rather than Cosmos.
v6.4	mid-April 2026	Ships the mechanism to disable inbound IBC. Activation requires a separate governance proposal.
v6.5	early-mid 2026	Removes Sei's native oracle (replaced by Chainlink, API3, Pyth).
Final cutover	mid-2026 (target)	Cosmos message handling fully removed. Specific date not yet announced.

The April timing of v6.4 was sometimes reported externally as "Sei went EVM-only in April 2026." That's a mischaracterization. v6.4 shipped the capability to disable IBC; the actual disable requires a community governance proposal that, as of mid-2026, has not yet been voted in. The final EVM-only state is still ahead.

What you need to do, by holdings type

If you only hold SEI at 0x addresses

Nothing required. You're already on the surviving address format. Your wallet (Sei Wallet, Keplr, MetaMask via custom RPC, Rabby) continues to work.

If you hold SEI at a sei1 address

Migrate before the final cutover. Use a wallet that supports both formats; let it derive the matching 0x address from the same seed; run the address-association tool. After association, dApps treat the two addresses as the same account. Step-by-step: /migrate-cosmos-to-evm.

If you hold IBC-bridged tokens on Sei

Token	What it is	Recommended action
USDC.n	USDC bridged via Noble IBC	Convert to native USDC via Circle's CCTP V2.
ATOM	Cosmos Hub native, bridged via IBC	Bridge back to Cosmos Hub via Skip:Go before IBC disable.
Wormhole IBC	Bridged via Wormhole's older Cosmos integration (USDCet, USDCop, etc.)	Bridge back to origin chain via Wormhole's portal.
Kava USDT	Tether bridged from Kava via IBC	Bridge back to Kava or swap for native USDT.

If you stake SEI

Nothing extra required beyond the address migration above. v6.3 moved staking onto EVM in January 2026; existing delegations and pending rewards persist through subsequent upgrades.

What if I don't migrate before final cutover?

Your SEI is not at risk of being burned or taken. It just becomes inaccessible from the sei1 address. The balance remains visible on chain explorers. The chain still knows about it. But after cutover you cannot send transactions from the sei1 address because Cosmos message handling has been removed. To recover access, you'd need to associate sei1 with 0x on-chain — but you'd need post-cutover recovery tooling. Migrate while the tools are routine, not urgent.

Start migration now

The full step-by-step is at /migration. Background on what changed: /learn/sei-evm.