Averaged over the six most recent block timestamps.
Why 2-second blocks →Sovereign L1 · Solidity · Live
A live Solidity chain, running in the open.
Satsuma is a sovereign Layer-1 that runs Solidity smart contracts — live in production, Ethereum-compatible, with blocks that finalize in seconds. Every block is public and readable by anyone; writing to the chain is permissioned.
An Ethereum-compatible blockchain, running in production.
Its own Layer-1 — sovereign, live, and fully transparent. The only thing it holds back is who's allowed to write.
Real Solidity
Contracts run with full EVM semantics — the same bytecode the ecosystem already speaks, no subset and no surprises.
A fixed clock
A block every 2 seconds on a fixed cadence. Finality is deterministic and arrives in seconds — a finalized block is never reorganized.
Public by default
Every block, transaction, and contract call is readable by anyone. The chain hides nothing — the explorer is its front door.
Closed where it counts
Reading is open to all. Transacting and deploying is limited to approved accounts — the chain is sovereign, and stays that way.
Chain ID 555555555
Native token SUMA · 18 decimals · eip-155. One validator set, one job: settle on schedule.
Speaks Ethereum
A standard Ethereum JSON-RPC interface and an EIP-155 chain ID mean familiar wallets and explorers understand Satsuma out of the box.
Numbers you can check.
Live figures are read from the chain by your browser as you watch. Benchmark figures link to the method that produced them.
The finalized block is — behind the head. Finalized blocks are never reorganized.
Litepaper §6 →A 21,000-gas transfer at the current gas price of — gwei: — SUMA.
Litepaper §5 →Median under an eth_call storm against one RPC server, at 4 ms p99 latency.
Given one objective, it built what it needed.
Satsuma is an attempt at a fully autonomous AI. Language models make its decisions; this chain holds its identity, its treasury and the rules it must act within.
In the first governed run, Satsuma was given one objective and an honest description of its surroundings. Nothing it needed existed.
Over 1 hour 45 minutes it proposed six protocols, approved them by vote on its own chain, and built, reviewed and deployed three of them across two chains. Then it used them: ten swaps on a second chain, each inside limits it had written for itself.
No person approved a proposal, a deployment or a trade.
All approved on chain; three built and deployed.
On a second chain, through its own contracts.
By the limits it set itself.
Of proposals, deployments or trades.
[04] Litepaper · v1.1
How the chain actually works.
The technical paper on the network as it runs today: open reads with allowlisted writes enforced by the protocol itself, 2‑second blocks with deterministic finality, stable utilization‑targeted fees — and a trust model we state out loud.
Built in the open, written down.
Deep-dives, measurements and experiments from building Satsuma — with the method alongside every result.
Experiment 01: Satsuma gets a goal, builds what it needs, and trades on another chain
One objective, six proposals, three deployments across two chains, ten swaps — and no human approvals.
Oct 5, 2026 · read →Why Satsuma Has 2-Second Blocks
Block time is the one performance setting a chain can't change after it launches. Here's why Satsuma's is two seconds.
Jul 15, 2026 · read →Inside Satsuma's Performance Benchmarks
What the benchmarks measured, and how — including what a 'transaction' even means.
Jul 13, 2026 · read →