How to migrate to Sei from another EVM chain
Sei offers full EVM bytecode compatibility plus near-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 – 33× higher than Ethereum mainnet
- Instant finality – 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:
| Feature | Sei | Ethereum | Arbitrum | Base | Polygon PoS | Avalanche C-Chain |
|---|---|---|---|---|---|---|
| Chain ID | 1329 | 1 | 42161 | 8453 | 137 | 43114 |
| Block Time | 400 ms | ~12 s | ~250 ms | ~2 s | ~2 s | ~2 s |
| Finality | Instant | ~15 min (finalized) | ~7 days (L1 settlement) | ~7 days (L1 settlement) | ~2 min (256 blocks) | ~1 s |
| Gas Limit | 10M | ~36M | 32M | ~30M | ~30M | 15M |
| Native Token | SEI | ETH | ETH | ETH | POL (MATIC) | AVAX |
| Parallel Execution | Yes | No | No | No | No | No |
| Base Fee Burn | No (100% to validators) | Yes (EIP-1559) | Yes | Yes | Yes | Yes |
| EVM Version | Pectra (w/o blobs) | Pectra | Cancun | Cancun | Shanghai | Durango |
Chain-Specific Migration Guides
Select your source chain to see specific migration considerations:
Ethereum
Migrating from Ethereum Mainnet
Key Differences:
| Aspect | Ethereum | Sei | Migration Impact |
|---|---|---|---|
| Block time | ~12 seconds | 400 ms | Reduce deadline buffers in DEX swaps by 30× |
| Finality | ~15 min for finalized | Instant | Remove confirmation polling logic |
| Gas limit | ~36M per block | 10M per block | Split large batch deployments |
| Fee model | EIP-1559 with burn | Dynamic, no burn | Update fee estimation UIs |
| Pending state | Yes | No | Remove pending transaction logic |
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
gasLimitcalculations. -
Fee UI: Simplify your frontend—you can use a single
gasPriceinput instead ofmaxFeePerGas/maxPriorityFeePerGas.
// Before (Ethereum EIP-1559)
const tx = await contract.method({
maxFeePerGas: ethers.parseUnits('50', 'gwei'),
maxPriorityFeePerGas: ethers.parseUnits('2', 'gwei')
});
// After (Sei - simplified)
const tx = await contract.method({
gasPrice: ethers.parseUnits('0.1', 'gwei') // Sei has much lower fees
});- 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.
Step 1: Evaluate Compatibility
Revisit the Divergence from Ethereum doc and confirm every assumption your contracts/frontends make still holds.
| Dimension | Sei EVM | Practical Effect |
|---|---|---|
| Block time | 400 ms | Faster TX inclusion → smaller deadline buffers and quicker price oracles |
| Finality | Instant | No separate “safe/latest” commitment levels to poll |
| Gas limit | 10M gas + 21 MB byte limit | Batch contract deployments by 10M gas blocks |
| Base fee | Dynamic but never burned | Validators receive 100% of fees |
| Execution | Parallelized EVM | No changes to your Solidity code are necessary |
| Address format | Dual (0x + sei1…) | Same private key derives both addresses |
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:
import '@nomicfoundation/hardhat-verify';
const config = {
networks: {
seiMainnet: {
url: process.env.SEI_MAINNET_RPC ?? 'https://evm-rpc.sei-apis.com',
chainId: 1329,
accounts: process.env.DEPLOYER_KEYS?.split(',') ?? []
},
seiTestnet: {
url: process.env.SEI_TESTNET_RPC ?? 'https://evm-rpc-testnet.sei-apis.com',
chainId: 1328,
accounts: process.env.DEPLOYER_KEYS?.split(',') ?? []
}
},
etherscan: {
apiKey: {
seiMainnet: 'dummy', // Seitrace doesn't require real API key
seiTestnet: 'dummy'
},
customChains: [
{
network: 'seiMainnet',
chainId: 1329,
urls: {
apiURL: 'https://seitrace.com/pacific-1/api',
browserURL: 'https://seitrace.com'
}
},
{
network: 'seiTestnet',
chainId: 1328,
urls: {
apiURL: 'https://seitrace.com/atlantic-2/api',
browserURL: 'https://seitrace.com'
}
}
]
}
};
export default config;Foundry Configuration:
[profile.default]
src = "src"
out = "out"
libs = ["lib"]
[rpc_endpoints]
sei_mainnet = "https://evm-rpc.sei-apis.com"
sei_testnet = "https://evm-rpc-testnet.sei-apis.com"
[etherscan]
sei_mainnet = { key = "dummy", url = "https://seitrace.com/pacific-1/api", chain = 1329 }
sei_testnet = { key = "dummy", url = "https://seitrace.com/atlantic-2/api", chain = 1328 }See the Hardhat tutorial and Foundry guide for complete setup instructions.
Wallet Configuration
Pre-configure MetaMask or other wallets with Sei chain params:
const seiMainnet = {
chainId: '0x531', // 1329
chainName: 'Sei',
nativeCurrency: { name: 'Sei', symbol: 'SEI', decimals: 18 },
rpcUrls: ['https://evm-rpc.sei-apis.com'],
blockExplorerUrls: ['https://seitrace.com']
};
await window.ethereum.request({
method: 'wallet_addEthereumChain',
params: [seiMainnet]
});Step 3: Bootstrap Common Infrastructure
Sei already exposes canonical helper contracts—reference them instead of redeploying:
| Component | Address | Notes |
|---|---|---|
| Permit2 | 0xB952578f3520EE8Ea45b7914994dcf4702cEe578 | Shared allowance manager for DEX and wallet flows |
| Multicall3 | 0xcA11bde05977b3631167028862bE2a173976CA11 | Enables batching and view aggregation |
| ImmutableCreate2Factory | 0x0000000000FFe8B47B3e2130213B802212439497 | Deterministic deployments with CREATE2 |
| SingletonFactory | 0xce0042B868300000d44A59004Da54A005ffdcf9f | EIP-2470 singleton factory |
For third-party contracts (LayerZero, Safe, etc.), consult the full Ecosystem Contracts page.
Step 4: Port Contracts and Configuration
Parameterize Chain-Specific Constants
// Example: Chain-aware deadline calculation
function getDeadline(uint256 secondsFromNow) internal view returns (uint256) {
if (block.chainid == 1329) { // Sei mainnet
// ~2.5 blocks per second on Sei
return block.timestamp + secondsFromNow;
} else if (block.chainid == 1) { // Ethereum
// ~1 block per 12 seconds on Ethereum
return block.timestamp + secondsFromNow;
}
return block.timestamp + secondsFromNow;
}Adjust Gas and Size Assumptions
- Keep
gasLimitbuffers modest but ensure calldata stays under 21 MB - Sei’s 10M gas limit per block means large deployments may need batching
Refactor Deprecated Patterns
// Before: SELFDESTRUCT (deprecated)
function destroy() external onlyOwner {
selfdestruct(payable(owner));
}
// After: Soft close pattern
bool public closed;
function close() external onlyOwner {
closed = true;
// Transfer remaining funds
payable(owner).transfer(address(this).balance);
}
modifier notClosed() {
require(!closed, "Contract is closed");
_;
}Step 5: Plan Bridging and Cross-Chain Connectivity
LayerZero V2
Sei’s LayerZero Endpoint ID is 30280. See the complete LayerZero integration guide.
import { EndpointId } from '@layerzerolabs/lz-definitions';
const seiContract = {
eid: EndpointId.SEI_V2_MAINNET, // 30280
contractName: 'MyOFT'
};Other Bridge Options
- Circle CCTP: For USDC bridging (check availability)
- IBC: For Cosmos ecosystem assets
- Pointer contracts: For bridging non-EVM assets—see Pointer Contracts
Step 6: Handle Assets and Oracles
Bridge Canonical Assets
Follow the Bridging guide to move core tokens to Sei.
Oracle Integration
Sei supports multiple oracle solutions:
| Provider | Use Case | Documentation |
|---|---|---|
| Sei Native Oracle | Built-in price feeds via precompile | Oracle Precompile |
| Pyth Network | High-frequency price feeds | Pyth Network |
| Chainlink | Industry-standard data feeds | Chainlink on Sei |
| RedStone | Modular oracle with push model | RedStone on Sei |
| API3 | First-party oracle data | API3 on Sei |
Step 7: Launch Checklist
Testnet Deployment (atlantic-2)
- Deploy all contracts to testnet (chain ID:
1328) - Run full integration test suite
- Verify contracts via Seitrace
- Test wallet connections and transaction flows
- Validate oracle integrations
- Test cross-chain messaging if applicable
Mainnet Deployment (pacific-1)
- Deploy contracts to mainnet (chain ID:
1329) - Re-run smoke tests
- Verify all contracts on Seitrace
- Update frontend configurations
- Prepare user migration documentation
Step 8: Operational Readiness
Contract Verification
Automate verification through CI using the Seitrace APIs:
# Foundry verification
forge verify-contract --watch \
--compiler-version "0.8.22" \
--verifier blockscout \
--verifier-url https://seitrace.com/pacific-1/api \
--etherscan-api-key dummy \
--chain-id 1329 \
<CONTRACT_ADDRESS> \
<CONTRACT_NAME>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:
// Monitor current gas prices
const feeHistory = await provider.send('eth_feeHistory', ['0x5', 'latest', []]);
const gasPrice = await provider.getGasPrice();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
- Router:
-
Permit and Multicall: Point your frontend SDK to the shared
Permit2andMulticall3addresses 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 10M block cap
-
Price Oracles: Reuse TWAP/Chainlink logic but shorten observation windows for Sei’s faster blocks.
-
Verification: Submit to Seitrace and the Ecosystem Contracts registry.
Helpful References
- Divergence from Ethereum – Opcode, gas, and state nuances
- EVM Networks – RPCs, explorers, and MetaMask payloads
- Precompiles – Interoperability patterns
- Ecosystem Contracts – Canonical addresses
- LayerZero Integration – Cross-chain messaging
- Contract Verification – Contract verification guide