Ship your own
EVM chain.
Deploy EVM smart contracts on a chain you own. Walrus handles data availability, Sui handles settlement, and throughput stays predictable.
Production runs concurrently with finalization. Block time is never gated by DA latency.
// Built from proven primitives
Four layers. One chain.
Podseq as sequencer, EVM execution on Reth, data availability on Walrus, settlement on Sui. Because Walrus blobs are Sui objects, there's no trust hop between DA and settlement.
Orders transactions and produces blocks. The core of the network.
Reth under the hood. Deploy any Solidity contract, unchanged.
Erasure-coded, BFT. Blobs verifiable directly on Sui.
Every block anchored on Sui L1. No separate trust assumption.
Done with shared infrastructure.
Six reasons teams run their own chain instead of renting space on someone else's.
Dedicated throughput, zero contention
Your chain runs on your infrastructure. No shared blockspace, no noisy neighbors.
Block time never waits on DA
Production and finalization run concurrently. Block time stays sub-second while the finalizer posts to Walrus and settles on Sui in the background.
Verifiable by anyone
Full nodes reconstruct and audit the entire chain from DA and settlement alone. No trusted sequencer.
EVM native. Sui anchored.
Deploy standard EVM smart contracts with the tooling you already use. Every block settles on Sui with Walrus availability.
Enshrined Sui bridge
Native asset bridge between your chain and Sui. Move tokens in and out of Sui DeFi without third-party bridges.
Capture every fee
Own the economics end to end. Transaction fees stay on your chain instead of going to a shared sequencer or an L1.
Three signals it's time.
Not every project needs dedicated infrastructure. These are the cases where it pays for itself.
Bring EVM to Sui
Run EVM smart contracts that settle on Sui, with Walrus for data availability. Your existing contracts deploy unchanged.
Tap into Sui DeFi
Your users keep the EVM tooling they know, and get access to Sui liquidity and DeFi protocols.
Auditable, policy-ready chains
Deterministic EVM execution with verifiable commitments on Sui. Built for payments and regulated workloads that need an audit trail.
From zero to a verified chain.
Three steps.
Configure
Create settlement and block keys, write a minimal TOML config, and start the sequencer. Defaults cover everything but the Reth endpoint.
Run the sequencer
Start the Podseq and Reth binaries. They communicate over the Engine API to build blocks and gossip soft confirmations over P2P.
Settle on Sui
Each block posts to Walrus and its blob ID anchors on Sui. Full nodes verify the entire chain from those two sources alone.
Built to be verified.
Ordering, execution, availability, and settlement are separate. Each lives in its own crate and talks to the others through zero-dependency traits in podseq-core. Any full node can re-derive and audit the entire chain from public data alone.
The sequencer broadcasts soft confirmations over P2P for sub-second latency. The finalizer posts each block to Walrus and anchors the blob ID on Sui. Full nodes reconstruct the chain from DA + settlement alone. No sequencer trust required.
A running node in four commands.
Create your keys, write a minimal config, and start. Everything else defaults to testnet.
Full setup guide# shared 32-byte secret for Reth + podseq
head -c 32 /dev/urandom | od -A n -t x1 | tr -d ' \n' > jwt.hex
# reth
reth node --authrpc.jwtsecret jwt.hex
# both sides must use the same jwt.hexQuestions teams ask before committing.
A single sequencer you operate gives sub-second block times, predictable fees, and control over ordering. Since DA and settlement both live on Sui, every block is still independently verifiable. For most teams this is the right trade: simplicity and speed over decentralized sequencing.
Still have questions? Read the full documentation
// Ready to deploy
Your EVM chain,
on your terms.
Walrus for data availability, Sui for settlement. Every block is independently verifiable. No shared infrastructure, no per-transaction fees to a third party.