Tooling for bridging tokens and NFTs between Sei and other EVM chains (Ethereum, BSC, and more) using industry-standard cross-chain protocols.
| Directory | Protocol | Asset Type | Description |
|---|---|---|---|
layerzero-oft/ |
LayerZero V2 | Fungible Tokens (ERC-20) | Bridge tokens using Omnichain Fungible Token (OFT) standard |
layerzero-nft/ |
LayerZero V2 | NFTs (ERC-721) | Bridge NFTs using Omnichain Non-Fungible Token (ONFT721) standard |
wormhole-ntt/ |
Wormhole NTT | Fungible Tokens (ERC-20) | Bridge tokens using Wormhole Native Token Transfers |
- Fungible tokens (ERC-20) →
layerzero-oft/orwormhole-ntt/ - NFTs (ERC-721) →
layerzero-nft/
| I want to... | Go to |
|---|---|
| Launch a new token that works across chains | layerzero-oft/oft-token |
| Bridge an existing ERC-20 from Sei to other chains | layerzero-oft/oft-adapter or wormhole-ntt/ |
| Launch a new NFT collection that works across chains | layerzero-nft/onft-token |
| Bridge an existing ERC-721 to Sei from another chain | layerzero-nft/onft-adapter |
| Use Wormhole's guardian-relayed token transfers | wormhole-ntt/ |
sei-bridging-tooling/
│
├── layerzero-oft/ ← Token bridging via LayerZero V2
│ ├── oft-token/ New omnichain token (burn/mint)
│ ├── oft-adapter/ Wrap existing ERC-20 (lock/unlock)
│ └── README.md
│
├── layerzero-nft/ ← NFT bridging via LayerZero V2
│ ├── onft-token/ New omnichain NFT (burn/mint)
│ ├── onft-adapter/ Wrap existing ERC-721 (lock/unlock)
│ └── README.md
│
├── wormhole-ntt/ ← Token bridging via Wormhole NTT
│ ├── example-ntt-token-evm/ EVM token + NTT setup
│ ├── demo-ntt-ts-sdk/ TypeScript SDK demo
│ ├── my-ntt-project/ Starter project
│ └── README.md
│
└── README.md ← You are here
All projects support the following chains out of the box:
| Chain | Mainnet | Testnet |
|---|---|---|
| Sei | Sei mainnet (1329) | Sei testnet (1328) |
| Ethereum | Mainnet (1) | Sepolia (11155111) |
| BSC | BSC mainnet (56) | BSC testnet (97) |
Adding more chains is straightforward — each project's README explains how.
- Pick the directory that matches your use case from the table above
- Open its
README.mdfor a step-by-step walkthrough - Each sub-project is self-contained with its own
package.json, contracts, deploy scripts, and interaction scripts
Every README follows the same flow: install → configure .env → compile → deploy → set peers → bridge → track on explorer.
- Node.js >= 18
- A funded wallet on the chains you want to bridge between