Layer 1 blockchain

Sei ticker SEI

No public-data lookups yet
5 reviewed developments
40 cited sources

Summary

Delegated proof-of-stake chain whose node software (sei-chain) is built on forks of the Cosmos SDK and Tendermint. Sei calls its tuned consensus Twin Turbo: Tendermint-derived BFT voting with shortened timeouts, plus optimistic parallel execution that runs while validators vote, targeting about 400ms blocks. A block commits once validators holding more than 2/3 of voting power precommit it. Execution is an EVM using optimistic concurrency control; existing CosmWasm contracts still run, but new ones cannot be deployed, and SIP-3's final step would also switch off the remaining CosmWasm execution. The Giga upgrade is partly shipped: v6.6 (mainnet, 4 August 2026) made the new Ares execution client the default path for upgraded nodes and began a phased, operator-controlled Eidos storage migration, while the multi-proposer Autobahn consensus ships disabled until a separate network activation. 2 3 6 11 14 16 20 29

Design

System: Layer 1 blockchainSei mainnet (Cosmos chain ID pacific-1, EVM chain ID 1329) is a sovereign proof-of-stake chain with its own validator set; it does not settle to another chain and no Cosmos Hub shared-security arrangement was found. Under SIP-3 it is moving to EVM-only access: new CosmWasm deployments and IBC transfers are already disabled, and a shutdown of Cosmos-format transactions was announced for 15 June 2026 but was not confirmed as active in this review.
Settlement family: Cosmos SDK
Scarce resource: Stake (proof of stake)
State model: Accounts
Finality: Other
Who makes blocks: Validators from an active set capped at 40 (Sei technical reference), weighted by delegated SEI; the Seistream explorer showed 40 active validators on 2026-09-27. Unbonding takes 21 days. Proposer rotation in proportion to voting power is inferred from the Tendermint lineage rather than from a Sei-specific page.
Fork choice: No open weight-based fork choice: a height is decided by more than 2/3 precommits, and Sei documents every committed block as final with no reorganisation window. Conflicting commits would need at least 1/3 of voting power to double-sign; Sei's parameters permanently remove (tombstone) a double-signing validator but slash 0% of its stake.

Qualifications

Settlement family · Partial. Filed with Cosmos SDK chains because the node software forks the Cosmos SDK and Tendermint, and staking and governance run on that stack. Under SIP-3 users interact through the EVM only, IBC is closed in both directions and new CosmWasm contracts are blocked, so usual Cosmos-family expectations such as IBC transfers no longer apply. An Ethereum-family filing would also be defensible.
Ibc · Not applicable. Sei documents IBC as disabled in both directions: inbound by governance Proposals 116 and 120, and outbound by Proposal 121, which passed on 31 July 2026. IBC tokens left on Sei can still move between Sei addresses but can no longer be redeemed on their origin chain over IBC.
Cosmos transactions · Contested. Sei announced that Cosmos-format transactions and sei1 address association would stop on 15 June 2026. Sei pages retrieved on 2026-09-27 still describe that shutdown as slated, no mainnet release notes or later announcements reviewed confirm it, and the September 2026 v6.7 release candidates, which remove the IBC modules, were still pre-releases, so whether the shutdown is active was not confirmed.
Slashing · Partial. Sei's technical reference lists 0% stake slashing for both downtime and double-signing; double-signing permanently removes the validator and downtime brings a 10-minute jail. Safety still assumes more than 2/3 of voting power is honest, but a violation costs validators their position rather than bonded stake.
Shared security · Not applicable. Sei's documentation describes its own active set capped at 40 validators; no Cosmos Hub shared-security arrangement was found, so Cosmos Hub security properties do not describe Sei.
Finality · Partial. Blocks are final at commit: Sei documents that its latest, safe and finalized block tags point to the same block and that committed blocks cannot be reorganised. This profile does not count that as finality backed by stake, because Sei takes 0% of stake for double-signing; reverting a committed block would cost validators their seats, not bonded SEI. The sub-250ms ordering finality reported for Giga comes from an internal devnet, not mainnet.

Tradeoffs

This view follows one way of thinking about design priorities, often called the blockchain trilemma. The design-priorities lesson sets out the counter-view. Read the design-priorities lesson.

Emphasizes

Scalability

Gives up

Operational decentralization: consensus is limited to at most 40 active validators, and Sei's node page lists 16 cores, 256 GB RAM, a 2 TB high-IOPS NVMe drive and a 2 Gbps low-latency link. The chain also cannot commit blocks if more than 1/3 of voting power is offline, so a small group of large validators can halt it.Security is not listed as a design emphasis because Sei slashes 0% of stake for double-signing or downtime; a safety violation costs validators their position, not bonded SEI. Readers who count deterministic BFT finality as a security emphasis may reasonably disagree. The liveness point is inferred from the more-than-2/3 commit rule. Throughput figures appear only as classified claims in this profile.

Full node at home

Data-center class 8 9 10 11Sei's node documentation lists 16 CPU cores, 256 GB DDR5 RAM, a 2 TB high-IOPS NVMe SSD and a 2 Gbps low-latency network without naming a node type; the sei-chain README gives a lower minimum of 64 GB RAM, 1 TB NVMe and 16 cores. Archive nodes need 10 TB+ disks. Non-archive nodes keep about 28 hours of history by default and can join through state sync or snapshots. The rating describes the published hardware, not where a node must run.

Throughput claims

Lab benchmark: 5 13 14Controlled benchmark; not observed network behavior.Gigagas per second (billions of EVM gas units per second), not transactions per second.Internal devnet result reported in the Giga whitepaper v2.0 (June 2026)Internal devnet of 40 nodes across 20 regions; node hardware is not stated on the reviewed pages, and Sei says the whitepaper publishes no validator hardware specification.Measured on Sei Labs' own internal devnet, not observed mainnet load; the reviewed pages do not say which consensus configuration the devnet ran, and Giga's Autobahn consensus is not active on mainnet. Gas per second depends on transaction mix and Sei's gas schedule, so it cannot be compared with another chain's gas or transaction figures. No workload, bandwidth or state-size details were published on the reviewed pages; the figure ignores propagation to ordinary full nodes and long-run state growth.
Theoretical peak: 200,000 tx/s 13 14 15Theoretical peak; not comparable across chains or with observed load.Roadmap target (at 400ms finality) for a future public Autobahn testnet milestone; not a measurementSei's Giga pages present this as a public-testnet roadmap target, separate from the devnet measurement; the whitepaper blog post states it as network throughput without any test setup. Ignores propagation, state growth and spam or decoy load; not comparable with any other chain's figure.
Unclassified: 15,000 tx/s 16Unclassified; do not compare.Listed as 15,000+ for simple transfers under parallel execution in a sequential-versus-parallel table; the same table gives lower figures for token transfers, DEX swaps and complex contracts.Sei's parallelization page gives no method, hardware, window or network setup, so the figure is left unclassified. Describes the execution engine only; says nothing about consensus, propagation, state growth or whether full nodes keep up.
Unclassified: 100 4Unclassified; do not compare.Approximate megagas per second, from a table on Sei's EVM-differences documentation page; not transactions per second.Stated as an approximate table entry with no method, window or hardware; unclassified. Gas schedules differ between chains (Sei charges 72,000 gas for a storage write), so gas-per-second figures are not comparable across chains.

Headline figures are not comparable across chains. A theoretical peak is never a like-for-like number.

Scaling layers

No scaling layer recorded in this profile.

Capabilities

Capabilities of Sei: how each one is provided, or its research status
Capability	How it is provided	Notes and sources
Account abstraction	Structured assessment pending	Not yet assessed for any chain.
Atomic swaps	Unknown	No protocol-level hash-locked or equivalent trust-minimized swap on Sei was reviewed; EVM contracts could implement one, but none was verified. Moving tokens through bridges is not an atomic swap.
Authenticated data publication	Unknown	Not yet assessed under this row's current definition.
Light clients	Unknown	Not yet assessed under the current definitions; Sei answers state-proof requests with IAVL-format proofs, which standard EVM proof verifiers reject, and names light clients as a use case, but no supported light-client path that checks proofs against block headers was documented. IBC, which relied on on-chain light clients, is disabled. 21 22
Native staking or delegation	Structured assessment pending	Not yet assessed for any chain.
On-chain governance	Structured assessment pending	Not yet assessed for any chain.
Parallel execution	Structured assessment pending	Not yet assessed for any chain.
Payment or state channels	Unknown	No payment or state channel layer anchored to Sei was reviewed.
Programmable spending	Native (protocol or core-team software) Earlier definition	Spend conditions are EVM smart contracts, and Sei lists account-abstraction entry-point contracts. Existing CosmWasm contracts still execute, but governance Proposal 115 blocked new uploads and instantiations, and SIP-3's final step would switch off the remaining CosmWasm execution. 1 18 20 23
Protocol-verified messaging	Structured assessment pending	Not yet assessed for any chain.
Reversible transfers or recovery	Unknown	Not yet assessed under the current definitions; no protocol feature for cancelling, delaying or reclaiming a payment, or for recovery through a predefined role or delay, was verified. Account-abstraction entry-point contracts are deployed on Sei and smart-contract wallets may offer recovery, but none was reviewed. 23
Rollups	Unknown	No rollup settling to Sei was found in reviewed sources; absence was not exhaustively verified. Giga is an upgrade of Sei itself, not a rollup. 13
Shielded transfers	Structured assessment pending	Not yet assessed for any chain.
Signed partial offers	Unknown	Not yet assessed under this row's current definition.

Reading these values

How this feature is provided: Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
Structured assessment pending: The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
Unknown: The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
Earlier definition: Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
Reading across rows: The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.

Definitions, schema version and review history

Ecosystem & custody

Ecosystem products for Sei
Product type	Status	Notes and sources
Automated market makers	Established in the ecosystemDragonSwap (contracts listed under Saphyre), Sailor Finance, oku.trade (v3 contracts), DonkeSwap	Sei's ecosystem-contracts page lists AMM factory and router contracts for these venues, and DragonSwap's docs describe V1 pools and V2 concentrated-liquidity pools on Sei. dragonswap.app now redirects to saphyre.xyz, whose page describes leverage trading, so the AMM's current branding is unclear. Liquidity depth was not measured. 23 37 As of Sep 27, 2026.
Issuer-native stablecoins	Established in the ecosystemUSDC (Circle)	Circle lists natively issued USDC on Sei (0xe15fC38F6D8c56aF07bbCBe3BAf5708A2Bf42392; 6 decimals per Sei's docs). Sei also lists USDT0 and Ondo USDY contracts, whose issuer arrangements were not reviewed. The older IBC-delivered USDC.n can no longer be redeemed over IBC; Sei advises swapping it for native USDC. 18 23 25 35 As of Sep 27, 2026.
Algorithmic stablecoins	Unknown	Algorithmic or hybrid stablecoins on Sei were not reviewed. As of Sep 27, 2026.
Bridges	Established in the ecosystemCircle CCTP V2 (domain 16), LayerZero V2 (endpoint 30280), Stargate, Symbiosis	Circle lists Sei on CCTP V2; Sei's docs cover LayerZero V2 with 11 available verifier networks and list Stargate and Symbiosis contracts. IBC is disabled in both directions, so Sei no longer has a protocol-native bridge. Risk: Each bridge adds its own trust: CCTP relies on Circle's attestations, and LayerZero messages rely on the verifier networks and settings each application chooses; Sei's guide warns that LayerZero default settings are placeholders and that an unconfigured pathway fails. A bridged token is only as sound as its bridge and origin chain. Tokens that arrived over IBC and were not moved before it closed can no longer be redeemed that way. 21 23 24 36 As of Sep 27, 2026.
Block explorers	Established in the ecosystemSeiscan (Etherscan team), Seistream (STAKEME), NG Explorer (Nodes Guru)	Sei's explorer page lists these three for mainnet; Seiscan says it is built by the Etherscan team and Seistream covers both Cosmos and EVM views. Explorer data is provider-indexed, not canonical consensus. 26 27 28 As of Sep 27, 2026.
Hardware wallets	ThinLedger (Sei EVM behind a switch that is off by default in Ledger Wallet; MetaMask route per Sei's docs)	See custody rows: Ledger Wallet's code includes Sei EVM behind a switch that is off by default, and Sei's docs describe Ledger signing through MetaMask with the Ethereum or Sei device app; Trezor's page says it does not support Sei. Sei's wallet page also lists Arculus, which was not reviewed. 31 33 34 39 As of Sep 27, 2026.

Hardware-wallet custody

Hardware-wallet custody for Sei
Device maker	Status	What users can and cannot do
Ledger	PartialSame as native: Unknown	Can: Sign Sei EVM transactions on a Ledger device through MetaMask using the Ethereum app, per Sei's documentation Can: Install a dedicated Sei app from the Ledger Live app catalog, per Sei's setup guide Can: Check receive addresses on the device before sharing them Cannot: Count on Sei appearing in Ledger Wallet: its Sei EVM module sits behind a feature switch that is off by default, and no Ledger page confirming it is on was found Cannot: Use Ledger Wallet for sei1 accounts: its code has no module for Sei's Cosmos side, and Sei's docs describe the older Cosmos-app flow as deprecatedLedger Wallet's code includes Sei EVM but hides it unless a remotely controlled switch is turned on, and that production setting could not be read; Ledger's own Sei pages returned 404. The MetaMask route comes from Sei's documentation. A February 2026 Sei blog post says Ledger Enterprise, Ledger's institutional platform, supports Sei token sends and receives; that is Sei's statement, not a Ledger page, and does not describe consumer use. 30 31 32 38 39 40 As of Sep 27, 2026.
Trezor	None foundSame as native: No	Cannot: Manage SEI in Trezor SuiteTrezor's Sei page says Trezor does not currently support Sei. Whether a Trezor can sign Sei EVM transactions through a third-party EVM wallet on a custom network was not verified. 34 As of Sep 27, 2026.

Public data

iKnow Blockchain has no public-data lookups for Sei yet. This is a limit of the service, not a statement about the network.

Public-data lookups for Sei
Lookup	Status	What it covers and its limits
Address or account	Not available yet	Public-data lookups for this chain are not built yet.
Tokens and assets	Not available yet	Public-data lookups for this chain are not built yet.
NFTs	Not available yet	Public-data lookups for this chain are not built yet.
Transactions	Not available yet	Public-data lookups for this chain are not built yet.

A lookup covers one address or transaction from one provider. It is never a complete wallet, and an error or private value is reported as unknown, not zero. About public data · Connect your AI

Sourced developments

Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.

Publication date · newest first

Published Aug 28, 2026ProtocolVerified against sources

sei-chain v6.6.3 fixed validator snapshot problems and added a freeze mode for historical EVM RPC

The v6.6.3 patch release, published on 28 August 2026, is recommended for validators, full-node operators and RPC operators. For validators it fixes a memory leak in memiavl snapshot writes, closes a race that could publish a truncated snapshot file, and checks snapshots before they are made current. For RPC operators it adds a freeze mode that holds a node at an upgrade boundary while it keeps serving historical EVM state, plus a router that sends each block-specific request to the matching frozen node. The notes say it contains no state-machine or consensus-breaking changes.
- Implementation:Released
- Release:v6.6.3 published 28 August 2026 as a recommended patch release
- Activation:no network activation; changes apply on each node that installs the release
Date basis: GitHub release v6.6.3 published 2026-08-28 18:33 UTC (GitHub releases API); it is a stable release, not a pre-release, and names no upgrade height.

Sources: Sei Protocol contributors — sei-chain v6.6.3 release notes (external site) · Sei Protocol contributors — sei-chain releases (external site) · Sei Protocol contributors — Release notes from sei-chain (Atom feed) (external site)
Published Jul 31, 2026ProtocolVerified against sources

IBC closed in both directions on Sei

Governance Proposal 121, which passed on 31 July 2026, switched off outbound IBC transfers on Sei, after Proposals 116 and 120 had already disabled inbound transfers. IBC tokens still on Sei can move between Sei addresses but can no longer be sent back to their origin chains over IBC.
- Proposal:Proposal 121 passed 31 July 2026
- Implementation:IBC module outbound transfers disabled; inbound disabled by Proposals 116 and 120
- Release:governance parameter change; v6.4 (April 2026) added the inbound switch
- Activation:active per Sei documentation
Date basis: Sei's migration guide and exchange guide both state that Proposal 121 disabled outbound IBC on 31 July 2026, and that Proposals 116 and 120 disabled inbound IBC.

Sources: Sei Documentation — SIP-03 Migration Guide (external site) · Sei Documentation — Sei EVM Upgrade for Exchanges and Custodians (external site) · Sei Documentation — Sei Network Interoperability Framework (external site) · Sei Blog — Sei v6.4 Is Live on Mainnet: What It Means for IBC (external site)
Published Jul 31, 2026ProtocolVerified against sources

Sei v6.6 brought the first Giga components to mainnet

The mandatory v6.6.0 release, targeting mainnet height 224,201,091 on 4 August 2026, made the Ares execution client the default execution path for upgraded nodes and began the first, operator-controlled phase of the Eidos storage migration, which separates EVM history from other chain state. Autobahn consensus code is included but disabled until a separate network activation.
- Proposal:Software upgrade Proposal 122 (v6.6, height 224,201,091) was open for voting on 31 July 2026 per Sei's blog and is shown as passed on the Seistream explorer
- Implementation:Released
- Release:v6.6.0 released 31 July 2026 as a mandatory mainnet upgrade
- Activation:Sei's Giga page reports activation on 4 August 2026; the upgrade height was not checked on chain
Date basis: GitHub release published 2026-07-31 with a target upgrade time of 2026-08-04 16:30 UTC; Sei blog post dated 31 July 2026; Sei's Giga pages report v6.6 reaching mainnet at the target height on 4 August 2026.

Sources: Sei Protocol contributors — sei-chain v6.6.0 release notes (external site) · Sei Blog — Ares and Eidos, the first components of the Giga Upgrade, will go live in Sei 6.6 (external site) · Sei Blog — The Eidos Upgrade: replacing Sei's storage database while the chain is running (external site) · Sei Documentation — What Is Sei Giga? (external site) · Sei Documentation — Sei Giga Technical Specification (external site) · STAKEME — Proposal #122: v6.6 (external site)
Published May 7, 2026ProtocolProposed, not adopted

Sei scheduled the end of Cosmos-format transactions for 15 June 2026

Sei told exchanges and custodians to switch to 0x-address integrations before 15 June 2026, after which Cosmos-native transaction interfaces and new address associations through Cosmos wallets would stop working. Funds under sei1 addresses that were never associated would not be accessible.
- Proposal:part of SIP-3
- Implementation:announced; activation not observed
- Release:no release or upgrade height named in reviewed sources
- Activation:not confirmed as of 2026-09-27
Date basis: Sei blog post dated 7 May 2026 sets the 15 June 2026 deadline; Sei docs retrieved on 2026-09-27 still describe the shutdown as upcoming.

Sources: Sei Blog — What SIP-03 means for exchanges and custodians (external site) · Sei Documentation — Sei EVM Upgrade for Exchanges and Custodians (external site) · Sei Documentation — SIP-03 Migration Guide (external site)
Published May 1, 2026ProtocolVerified against sources

Governance blocked new CosmWasm deployments on Sei

As part of SIP-3, Proposal 115 made new CosmWasm code uploads and contract instantiations fail on Sei. Existing CosmWasm contracts keep running and can still be queried, and new tokens are expected to use ERC standards.
- Proposal:Proposal 115 passed, per Sei's migration guide
- Implementation:uploads and instantiations blocked
- Release:governance change; no separate client release named in reviewed sources
- Activation:active per Sei's blog and migration guide
Date basis: Sei blog post dated 1 May 2026; Sei's migration guide attributes the change to Proposal 115.

Sources: Sei Blog — SIP-03: No new CosmWasm contract deployments (external site) · Sei Documentation — SIP-03 Migration Guide (external site) · Sei Documentation — Token Standards (external site) · sei-protocol/sips — SIP-3: EVM only (external site)

Topics your AI can explain

Your AI can explain these topics for Sei through the connection, with sources.

What Sei is and how SEI is counted
How Sei reaches agreement: Twin Turbo consensus and its validators
Sei's account model and dual addresses
Fees and units on Sei
Finality on Sei: final at commit, no reorganisations
SIP-3: Sei's move to EVM-only
Parallel execution, Giga, and how to read Sei speed claims
Moving value to and from Sei, stablecoins and hardware wallets

Known gaps

What this profile's review did not establish:

Whether Cosmos-format transactions and sei1 address association actually stopped on or after 15 June 2026 is unconfirmed; Sei pages retrieved on 2026-09-27 still describe the shutdown as upcoming.
A v6.7 release candidate published in September 2026 lists removal of the IBC modules and legacy Sei-specific RPC methods; it was still a pre-release when reviewed, and no mainnet upgrade height for it was found.
Sei's two hardware statements disagree (docs: 256 GB RAM, 2 TB NVMe, 2 Gbps, node type not named; README: 64 GB RAM, 1 TB NVMe minimum), and current chain and snapshot sizes were not captured.
Sei's node guide says keeping 100,000 recent state versions is roughly 28 hours of mainnet history; with one version per block that implies about one block per second rather than the 400ms target. Observed block times were not measured.
How stake is spread across the 40 active validators, and how few of them together hold more than one-third of voting power, was not verified.
Whether the SIP-4 fee-parameter changes are active on mainnet was not confirmed.
Ledger's own pages for Sei returned 404, and the production setting of Ledger Wallet's Sei EVM switch (off by default in code) could not be read; a Trezor signing path through third-party EVM wallets was not checked.
DragonSwap's site now redirects to saphyre.xyz; the AMM's current operator and branding are unclear. Sailor Finance's site did not resolve, so it is listed only from Sei's contract page.
Issuer arrangements for USDT0 and USDY on Sei, algorithmic stablecoins, atomic swaps, reversible or delayed transfers and recovery, light clients, channels and rollups were not reviewed.
No rollup, channel or sidechain anchored to Sei was verified, so no scaling layers are listed.
The Autobahn activation date and any Giga-specific node hardware requirements are not published on the reviewed pages.
Past chain halts or incidents on Sei were not reviewed.

Sources

Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.

All 40 sources were checked in the last 30 days.

Sei documentation home (external site)Sei Documentation · retrieved Sep 27, 2026
Twin Turbo Consensus (external site)Sei Documentation · retrieved Sep 27, 2026
Finality and Block Tags (external site)Sei Documentation · retrieved Sep 27, 2026
Sei EVM vs Ethereum: Key Differences (external site)Sei Documentation · retrieved Sep 27, 2026
Gas and Fees (external site)Sei Documentation · retrieved Sep 27, 2026
Sei Technical Reference (external site)Sei Documentation · retrieved Sep 27, 2026
Sei Blockchain Staking Guide (external site)Sei Documentation · retrieved Sep 27, 2026
Node Operations on Sei (external site)Sei Documentation · retrieved Sep 27, 2026
Node Types (external site)Sei Documentation · retrieved Sep 27, 2026
Sei Node Operations Guide (external site)Sei Documentation · retrieved Sep 27, 2026
sei-protocol/sei-chain (external site)Sei Protocol contributors · retrieved Sep 27, 2026
sei-chain v6.6.0 release notes (external site)Sei Protocol contributors · retrieved Sep 27, 2026
What Is Sei Giga? (external site)Sei Documentation · retrieved Sep 27, 2026
Sei Giga Technical Specification (external site)Sei Documentation · retrieved Sep 27, 2026
Sei Labs Publishes the Giga Whitepaper V2 (external site)Sei Blog · retrieved Sep 27, 2026
Sei Parallelization Engine (external site)Sei Documentation · retrieved Sep 27, 2026
Sei Network Accounts: Dual Address System (external site)Sei Documentation · retrieved Sep 27, 2026
SIP-03 Migration Guide (external site)Sei Documentation · retrieved Sep 27, 2026
Sei EVM Upgrade for Exchanges and Custodians (external site)Sei Documentation · retrieved Sep 27, 2026
SIP-3: EVM only (external site)sei-protocol/sips · retrieved Sep 27, 2026
Sei Network Interoperability Framework (external site)Sei Documentation · retrieved Sep 27, 2026
State Proofs (external site)Sei Documentation · retrieved Sep 27, 2026
Ecosystem Contracts (external site)Sei Documentation · retrieved Sep 27, 2026
LayerZero V2 on SEI (external site)Sei Documentation · retrieved Sep 27, 2026
USDC on Sei (external site)Sei Documentation · retrieved Sep 27, 2026
Sei Blockchain Explorers Guide (external site)Sei Documentation · retrieved Sep 27, 2026
SeiScan (external site)Etherscan · retrieved Sep 27, 2026
Seistream Sei explorer (external site)STAKEME · retrieved Sep 27, 2026
Seistream validators (external site)STAKEME · retrieved Sep 27, 2026
Ledger Enterprise Now Supports Sei Network (external site)Sei Blog · retrieved Sep 27, 2026
Hardware Wallets (external site)Sei Documentation · retrieved Sep 27, 2026
Ledger Hardware Wallet Setup Guide for Sei (external site)Sei Documentation · retrieved Sep 27, 2026
Sei Wallet Providers Guide (external site)Sei Documentation · retrieved Sep 27, 2026
Sei wallet (external site)Trezor · retrieved Sep 27, 2026
USDC Contract Addresses (external site)Circle · retrieved Sep 27, 2026
CCTP supported blockchains (external site)Circle · retrieved Sep 27, 2026
DragonSwap documentation (external site)DragonSwap · retrieved Sep 27, 2026
Ledger Wallet coin module loaders (ledger-live develop branch) (external site)Ledger (LedgerHQ/ledger-live on GitHub) · retrieved Sep 27, 2026
Ledger Wallet feature switch for Sei EVM (currencySeiNetworkEvm) (external site)Ledger (LedgerHQ/ledger-live on GitHub) · retrieved Sep 27, 2026
Ledger Wallet feature-switch definitions (a switch declared without a value is off by default) (external site)Ledger (LedgerHQ/ledger-live on GitHub) · retrieved Sep 27, 2026

Report an error

Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.

Report an error about Sei Corrections log

Funding disclosure

Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding