Sei offers full EVM bytecode compatibility plus instant finality and sub-second blocks. This guide distills what product teams need to do when they already run on Polygon, Base, Ethereum, Arbitrum, Avalanche or another EVM chain and want to bring your dApp stack to Sei.
Why Migrate to Sei?
- 400ms block times – 30× faster than Ethereum, 2-5× faster than most L2s
- ~100 MGas/s throughput – 20× higher than Ethereum mainnet
- Instant finality (~400 ms) – No waiting for confirmations or safe/finalized states
- Parallelized execution – Higher throughput without code changes
- Full EVM compatibility – Deploy your existing Solidity contracts unchanged
Chain Comparison Overview
Before diving into migration steps, understand how Sei compares to your source chain:
Chain-Specific Migration Guides
Select your source chain to see specific migration considerations:
Ethereum
Arbitrum
Base
Polygon
Avalanche
Migrating from Ethereum Mainnet
Key Differences:What to Update:
-
Time-based logic: If your contracts use block timestamps for deadlines, reduce timeouts proportionally. A 30-minute deadline on Ethereum (~150 blocks) should be ~45 seconds on Sei (~112 blocks).
-
Confirmation requirements: Remove any logic that waits for multiple confirmations or checks “safe” vs “finalized” states—Sei has instant finality.
-
Gas estimation: Sei’s parallelized execution can slightly vary gas estimates. Add a modest buffer (10-15%) to your
gasLimit calculations.
-
Fee UI: Simplify your frontend—you can use a single
gasPrice input instead of maxFeePerGas / maxPriorityFeePerGas.
Sei enforces a 50 gwei minimum gas price; transactions below this are rejected by the mempool. Query the live value with eth_gasPrice (returns base fee + suggested tip).
- PREVRANDAO/DIFFICULTY: If you use these for any randomness, integrate a VRF oracle instead—Sei’s values are derived from block time, not true randomness.
Migrating from Arbitrum
Key Differences:What to Update:
-
Remove L1 interactions: Any logic that posts data to or reads from Ethereum L1 should be removed or replaced with Sei-native alternatives.
-
Sequencer assumptions: Remove any sequencer uptime checks or fallback logic—Sei uses decentralized consensus.
-
Withdrawal delays: If your protocol has 7-day withdrawal windows for “L1 finality,” you can remove these—Sei settles instantly.
-
ArbOS precompiles: Replace any Arbitrum-specific precompiles:
- Cross-chain messaging: Replace Arbitrum’s native bridge with LayerZero V2 for omnichain connectivity.
Migrating from Base
Key Differences:What to Update:
-
Remove blob transactions: Sei doesn’t support EIP-4844 blob transactions. If you’re using them for data availability, store data differently or use Sei’s native mechanisms.
-
OP Stack precompiles: Remove any Optimism/Base-specific precompile calls:
-
Fault proof assumptions: Remove any logic that accounts for the 7-day challenge period—Sei has instant finality.
-
Sequencer fee logic: Base has a separate L1 data fee component. On Sei, fees are simpler:
Gas Used × Gas Price.
-
Coinbase Wallet integrations: Update wallet connection logic to use Sei network parameters:
Migrating from Polygon PoS
Key Differences:What to Update:
- Token references: Replace all MATIC/POL references with SEI:
-
Checkpoint logic: Remove any logic that waits for Polygon checkpoints to Ethereum—Sei has instant finality.
-
Heimdall/Bor assumptions: Remove any Polygon-specific validator or sidechain logic.
-
Reorg handling: You can safely remove block reorganization handling code—Sei’s consensus prevents reorgs.
-
Gas price oracles: Polygon’s gas prices can spike significantly. Sei’s fees are more stable due to higher throughput:
- Bridge integrations: Replace Polygon Bridge with LayerZero or other Sei-supported bridges.
Migrating from Avalanche C-Chain
Key Differences:What to Update:
- Token references: Replace AVAX with SEI:
-
Subnet interactions: If your dApp uses Avalanche Subnets, you’ll need to redesign that architecture for Sei’s single-chain model or use cross-chain messaging.
-
Avalanche-specific precompiles: Remove C-Chain precompile calls:
- Gas limit adjustments: Avalanche now uses a dynamic gas model after Octane, while Sei has a fixed
12.5M block/tx cap. If you have large transactions, benchmark them on Sei and split them when needed:
- TWAP calculations: Both chains have fast blocks, but adjust your observation windows if migrating oracle logic:
Step 1: Evaluate Compatibility
Revisit the Divergence from Ethereum doc and confirm every assumption your contracts/frontends make still holds.
Features Requiring Attention:
- Pending state: Sei doesn’t have pending state — transactions are either included or not
- Blob opcodes: EIP-4844 blob transactions are not supported
- PREVRANDAO entropy: Returns block-time-derived value, not true randomness — use VRF oracles here
- SELFDESTRUCT: Deprecated; refactor to “soft close” patterns
Step 2: Prepare Your Development Environment
Add Sei Network Configuration
Hardhat Configuration:
Store your deployer key in Hardhat’s encrypted keystore with npx hardhat keystore set SEI_PRIVATE_KEY. Contract verification via Sourcify is enabled by default in Hardhat 3’s hardhat-verify (bundled with the toolbox).
Foundry Configuration:
See the Hardhat tutorial and Foundry guide for complete setup instructions.
Wallet Configuration
Pre-configure MetaMask or other wallets with Sei chain params:
Step 3: Bootstrap Common Infrastructure
Sei already exposes canonical helper contracts—reference them instead of redeploying:
For third-party contracts (LayerZero, Safe, etc.), consult the full Ecosystem Contracts page.
Step 4: Port Contracts and Configuration
Parameterize Chain-Specific Constants
Adjust Gas and Size Assumptions
- Keep
gasLimit buffers modest but ensure calldata stays under 21 MB
- Sei’s 12.5M gas limit per block means large deployments may need batching
Refactor Deprecated Patterns
Step 5: Plan Bridging and Cross-Chain Connectivity
LayerZero V2
Sei’s LayerZero Endpoint ID is 30280. See the complete LayerZero integration guide.
Other Bridge Options
- Circle CCTP: For USDC bridging (check availability)
Step 6: Handle Assets and Oracles
Oracle Integration
Sei supports multiple oracle solutions:
TWAP Adjustments: Because Sei blocks arrive ~30× faster than Ethereum, shorten your TWAP observation windows to maintain comparable time-weighted calculations.
Step 7: Launch Checklist
Testnet Deployment (atlantic-2)
Mainnet Deployment (pacific-1)
Fee Redistribution Warning: Fees on Sei are not burned. If your protocol redistributes “burn rebates” to users, redesign that logic so it does not expect a base-fee burn component.
Step 8: Operational Readiness
Contract Verification
Automate verification through CI using Sourcify:
RPC and Indexer Health
- Primary RPC:
https://evm-rpc.sei-apis.com
- Testnet RPC:
https://evm-rpc-testnet.sei-apis.com
- For mission-critical paths, consider self-hosted nodes or premium RPC providers
Monitoring Gas Parameters
Periodically query fee data to keep dashboards aligned:
Example: Uniswap V3-Style Deployment
Here’s how to mirror a Uniswap V3 experience on Sei:
-
Routers & Factories: Deploy your own or fork the existing DragonSwap stack:
- Router:
0xdD489C75be1039ec7d843A6aC2Fd658350B067Cf
- V3 Factory:
0x75FC67473A91335B5b8F8821277262a13B38c9b3
- Position Manager:
0x8B3c541c30f9b29560f56B9E44b59718916B69EF
-
Permit and Multicall: Point your frontend SDK to the shared
Permit2 and Multicall3 addresses above.
-
Liquidity Migration Script: Build a helper that:
- Withdraws LP on source chain
- Bridges underlying tokens to Sei
- Mints new Sei LP positions
- Include gas estimations tuned for Sei’s 12.5M block cap
-
Price Oracles: Reuse TWAP/Chainlink logic but shorten observation windows for Sei’s faster blocks.
-
Verification: Submit to Sourcify and the Ecosystem Contracts registry.
Helpful References