sei

Deploy and interact with EVM contracts on Sei's parallelized Layer 1 blockchain.

1|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/naruto11eth/cryptoskills --skill sei-naruto11eth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sei
Source: https://github.com/naruto11eth/cryptoskills/tree/main/skills/sei
Command: npx skills add https://github.com/naruto11eth/cryptoskills --skill sei-naruto11eth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires viem.

What problem does it solve? AI agents often have outdated or incorrect knowledge about Sei, such as treating it as a pure Cosmos chain, using the wrong EVM version (Shanghai instead of paris), or building against the deprecated native DEX module. This Skill provides accurate chain configuration, precompile addresses, and working code patterns for Sei development. ## Core Features & Use Cases - Chain Configuration: Provides verified chain IDs (1329 mainnet, 1328 testnet), RPC endpoints, explorers, and Foundry/Hardhat/viem setup with the required paris EVM target. - Precompile & Interop Guidance: Documents all precompile contracts (staking, governance, IBC, bank, address conversion, pointer, Wasm) with Solidity interfaces for EVM-CosmWasm interoperability. - Deployment & Troubleshooting: Includes deployment walkthroughs, contract verification on Seitrace, error-code references, and fixes for common issues like PUSH0 opcode failures. - Use Case: Deploy an ERC20 token to Sei mainnet with Foundry, then query a CW20 token's ERC20 pointer contract and read associated Cosmos-native balances from an EVM address. ## Quick Start Ask the agent to deploy a Solidity contract to Sei testnet using Foundry with the correct chain configuration.

Frequently Asked Questions about sei

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a smart contract to Sei with Foundry?

Set evm_version = "paris" in foundry.toml, then run forge create with --rpc-url https://evm-rpc.sei-apis.com and your private key. Mainnet chain ID is 1329 and testnet (atlantic-2) is 1328.

Why does my Sei deployment fail with an invalid opcode error?

Sei's EVM targets the paris hard fork and does not support the PUSH0 opcode introduced in Shanghai. Set evmVersion to "paris" in your Foundry or Hardhat compiler config, then clean and recompile.

What are Sei precompile contracts and how do I call them?

Precompiles are built-in contracts at fixed addresses (0x...1001 through 0x...100b) exposing Cosmos-native functions like staking, governance, IBC transfers, and address conversion. Call them from Solidity using CALL only; DELEGATECALL is not supported for state-changing operations.

How do pointer contracts work for EVM and CosmWasm tokens on Sei?

A pointer contract is a lightweight proxy that makes a CW20 token accessible as an ERC20 (or vice versa) without wrapping or bridging. Query the Pointer precompile at 0x...100b with getPointer to find or verify a registered pointer address.

Does Sei support standard Ethereum tooling like Hardhat and viem?

Yes, Sei EVM is bytecode-compatible with Ethereum, so Hardhat, Foundry, viem, and ethers.js work without custom plugins. The only required change is setting the EVM version to paris and using Sei's chain IDs and RPC endpoints.

Why do SEI token amounts look wrong between EVM and Cosmos?

SEI uses 18 decimals in the EVM (wei) but 6 decimals in the Cosmos bank module (usei). The chain converts automatically across precompiles and pointer contracts, but IBC transfer amounts follow the Cosmos 6-decimal convention.